How oexza/orisun works
• Core Server Application (Orisun Server): This is implemented predominantly in Go (located in the “src/orisun” folder) and is responsible for handling incoming gRPC requests, event storage logic, and managing the modular components (admin, event store, and various storage backends).
• Database (PostgreSQL): Used for durable event storage, automatic schema setup, and managing boundaries (each PostgreSQL schema representing a bounded context).
• Embedded Messaging System (NATS JetStream): Provides real‐time event streaming and pub/sub. It is embedded, meaning that no external NATS service is required—but it still represents a separate logical component.
• Client Libraries: For example, the Java client (present under “clients/java”) which communicates with the Orisun server via gRPC. This highlights the external interfaces and connectivity.
• Administration & UI Components: These are parts of the “admin” module (files under “src/orisun/admin”) containing handlers, templates, and dashboards. They deliver the administrative interface for schema and event management.
Relationships and Interactions
• Administrative & Configuration Interaction: The admin sub-module in the Go code manages boundaries, authentication, and provides templates for dashboards. Indicate this as a separate module within the Orisun server that interfaces with the database and monitoring/logging functions.
Architectural Patterns and Design Principles
• Modular and Extensible Architecture: The project separates different functionalities into distinct directories (admin, eventstore, multiple storage backends like PostgreSQL, SQLite, and FoundationDB). Annotate these modules and emphasize the “Batteries Included” philosophy.
• Real-time Streaming: Demonstrate a pipeline from the server’s event processing to NATS JetStream for pub/sub and back to any subscribing clients.
• API-Driven Communication: Use the gRPC interface as the primary communication mechanism between external clients and the backend components.