MAD-API: A real world Digital Transformation experiment
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
API
A collection of 22 posts
Real world API ecosystem architecture
In the post about APIs and SOA, I mentioned briefly the architecture we designed and built to the support MAD-API: the API ecosystem [http://hacksaw.co.za/blog/a-real-world-dx-experiment/]. To begin understanding MAD-API
Book Review: The DevOps Adoption Playbook - Sanjeev Sharma
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
Scaling out DevOps: Product and Platform Teams
In a previous post, we spoke in depth about product/feature teams [http://hacksaw.co.za/blog/conways-law-and-devops-moving-the-org-structure-to-feature-teams/] . In this post, I want to talk about a Platform team, that will support the
API and microservices vs ESB
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
Legacy Software Architecture in Corporates
In a previous post, I got started on Making Architecture Matter [http://gcp.hacksaw.co.za/blog/making-software-architecture-matter/]. Specifically in corporate enterprises, architecture is more about hand-wavy, fluffy things that has nothing to