Middleware Plane
Reference: This page is a source-based technical synthesis of the LaTeX chapter cited below. For exact syntax, availability or ABI signatures, verify the versioned source, manifest and executable tests.
Scope and source boundary
Middleware composes service adapters and messaging patterns without displacing modeled business authority.
The runtime books distinguish centralized, distributed and decentralized topologies. These choices concern component placement, communication, ownership and failure handling; they should not silently change what a business concept means. Local service calls and remote invocations need explicit operation and consistency boundaries.
Engineering rules
- Choose the smallest topology consistent with required deployment and fault boundaries.
- Document state ownership and what crosses a remote call.
- Treat retry, cancellation, duplicate delivery and disconnection as design conditions.
- Do not claim the same execution guarantees for every transport or platform.
Chapter outline (original LaTeX headings)
- Why Service Architecture Matters
- SOA versus Microservices
- How logiCells Defines a Service Boundary
- Actions as Service Operations
- Collections as Query Endpoints
- Events as Integration Signals
LaTeX provenance
Primary chapter: Runtime/logiCells Runtime Programming with RadStudio/soa-microservices-and-runtime-service-boundaries.tex.