Infrastructure
The Bosca Framework relies on a set of robust infrastructure services to ensure scalability, reliability, and performance.
Infrastructure
The Bosca Framework relies on a set of robust infrastructure services to ensure scalability, reliability, and performance.
Docker Services
The development environment is containerized using Docker Compose. The following services are configured:
| Service | Image | Port | Description |
|---|---|---|---|
| NATS | nats | 4222 | High-performance messaging system. Can be used for caching, pub/sub, job queues, and distributed locking. |
| Meilisearch | getmeili/meilisearch | 7701 | Next-generation search engine used for fast and relevant content search. |
| PostgreSQL | postgres | 5433 | Primary relational database for transactional data. |
| PostgreSQL Warehouse | postgres | 5434 | Secondary database optimized for analytics and warehousing tasks. |
| S3Proxy | andrewgaul/s3proxy | 8000 | S3-compatible interface for local object storage testing. |
| Trino | trinodb/trino | 8089 | Distributed SQL query engine for big data analytics over S3 storage. |
| Text Extractor | ghcr.io/sowers-io/bosca/text-extractor | 8083 | Service for extracting text from various document formats. |
| Jaeger | cr.jaegertracing.io/jaegertracing/jaeger | 16686 | Distributed tracing platform for monitoring and troubleshooting. |
| Redis | docker.dragonflydb.io/dragonflydb/dragonfly | 6380 | In-memory datastore. Can be used for caching, pub/sub, job queues, and distributed locking. |
Infrastructure Diagram
Engineering
Welcome to the engineering documentation for the Bosca Framework. This section is designed to provide software engineers with a detailed understanding of the system's architecture, components, and data flow.
Backend Services
The backend logic is distributed across several key services, each responsible for a specific domain of the Bosca Framework.