Renno Reinurm, Pipedrive At Pipedrive, we designed all of our internal processes with a “self-service attitude” that gives our developers the flexibility to build and test new services as often as they like. Each developer has a Docker Desktop environment, with the ability to self-provision an on-demand isolated sandbox environment on top of Docker Enterprise. Tied to our CI/CD process, Pipedrive manages a fleet of microservices across multiple datacenters where we do 250+ deployments a day, 50 of them in our production environment. In this talk we’ll show you how this works, what the day in the life a developer looks like at Pipedrive, and how how several Docker products influenced the development processes. We’ll also explore the architectural decisions and reasoning around it. And finally, if the demo-gods are merciful, then we’ll do some hands-on demonstration of the environment.

1. A Day in the Life of a
Developer at
Pipedrive with
Docker Enterprise

2. Pipedrive - SaaS
DockerEE clusters
8
Projects
~400 Datacenters
3

3. •
•
•
•
•
Separation of duties

4. Demo ...

5. Testbox setup

6. ready-for-deploy

7. Supply Chain
STAGING PRODUCTION
SANDBOX

8. Number of Sucessful deployments

9. 21 3
Wrap up

10. Check out these sessions: