Microservices: Distributed Data Patterns
tldr It shouldn’t be synchronous I’ve written about microservices before, based on the work I did with the MAD-API program. One of the particular limitations and lessons learnt was that all
A collection of 17 posts
tldr It shouldn’t be synchronous I’ve written about microservices before, based on the work I did with the MAD-API program. One of the particular limitations and lessons learnt was that all
Legacy corporates are abound, and they see the Internet unicorns stealing their lunch. They know that if you cant beat 'em, then join 'em. So they also want some of the fancy stuff
In the post about APIs and SOA, I mentioned briefly the architecture we designed and built to the support MAD-API: the API ecosystem. To begin understanding MAD-API and API Management, the first starting
It's one thing reading about the extreme DevOps practices of the unicorns (Google, Facebook, etc), and it's completely another thing trying to adopt DevOps in a legacy organisation. Thats why it's reassuring to
In a previous post, we spoke in depth about product/feature teams. In this post, I want to talk about a Platform team, that will support the platform used by the feature teams
When ever we talk about APIs, people always think about the legacy ESB/SOA/ESF stack. They are not meant to solve the same problems. SOA uses APIs – that’s about the only