https://murateksi.com/tags/serverless/Recent content in Serverless on Murat EksiHugoen-usWed, 12 Nov 2025 09:00:00 +0100https://murateksi.com/posts/serverless-at-scale-lessons/Wed, 12 Nov 2025 09:00:00 +0100https://murateksi.com/posts/serverless-at-scale-lessons/The interesting problems in a serverless system at scale do not announce themselves as serverless problems. They announce themselves as pager alerts at 3 AM, as data inconsistencies discovered by a customer three weeks after they occurred, as deployment pipelines that work perfectly in staging and fail silently in production. When we were running a Nordic telematics platform at 200,000 messages per second across 1.6 million vehicles, the operational challenges had almost nothing to do with Lambda’s execution model.https://murateksi.com/case-studies/nordic-telematics-serverless/Sun, 15 Sep 2024 09:00:00 +0200https://murateksi.com/case-studies/nordic-telematics-serverless/Context A large Nordic telematics provider ran a fleet-management platform for more than 1.6 million commercial vehicles. Each vehicle reports position, diagnostics, and driver behavior several times per minute. At peak, the ingestion pipeline handled about 200,000 messages per second. The existing stack, a mix of dedicated EC2 instances running Kafka and bespoke Java consumers, was seven years old. It worked. It also woke people up twice a week. The business wanted to add three new vehicle platforms in the next fiscal year, which would roughly triple the throughput.https://murateksi.com/case-studies/emea-serverless-bootcamp/Thu, 15 Jun 2023 10:00:00 +0200https://murateksi.com/case-studies/emea-serverless-bootcamp/Context By mid-2022, AWS Professional Services EMEA had a serverless problem that looked like a staffing problem. Every engagement that involved Lambda, EventBridge, or Step Functions required one of four people on the team, or it required one of those four to review the architecture before delivery. The four people were good. They were also at capacity, consistently over-allocated, and becoming a single point of failure for a practice that was growing faster than the expertise could.