> For the complete documentation index, see [llms.txt](https://gotolabs.gitbook.io/lightninguservault/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gotolabs.gitbook.io/lightninguservault/architecture/overview.md).

# Overview

Welcome to the architectural heart of LightningUserVault! Our system is designed with modularity at its core, ensuring flexibility, scalability, and ease of integration

<figure><img src="https://2137313636-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI5rA29fXhJTbisED1H7y%2Fuploads%2Fva5Ff6WfTznSRKI4iAiN%2Farchitecture.png?alt=media&amp;token=44ab19fc-539c-4db8-a872-d0f2b1a28f53" alt=""><figcaption><p>LightningUserVault</p></figcaption></figure>

1. 📡 **Listener**:
   * **Current**: Our primary listener is HTTP, ensuring seamless communication and data transfer.
   * **Future Vision**: We're gearing up to extend our listeners to include WebSockets (WSS) and gRPC.
2. 🚦 **Router**:
   * A dynamic component that efficiently directs incoming requests to their respective endpoints. It ensures that every request finds its way to the right handler.
3. 🛠️ **Handlers**:
   * Handlers process the requests, interacting with caching mechanisms and storage to fetch or store data.
4. ⚡ **Caching Mechanism**:
   * Designed for speed! Our caching system ensures that frequently accessed data is retrieved swiftly, reducing the need to access primary storage. It's modular, allowing for easy integration of different caching systems.
5. 🗃️ **Storages**:
   * The backbone of data persistence. Whether it's key-value storage like Pebble or relational databases like PostgreSQL, our storage system is flexible and ready to accommodate.

#### 🌟 **The Modular Advantage**:

Our emphasis on modularity means that each component of LightningUserVault can be developed, scaled, or replaced independently.