# Microservice API - The key to seamless server communication!

<figure><img src="/files/VvjfG1NTaAj8DzMZHaeS" alt=""><figcaption></figcaption></figure>

## Using microservices

Using microservices for your Minecraft plugin is a better approach compared to\
directly using MySQL, MongoDB, etc., in your code for several reasons:

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td></td><td><mark style="color:blue;"><strong>Scalability:</strong></mark> Microservices allow you to scale individual components of your plugin independently, allowing you to handle increased traffic or load more efficiently.</td><td></td></tr><tr><td></td><td><mark style="color:blue;"><strong>Maintainability:</strong></mark> By breaking down your plugin into smaller, self-contained services, it becomes easier to maintain and update each component individually. </td><td></td></tr><tr><td></td><td><mark style="color:blue;"><strong>Improved security:</strong></mark> Microservices help to isolate different components of your plugin, reducing the risk of security breaches or vulnerabilities. </td><td></td></tr><tr><td></td><td><mark style="color:blue;"><strong>Better performance:</strong></mark> By breaking down your plugin into smaller components, you can reduce the amount of data that needs to be transferred between services.</td><td></td></tr></tbody></table>

In conclusion, using microservices for your Minecraft plugin provides numerous benefits, \
from improved scalability and maintainability to better performance and security.

## Want to jump right in?

Feeling like an eager beaver? Jump into the quick start docs and get making your first request:

{% content-ref url="/pages/8dmf0ESUVFBZomx6SLJj" %}
[Initialization](/microservice-api/reference/initialization.md)
{% endcontent-ref %}

{% content-ref url="/pages/VHmNscTWzA3kCnJJgM2Y" %}
[Intro: Making requests](/microservice-api/reference/intro-making-requests.md)
{% endcontent-ref %}

## Want to deep dive?

Dive a little deeper and start exploring our API reference to get an idea of everything.

{% content-ref url="/pages/wnvxFhbJX4Jr1s3Uz8AX" %}
[Make request: Spigot](/microservice-api/reference/intro-making-requests/make-request-spigot.md)
{% endcontent-ref %}

{% content-ref url="/pages/VLMOlKpbernBc40vr1Ec" %}
[Send response: Microservice](/microservice-api/reference/intro-making-requests/send-response-microservice.md)
{% endcontent-ref %}

Or if you want to go step by step, click here under to start.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://walkinthepark.gitbook.io/microservice-api/microservice-api-the-key-to-seamless-server-communication.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.