Event-Driven Architecture
A software design pattern where the flow of the program is determined by events such as user actions, sensor outputs, or messages from other services.
BasaltHQ's inter-module communication is entirely event-driven. When a new deal closes in BASALTCRM, it emits a "DealClosed" event. BASALTERP subscribes to this event and automatically provisions the resources needed to fulfill the order. BASALTONYX subscribes to generate the contract. The billing module subscribes to create the invoice. No module directly calls another; they all react to events on a shared bus. This loose coupling means new modules can be added to the ecosystem without modifying existing ones—they simply subscribe to the relevant events.
Related Concepts
See also:
Autonomous Orchestration
The ability of an AI system to coordinate workflows across multiple enterprise platforms without human scheduling or intervention.
See also:
Microservices
An architectural style where an application is composed of small, independently deployable services, each running its own process.
See also:
API Gateway
A server that acts as the single entry point for all API requests, handling routing, authentication, rate limiting, and monitoring.