![]() ![]() ![]() Sure, you have a monolith, but you'll have tons of other stuff that is also interacting with that. This is the dream and it's a very nice scenario because in reality, things are a bit more complicated, normally your system will look a lot like this. It will help you create that independence that you need and it will help you increase the velocity and the delivery lead time or that will decrease that time, so going to production much faster. You think that moving into the amazing world of microservices will help you solve a lot of those programs. This is the typical scenario, you have a monolith that has been working for many years, but is now in slowing stage and is slowing you down because it's not giving you the delivery speed that you need or the business needs and also, it's very painful to work with. Then we're also going to link it to some of the operational concerns and observability concerns that you also need to bake in when you are breaking down your monolith. We're going to talk about using domain driven design to help us understand better our system and to make better decisions when we want to break it down into microservices. We're going to be splitting this talk in two parts. This talk will have a lot of the experience and learnings that I picked up along the way and I hope that what I'll say will resonate with most of you, either because you have gone through similar experience or because you are the in the middle of one of them. ![]() As I said, I've been working for ThoughtWorks for seven years, in the last four and a half I've been mainly working with organizations that are on a digital transformation journey. Currently, I play the role of Head of Technology for ThoughtWorks in Spain in sunny Barcelona. Gomez: My name is Maria Gomez, I've been working at ThoughtWorks for the last seven years. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |