> ## Documentation Index
> Fetch the complete documentation index at: https://docs.opigno.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Integration & Concepts

# API as a Microservice​

The approach outlined below is built on a core principle: **all data extensions and enhancements occur exclusively at the back-end middleware level.** This ensures the original API remains a true microservice: **simple, stable, and immutable.**

Clients interact with the API to access core data, but the **back-end middleware handles all business logic, data enrichment, and integration with external systems.** This setup gives clients the flexibility to adapt and extend data to meet their needs **without modifying the API itself.**

# **Concept & Example**

<img src="https://mintcdn.com/connect-i/duHonZHPe3F63_yi/images/opigno-enterprise-v4.drawio-2fa12d499223571b83c35e018d8c54a5.png?fit=max&auto=format&n=duHonZHPe3F63_yi&q=85&s=23f32ba66b4002089b9f3791d3fb0083" alt="Opigno Enterprise V4 Drawio 2fa12d499223571b83c35e018d8c54a5 Pn" width="4342" height="1716" data-path="images/opigno-enterprise-v4.drawio-2fa12d499223571b83c35e018d8c54a5.png" />

<Note>
  **KEY TAKEAWAY**\
  This architecture emphasizes the principle of **loose coupling** between components. The **API remains unchanged**, regardless of changes in client requirements.
</Note>

* **All extensions and custom logic** are handled on the **back-end middleware**.
* Middleware is responsible for:
  * **Integration with external sources**
  * **Data enrichment and transformation**
* Each client has the **freedom to configure middleware** according to their specific needs.

<Tip>
  **WHY THIS MATTERS**\
  This approach provides developers with **full control** over the data transformation process. The API stays:

  * **Simple**: Focused only on providing core data.
  * **Reliable:** Free from frequent updates or client-driven changes.
  * **Independent:** Unaffected by unique client-side requirements.
</Tip>

### Advantages of API as a Microservice

We have separated the API into an independent microservice to simplify the integration process and enhance client experience:

* **Reducing Technical Burden**: We take full responsibility for maintaining and evolving the API, relieving clients from the need to support complex technical solutions.
* **Modular Approach**: The API is built using a microservice architecture, ensuring flexibility and ease of scalability.
* **Enhanced Functionality**:
  * Analytics tools for data analysis.
  * Advanced statistical capabilities.
  * Regular endpoint updates to meet modern requirements.

### What Does This Mean for Clients?​

* **Focus on Business Goals**: Clients can concentrate on achieving their educational objectives without worrying about technical support.
* **Updatable Features**: You gain access to a constantly evolving service that adapts to your needs.
* **Scalability**: Easy integration enables seamless expansion of functionality in the future.