This document provides information about Marten Meikop, including his hobbies, professional career, and role at Pipedrive. It then summarizes key details about Pipedrive's engineering including the number of employees, customers, offices, and requests processed per week. It outlines the evolution of Pipedrive's architecture from a PHP monolith to a microservices architecture running across multiple data centers.

2. About me
● Hobbies
○ Mindsports (chess, checkers)
○ Programming (vint.ee - 30 online
games)
● Wrote first line of code in 1999
● Professional career:
○ C coding for Bang & Olufsen
○ Software architect in Telia
○ Site lead in Proekspert
○ Startup founder
(atmosphere.ee)

3. 90k
Customers in
170 countries
600+
Employees
8
Offices
Pipedrive - The best sales CRM
2010
Founded
$90m
Total Venture Capital
Funding

4. 70+
Live deployments
every day
2
Data centers
1 billion
Requests
per week
Pipedrive Engineering in Numbers
250
People in
Engineering
250
Back-end
Services
1
Management
region

5. The Beginning (2010)
PHP framework
CodeIgniter
Percona Server
for MySQL
Schema per customer
database architecture
LEMP Stack

6. Natural Growth (2015)
Webapp
Websocket
Microservices
Microservice
DatabasePipedrive DB
Data Center in US
Company DB

7. Megaparsec: Moving to
Multi-datacenter environment (2016-2018)
The Needs Challenges
Serving end users from physically
closer location
Legal aspects (GDPR)
Not to put all eggs in one basket
Running out of physical space - one DC
might grow too big
Gateway
Service Discovery
Backoffice / management
CI/CD multi-dc support
Monitoring
1 parsec = 3.0857x1016m

8. Customer data in one DC
PipedriveDB in multi-master sync between datacenters
Universal domain name (pipedrive.com, not
eu.pipedrive.com)
Geolocation routing
Multi-DC architecture: Key concepts
Datacenter 1 Datacenter 2
Gateway Gateway

9. Our own custom public gateway
Written in NodeJS
User authentication
(Crypto cookie, api-token, Oauth)
Rate limiting
Service discovery & load balancing
Enriching headers
Producing full access log
Routing between Datacenters

10. Barista
eu-central-1
F5
BaristaIdentity
Microservice A
us-east-1
F5
BaristaIdentity
Microservice B

11. Pipedrive tech stack

12. ● Monolith split continues
Are we already there?
● Kubernetes
• Service mesh
• Sidecar
• Vault (Security between
microservices)
● Event driven architecture (Kafka)
● Composite API
● Independent DC-s

13. Thank you.
Marten Meikop · Engineering Manager @ Core Tribe Pipedrive
Any questions?
Email me at marten.meikop@pipedrive.com