Services
Engineering Architecture
Architecture, scalability, APIs, databases and technical strategy — the system underneath the product.
Engineering Architecture
Architecture, scalability, APIs, databases and technical strategy — the system underneath the product.
The system underneath: services, APIs, the data model, and the path from today's load to ten times it.
Work this is drawn from
- Event-driven under load. At Naqrat I rebuilt a marketing-conversion API as an event-driven system on Laravel Octane, taking response time from ~6 seconds to ~35 ms while handling millions of events.
- A platform failing under load. At iStoria I took over an English-learning platform with 2.5M users and 165M+ tracking records and resolved its performance issues within three months, moving the backend toward microservices.
- Infrastructure that costs less. At ID8 Media I migrated a platform from GKE to Cloud Run: deploys from 10–15 minutes to about 60–90 seconds, and 30–60% lower infrastructure cost.
- The foundation of a platform. At Lun Startup Studio I built the base of Shogol, with its full architecture and database.
Typical engagements
System and API design for a new product, a data model review before it becomes hard to change, a scaling plan for traffic that is about to arrive, or an infrastructure migration.
What is included6
- System design
- API design
- Databases and data modelling
- Event-driven architecture
- Scalability
- Infrastructure and cost