Amazon ECS / Fargate Deployment
Containers that deploy without downtime, and that stop deploying when the new version is broken.
From $649 3–7 days
Lambda behind API Gateway, with the database connections and the failure paths thought through.
From $549
Typically $549–$1,599, fixed in writing before anything starts.
What moves it up
Serverless fails in a way that looks like success right up until traffic arrives. A function that talks to RDS opens a connection per invocation, so an API that scales to two hundred concurrent executions opens two hundred connections to a database configured for eighty-seven, and the errors that follow look like database problems rather than architecture ones. Alongside that, API Gateway gives up at twenty-nine seconds regardless of the fifteen-minute timeout on the function behind it, and an async invocation that fails with no dead-letter queue simply disappears.
aws lambda get-function-configuration --query '[Timeout,MemorySize,VpcConfig]'SELECT count(*) FROM pg_stat_activity, sampled while the API is under load rather than idleCloudWatch metrics for Throttles and ConcurrentExecutions against the account limitaws lambda get-function-event-invoke-config — whether a failed async invoke goes anywhere at allUsually less than people expect, and when they do bite it is often because the function is VPC-attached or the package is large rather than because Lambda is slow. Both are fixable. If the workload genuinely cannot tolerate any variance, provisioned concurrency exists and it costs money — I will tell you which situation you are in.
At low and spiky traffic, dramatically. At steady high traffic, often not — there is a crossover point and it is worth knowing which side of it you are on before you commit to the architecture rather than after.
Yes, with connection pooling in front of it. Without that it is the single most common way a serverless API falls over under load, and it is the first thing this work addresses rather than an optimisation left for later.
With SAM or a similar local emulator for the function and the API layer, and real AWS services for anything stateful. Emulating the whole cloud locally is a rabbit hole that produces an environment which agrees with nothing.
Containers that deploy without downtime, and that stop deploying when the new version is broken.
From $649 3–7 days
Subnets, routing and security groups laid out so the next person can read them.
From $349 2–4 days
Tell me what you are running and I will come back with a fixed price and a date. If it turns out you do not need this, I will say that instead.
Prefer to talk? Book a free call ↗ · Or hire me on Upwork ↗ · Typical reply within one business day.
Sunday to Thursday, 09:00–18:00 EET. Outside that I will still look, but I will not promise a time.
One person, one time zone. If round-the-clock cover is what you need, you need a team, and I will say so rather than sell you a plan that cannot deliver it.
You pay Amazon directly and you keep control of the account. Nothing here resells your infrastructure or sits between you and your own billing.
Every service page lists exactly what pushes a quote above it, before you ask. You get a fixed number in writing before any work begins.