A practical guide to the many architectural, design, and coding decisions you too will need to make on the way to microservices.
To further improve time-to-market and adaptability in delivering their services, e-commerce company iBOOD (well-known for their daily deals) is reshaping their software landscape, which largely consists of a number of mobile applications (built with Flutter), web applications (TypeScript, React), and back-end services (TypeScript, nodejs, Python, Kotlin).
While the current landscape must continue to run and evolve (the shop must remain open), we started working on a new microservices platform called Ibex, which leverages state-of-the-art technology, such as Typescript, node.js, and additional frameworks (such as @thisisagile.easy), continuous delivery, fully automated pipelines and running on the Google Cloud Platform. Unfortunately, with microservices, there is no well-described recipe that will take you directly to your desired end state. So, together with the tech team Sander Hoogendoorn, CTO at iBOOD, ventured off to and is trying to navigate through the many big and small decisions you need to make when moving towards microservices technology on a daily basis. During this interactive talk, Sander will take you through the small steps iBOOD is making, illustrating many of these architectural, design, and frameworks decisions made, along the way, with real code examples in Typescript, slowly arriving at a happy state and a set of patterns and coding techniques that evolved along the way.
Sander not only talks the talk but walks the walk as well. The effort his teams have put in building microservices has resulted in a nice open-source framework called thisisagile.easy. If your company or organization is also underway towards a microservices architecture, and continuous delivery, be sure to visit this talk, as you too will have to answer many of the questions Sander and his team are facing, and have faced in earlier successful implementations..