Proof data consistency in a micro service landscape
Introduction
Even if it doesn't appeal to you, you might want to think about it when you work in a larger microservice landscape or have a serious big data platform. . .
When it comes to developing software we use the adagio: You built it, You run it, You love it. Same should hold for all the -ilities or non-functional requirements. So, one should love their logging.
Software Parade; the fun way to create an overview of hundreds of applications in Neo4J
One of the challenges in a (micro-)service landscape is to keep track of all capabilities in the services. Another is to keep track of the consumers of your service and the consumers beyond. Taking our IT landscape as...
Web applications usually start small and loveable, but gradually become larger and larger as more people work on them and front-end technologies move on. If you’re not careful they can potentially end up as the one thing no-one wants...
Video: Insights- Building a Boomerang that doesn’t come back (to haunt you) at Spaces Summit
“My past year as a software engineer at bol. com has mostly been dedicated to breaking down one of the big monoliths within our software landscape into smaller services. To be more specific: I’ve been working in a team to extract the processes related to customer returns into a separate microservice.
During the GoTo Amsterdam conference this year, I did a talk on "Resilience Engineering in a Microservice Landscape".
About the talk
In this talk I show how we at bol. com achieve fault tolerance across our application landscape.
Services & Autonomy: the one can’t live without the other
Services: automated business processes in small systems, connected through API’s. What started out as a means of technical scalability turned out to be the most important driver of team autonomy – and vice versa. This is our story of Backspin, Rabbits and the Man on the Moon.
How do you get the IT management board to serve you coffee on a golden platter? You have to do something good of course, exceptional in fact. In order to tell you how we became top performer instead of database killer by creative use of a cache, we will have to take you back to December 2015, when it all started.
December.
Resilience engineering in a microservice landscape
Attend my talk at GOTO to learn how we, the largest online retail platform in the Netherlands and Belgium, achieve fault tolerance. The bol. com website depends on dozens of services that might fail at any time.