https://murateksi.com/tags/aws/Recent content in AWS on Murat EksiHugoen-usThu, 05 Mar 2026 09:00:00 +0100https://murateksi.com/posts/building-ai-ready-architecture/Thu, 05 Mar 2026 09:00:00 +0100https://murateksi.com/posts/building-ai-ready-architecture/The most common question I hear from engineering leaders right now is some version of “how do we add AI to our platform?” It is a reasonable question. It is also usually the wrong first question. The right first question is: can your current architecture support AI workloads reliably? Not just technically, but operationally. In practice, most enterprise architectures were not designed with the access patterns, latency profiles, or cost structures that AI workloads require.https://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/posts/cloud-architecture-business-decisions/Wed, 10 Jul 2024 10:00:00 +0200https://murateksi.com/posts/cloud-architecture-business-decisions/There is a persistent myth in technology organizations that architecture is a purely technical discipline, that decisions about service boundaries, data stores, and deployment strategies belong exclusively to engineers and should be surfaced to business leadership only after they’re made. This is how organizations end up spending three years migrating a monolith to microservices while the market moved. The cost of abstraction is a business question When a team chooses between a managed service and a self-hosted alternative, they are not evaluating technical trade-offs.https://murateksi.com/case-studies/bundesliga-real-time-ml/Mon, 20 Nov 2023 10:00:00 +0100https://murateksi.com/case-studies/bundesliga-real-time-ml/Context The Deutsche Fußball Liga (DFL), which operates the Bundesliga and 2. Bundesliga, runs a digital products group called DFL Digital Sports. They license real-time match data and insights to broadcasters, clubs, and betting partners worldwide. They wanted to add machine-learned match signals, like expected goals, shot quality, pressing intensity, to the live data feed. The requirement was sub-two-second latency from event on the pitch to signal on the broadcast graphic.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.https://murateksi.com/case-studies/security-hub-open-source/Thu, 01 Sep 2022 10:00:00 +0200https://murateksi.com/case-studies/security-hub-open-source/Context The original customer was a large European financial services firm operating across eight AWS accounts, three regions, and two compliance regimes. They needed a unified view of their security posture: findings aggregated, normalized, prioritized, and routed to the right team without manual intervention. AWS Security Hub existed. Their multi-account setup, with a complex organizational structure that had grown through acquisition, meant that the out-of-the-box deployment did not fit. They also had no product budget for a third-party SIEM.