Pipedrive Engineering: Building Microservices at Scale

Building software that scales is hard and doesn't get easier as a SaaS product grows in either complexity or user base.

A well-known strategy for scaling a SaaS product is to use a Microservice Architecture, which comes with its own benefits and challenges.

Every company has had their own set of struggles scaling its microservice architecture through time, including achieving independent deployability, fault tolerance, highly observable systems, and easily decomposable components among others.

We feel it is important to talk about this as the Lisbon Tech scene grows, so in the next Pipedrive Meetup we want to showcase how different companies have done it, and some of the possible approaches to common struggles when scaling microservices and their learnings.

? Talk 1 - Microservices Observability - How, when and what to measure

Filipe Tavares, Senior Software Engineer at Pipedrive
In Pipedrive, developers are not only responsible for delivering code but also for the maintenance, monitoring, and scalability of what they build. We will be covering some practices and patterns we consider when it comes to observability, that allow us to deliver around 780 deployments per day across 6 distinct data centers.

? Talk 2 - Event-Carried State Transfer Pattern in Microservices

João Comba, Technical Product Owner at Nmbrs BV
It’s a quite common scenario when using microservices that service starts being too dependent on another service's data. That’s when it might come in handy to use this pattern. We have applied it in Nmbrs and I’d like to tell you about our experience.