Evolution of microservice architecture on Conversations API [ukr]
I'm going to talk about the evolution of microservice architecture on Twilio product called Conversations API. We'll consider the main reasons and drivers for architecture changes approaches to how we split our services and even in some cases merged several services in one. As a result, we'll sum up what our new architecture will look like, how it solves initial targets, and how it can be used for the next features.
- Tech Lead at Twilio
- Mostly works with Java, although during his work he had to work with Groovy, the frontend (Angular), and as DevOps. In the end, he settled on the backend role
- Has decided to try himself in a product company, so he’s chosen Twilio
- He is currently developing and scaling a backend for a Twilio product Conversations
- Facebook, Linkedin