Command Query Responsibility Segregation (CQRS) is an architectural pattern that segregates reads and writes of a system into two separate models. We propose and demonstrate an approach for building a RESTful API on top of CQRS systems. This approach joins HTTP semantics and resource-based style of REST APIs with distributed computing concerns such as eventual consistency and concurrency.
This article will take you through creating a simple RESTful web service with Spring Boot and Aerospike, a distributed and replicated in-memory NoSQL database.
Bureaucracy often plagues large product development efforts. Just like technical debt slows down development, process debt slows down your business. Eliminate process debt to get to market faster. 9
The growth of mobile devices, advances in technology and the rise of social media are impacting the way customers interact with organisations. Automated BPM can help organisations respond.
Winston Bumpus introduces Cloud Service Brokers – agents providing guidance in selecting and using the most appropriate cloud service – and the CIMI model used to integrate cloud service providers. 2
Web services offer distinct opportunities for real-time innovation, but requires new standards in the way APIs are secured and managed at the B2B enterprise gateway level.
The battle over security and performance is fought by security professionals and network administrators. These factions have to barter an uneasy truce for the organization to survive.
Zato is an open-source ESB and application server written in Python. It is designed to integrate systems in SOA and to build backend applications (i.e. API only). 2
Paul Dix leads a practical exploration into Big Data in this video training series. The training focuses on the high level architecture while teaching practical usage skills and Ruby algorithms.
Kai Wähner explains the differences between an integration framework, an ESB and a suite, following with advice for selecting the right one from existing commercial and open source solutions. 19
This article (the second in a four-part series) focuses on the design of a hypermedia server based on the API designed for the class scheduling problem domain outlined in part one of the series. 1