Errors frequently occur when processing records in transactional applications. Often times the underlying issue causing the error is transient, for example a remote system might be briefly offline or temporary network latency may cause a timeout. In these scenarios, frameworks
Read more
With the proliferation of service meshes composed of Microservices, Application Programming Interfaces (API’s) and the API Management (APIM) solutions to develop, deploy, manage and govern both API’s and Microservices, the need for Site Reliability Engineering (SRE) best practices
One of the most exciting things about API’s is the ability to invoke them to parse and evaluate a message (i.e. an Order Status object), and, based on the contents of the message, distribute to up to N
Decoupling monitoring infrastructure from an application’s behavior and infrastructure is a foundational technique for scaling a distributed system. There is unfortunately no escape from the “Observer Effect”, even in application development. Attempting to “observe” an application generally involves either
Combining API-Led and Domain Driven Design to Govern Your Microservices Architecture (MSA)
API-Led Connectivity is a technique of organizing the API's microservices expose into three categories: System, Process and Experience. In previous blog posts I've covered how System API's act
As alternative modern development platforms, such as SalesForce Lightning, Mendix and even analytics platforms like R proliferate, the role and value of API's can be a critical component to unleash their full potential. While these platforms promise rapid application development
Anti-Corruption Layers (ACLs) are an important Domain Driven Design pattern. ACLs translate data from foreign systems into the Ubiquitous Language (the practice of developing a common and rigorous vocabulary between the developers and users within a given business domain to