With the demands of our software architectures growing, our team sizes expanding and getting more and more agile in our software development processes, our often monolith-like software architectures can't always keep up with this pace.
While modularity is often built right into our software stacks using library focused design, dependency injection or (often tightly knitted) services; A populair approach to designing applications is using Microservices. This design pattern builds upon the principle of lightweight services often following a symmetrical instead of hierarchical design. By isolating behaviour and state, the pattern aims at building software components with less dependencies. Accelerating productivity, time-to-market and improving overall reactive traits (responsiveness, resilience, elasticity).
In this meetup, the talks will focus on the basis of this principle, why and when you should use it and how to implement the concepts on multiple levels of a software architecture.
Gideon de Kok (Xebia): Building on the shoulders of giants – Microservices as a redesign strategy
A common interpretation of the strengths of microservices is formed around the idea of scalability: by sharding application logic into multiple smaller components, overall scalability can be improved. And while elasticity is a trait which occurs when systems are composed of independent services. The true strengths of microservices go far deeper than runtime performance.
In this talk, Gideon will show how the concept of microservices can be used to (re-)gain business flexibility by improving time-to-market of new functionality while regaining agility within the development process.
Ruben Oostinga (Xebia): Frontend and Microservices
A possible adoption of a microservice based architecture doesn't only impact the back-end side of application structures. Since most applications have some user-facing parts, the way of working with microservices should also be adopted as a front-end developer.
Ruben will show how to work with multiple teams on multiple components in multiple microsites; how to set-up your architecture, what kind of tools to use and how to collaborate to integrate all parts into a functioning whole.
Harm Weites (Wehkamp): The Microservices journey starts in your infrastructure Wehkamp started with microservices a fair 2-3 years ago and we figured the infrastructure plays a pretty big role in making stuff work. Developing microservices can be a pain, so let's make sure everything around that pain simply just works.
This talk will tell you about what the shift to building microservices meant for the infrastructure we had running at Wehkamp.