> For the complete documentation index, see [llms.txt](https://docs.rumi.systems/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rumi.systems/rumi-core/core.md). # Overview Rumi Core is the foundation of the Rumi platform, providing the microservice runtime and low-level operational tools for building ultra-low latency, fault-tolerant distributed systems. ## Overview Rumi Core provides: * **AEP Engine** - The Application Event Processor that drives microservice business logic * **SMA** - The Simple Messaging Abstraction for transport-agnostic messaging * **Container** - The runtime host for Rumi microservices * **ADM** - The Application Data Modeler for defining messages and state ## Key Capabilities * Event-driven, single-threaded business logic model * Automatic high availability with Event Sourcing or State Replication * Zero-garbage operation for predictable latency * Transparent clustering and failover ## Sections * [Concepts](/rumi-core/concepts.md) - Core architectural concepts and models * [Guides](/rumi-core/guides.md) - Developing and operating Rumi applications * [Reference](/rumi-core/reference.md) - Annotations, events, and configuration reference --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.rumi.systems/rumi-core/core.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.