<commit_before>---
title: How does it work?
---

# How does it work?

Kong is made of two different components that are easy to set up and scale independently:

* The **Kong Server**, based on a modified version of the widely adopted **NGINX** server, processes API requests.
* **Apache Cassandra**, a highly scalable Datastore for storing operational data, which is being used by major companies like Netflix, Comcast or Facebook.

Kong needs to have both these components set up and operational. A typical Kong installation can be summed up with the following picture:

![](/assets/images/docs/kong-detailed.png)

Don't worry if you are not experienced with these technologies, Kong works out of the box and you or your engineering team will be able to set it up quickly without issues. Feel free to contact us for any technical question.

## Kong Server

The Kong Server, built on top of **NGINX**, is the server that will actually process the API requests and execute the configured plugins to provide additional functionalities to the underlying APIs before proxying the request to the final destination.<commit_msg>fix(how): Trim down apache cassandra entry<commit_after>---
title: How does it work?
---

# How does it work?

Kong is made of two different components that are easy to set up and scale independently:

* The **Kong Server**, based on a modified version of the widely adopted **NGINX** server, processes API requests.
* **Apache Cassandra**, a highly scalable Datastore for storing operational data, used by major companies like Netflix, Comcast and Facebook.

Kong needs to have both these components set up and operational. A typical Kong installation can be summed up with the following picture:

![](/assets/images/docs/kong-detailed.png)

Don't worry if you are not experienced with these technologies, Kong works out of the box and you or your engineering team will be able to set it up quickly without issues. Feel free to contact us for any technical question.

## Kong Server

The Kong Server, built on top of **NGINX**, is the server that will actually process the API requests and execute the configured plugins to provide additional functionalities to the underlying APIs before proxying the request to the final destination.
{'fraction_non_alphanumeric': 0.05538325210456358, 'fraction_numerical': 0.0, 'mean_word_length': 4.575308641975309, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3924404', 'n_tokens_mistral': 537, 'n_tokens_neox': 520, 'n_words': 343}