Hi Darya, tell us who you are and what lead you into microservices?

 

Hello! I am Software Developer with 2 years of experience. I currently work at Theodo where we help small and big companies launch new products and evolve existing systems. During my time at Theodo, I’ve participated in a project that span over five years and needed to address complex business logic. In order to have a performant application with clear and maintainable code, we chose the microservices architecture. And it worked great, until the number of microservices reached 30 and this started to cause some problems.

 

What will you be talking about at Voxxed Days Microservices? 

 

I will share with you the story of our 30 microservices that resided in their own code repositories and that caused issues with code quality and developer productivity. I will explain you how we performed the Great Migration to the Monorepository and the ways in which it changed our developers life for the better.

 

When talking about Microservices, we talk about isolated teams, isolated versioning, and isolated code. Isn’t the mono repo approach against the Microservice way of releasing ? 

 

Interesting question! Microservices whose code is kept in a monorepository remain independent. Separate releases can be managed via homemade or existing tools, like “lerna” for JavaScript projects. And the code and logic of each microservice remain isolated, even though it cohabits in the same repository as other microservices.

 

Good, see you soon then 

 

Thank you for choosing my talk for the 2019 edition of Voxxed Days Microservices! I am looking forward to sharing my experience with the participants and I hope that the monorepository approach will prove helpful for some of you!

 

#microservices #monorepo #realstory 

 

My contact information

LinkedIn: https://www.linkedin.com/in/darya-talanina-01b482a3/ 

GitHub: https://github.com/invfo

Twitter: https://twitter.com/invfo