Monolith to Microservices on AWS

Microservices on AWS

Each area scales on its own.

Every functional area of the monolith became an independent service on AWS. Business logic stayed intact, and each service is developed, deployed and scaled separately.

Strangler pattern

Zero downtime for Tabulate users.

New microservices ran alongside the monolith, and traffic moved to them step by step, so restaurants and bars using Tabulate never saw an outage during the migration.

Docker

Same behavior in every environment.

Each service is packaged into a Docker container with its own libraries, system tools and runtime, so it runs identically from development to production.

Jenkins CI/CD

From one release a day to many per hour.

Jenkins pipelines and automated configuration management build, test and release every service independently, without waiting for the rest of the app.

Infrastructure as code

Infra changes as easy as code changes.

Infrastructure is defined in code with CI/CD for each service, so changes are repeatable and made with the same tools developers already use every day.

Security & observability

Every service protected and measured.

Security at network, container and application levels, plus observability that shows each service's SLA, dependencies, response times and latency.

Releases multiple times per hour, compared to once per day.

Development teams experiment with new features and innovate at a much faster pace, with CI/CD in place for every service.

Zero downtime during the migration.

Each service scales horizontally on its own, errors are minimized, and disaster recovery and QA automation are in place.

A more stable, user-friendly application.

Tabulate's customers get new features faster on a platform that is notably more stable and more attractive to end users.