# Front-end & Back-end

AETHRA’s platform architecture is designed for performance, scalability, and ease of iteration, leveraging modern frameworks across both the front and back end.

***

## Front-End (User Interface)

* **Framework** – Vue.js for reactive UI components and scalable SPA design
* **Styling** – Tailwind CSS for utility-first, responsive design with consistent spacing and typography
* **Testing** – Playwright for end-to-end testing, regression coverage, and component isolation

***

## Back-End (Server & API)

AETHRA’s backend is built as a microservices architecture, meaning the system is composed of many small, independent services. Each service is responsible for a specific domain, such as authentication, time tracking and compensation logic.

### Key Characteristics

* **Independent operation** – Every service runs on its own. If one service fails, the rest of the system continues running.
* **Isolated data** – Each service maintains its own database, ensuring clear separation and preventing cross-service interference.
* **Scalable design** – Services can be scaled independently, allowing the platform to grow without friction.

### Event-Driven Communication

To keep services in sync, the backend uses AWS SNS (Simple Notification Service) and AWS SQS (Simple Queue Service):

* SNS broadcasts events whenever something important happens (e.g., a new user signs up or a staffing request is created).
* SQS delivers these events to the right services in the correct order, ensuring nothing is lost.

This event-driven design keeps the system loosely coupled: services don’t need to know about each other directly, they simply listen for the events they care about.

### Benefits

* **Reliable** – One service crashing doesn’t break the entire platform.
* **Scalable** – New services can be added, or existing ones expanded, without major rewrites.
* **Efficient** – Each service only processes what it needs to, while communication is handled automatically.

***

### CI/CD & DevOps

* **Infrastructure** – Hosted on AWS with containerized deployments
* **Continuous** **Integration** – Automated builds and testing before deployment
* **Continuous** **Delivery** – Rolling updates with minimal downtime
* **Monitoring & Alerts** – Real-time performance and error monitoring to ensure uptime

***

{% hint style="success" %}
AETHRA’s backend is engineered for continuous availability. Even if individual services fail, the platform as a whole keeps running without disruption. This resilience ensures providers, clients, and workers can always rely on AETHRA to be available when they need it most
{% endhint %}

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


---

# 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://docs.aethra.work/front-end-and-back-end.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.