The Paremus Service Fabric does not enforce any particular architectural form on the hosted applications.
- Messaging middleware and protocols are the concerns of each System.
- The messaging middleware and protocols are determined by the selection of bindings and middleware components used within each System e.g. SEDA, ESB, Tuple Space or P2P.
- Low latency, batch grid, order matching and transactional messaging based systems can all be run concurrently on the same Service Fabric.
Likewise, the Service Fabric does not dictate persistence API’s, instead it allows the selection of the most appropriate NoSQL solution based upon the requirements of your business data and the Consistency, Availability and Partitionability trade-offs dictated by your business SLAs.
To help get you started we provide a number of popular open source and commercial middleware and NoSQL technologies as optional pre-packaged Runtime Patterns. We also offer consulting services to help you integrate alternatives.