Infobip Engineering Handbook
Start HereJoin Infobip EngineeringBack to Infobip.com
  • Start Here
    • Infobip At A Glance
    • What We Believe
    • Infobip Engineering Timeline
  • Become A Better Engineer
    • Are You Bored At Work?
    • Steep Learning Curve
    • Freedom To Choose Your (Engineering) Hammer
  • Tech Stack & Architecture
    • The Scale of Our Systems
    • Platform Architecture
    • Observability For Quality
  • How We Code & Deploy
    • Development Flow
    • Testing (And The Freedom To Choose Your Tests)
    • Troubleshooting
    • Incident Management
    • Deployments and Disasters RPG
    • Engineering Enablers
    • A-Team
    • Collaboration Tools
  • Engineering Culture
    • Engineering Principles - In Practice
    • How Growth Impacts Infobip's Values
    • Culture of Approachability
    • Paid Interventions
    • How We Improve Our Culture
    • Employee Feedback Process
  • Key Processes
    • LeSS
    • OKRs
    • One Backlog
  • Self-Managed Teams
    • You Build It, You Own It
    • Examples of Infobip Teams
  • Community
    • Student and Youth Programs
    • Engineering Insider
    • Dev Days Conference
    • Meetups
    • Writing for Engineers
    • Publishing your ideas
    • ShiftMag
    • Hack Days
    • Startup Tribe
    • Infobip Shift Conference
  • Career Development
    • Career Development
    • Switching Positions
  • Benefits
    • Benefits Overview
    • ESOP & Bonuses
    • Engineering Education Budget
    • Learning & Knowledge Sharing
    • Attending Conferences (And Speaking At Them)
    • Good Hardware
    • Vacation & Well-being
  • Hiring & Onboarding
    • Hiring Process - Step by Step
    • Your Onboarding Plan
    • Engineering Onboarding Program
    • Referral Program
  • A Day In The Life - At Infobip
  • An Engineer's Log: No Such Thing as a Typical Day
  • 😊Join Infobip Engineering
  • Impressum
Powered by GitBook
On this page
  1. Tech Stack & Architecture

The Scale of Our Systems

Many engineers arrive to Infobip from smaller companies where they weren't accustomed to the scale Infobip works with. What do we mean by that? Let's talk some numbers. At the moment of writing this handbook, Infobip‘s underlying systems consist of:

  • On-premise equipment installed in 35+ worldwide datacenters which consist of:

  • Over 900 physical servers;

  • Over 29.000 virtual machines;

  • And we are rapidly expanding into cloud (AWS, Azure) where applicable;

  • All supported with over 900 network equipment devices that keep the things connected.

On those VMs we run our microservice architecture, that consists of:

  • Over 1.900 applications (service types)

  • that because of redundancy and architecture run as over 26.500 production application instances.

From data perspective we have:

  • more than 700 relational database servers

  • with more than 9.000 databases

  • containing more than 600.000 objects (tables, Kafka topics, ES indexes)

  • with a total of 600+ TB of working data size.

  • Our central internal data pipeline processes more than 800.000 messages per second going through our Kafka clusters.

Our 100+ teams deploy application-level changes to production over 1.400 times a day, making us truly agile in terms of continuous delivery.

The whole system processes:

  • over 20.000 client messages per second,

  • and transfers over 4.5 Gbps data between our datacenters

From the client side, we have:

  • More than 30.000 clients using our platform through our portal each day

  • and peaks of over 30.000 API requests per second

  • which in the end sends the data to 650+ mobile network operators that we directly connect to

So those are the numbers to have in mind when we talk about Infobip's scale.

PreviousTech Stack & ArchitectureNextPlatform Architecture

Last updated 1 year ago