The best compilation of January meetups about microservices is here! These were the most viewed videos this month so you might definitely want to check them out too. We wanted to make things easier for you folks, so decided to make a list of what you shouldn’t miss out.
Microservices enable reusability, make it easier to change and scale apps on demand but they also introduce new problems. How do they interact with each other toward a common goal? How do you figure out what went wrong when a business process composed of several microservices fails? Should there be a central orchestrator controlling all interactions between services or should each service work independently, in a loosely coupled way, and only interact through shared events? In this talk, Mete and Guillaume explore the Choreography vs Orchestration question and see demos of some of the tools that can help.
For a microservices architecture to be succesful it is crucial to have the right boundaries. But where are the right boundaries? Henning presents a tool that helps us answer this question.
The advent of Kubernetes and in particular the Knative Serverless and Functions technologies have opened up an amazing path to writing efficient, non-resident microservices. The session explains the ease of using the new abstracted Cloud Event technology as a bus for driving events to microservices that are deployed only on demand. It’s a mindshift but one that will open up huge opportunities for writing highly efficient and agile workloads.
When you first get started with using Springboot microservices in a distributed architecture, things are remarkably easy. But it won’t take long for a production system to start showing some signs of strain. Nialll demonstrates how a workflow engine or state machine can easily improve your architecture and decrease coupling. He will have three Springboot microservices ready, refactor them live on stage and add Camunda’s Open Source workflow engine. You will not only gain a better understanding of the architecture, but also can follow along on the code level.
Wix has a huge scale of traffic. More than 500 billion HTTP requests and more than 1.5 billion Kafka business events per day. This talk goes through 4 Caching Patterns that are used by Wix’s 1500 microservices in order to provide the best experience for Wix users along with saving costs and increasing availability.