About the service
I'm a serverless developer and I write backends that live in functions, not on servers that need constant monitoring. My daily work is AWS Lambda, Google Cloud Functions, and Azure Functions, connected through API Gateway, HTTP triggers, queues, and event buses. First I design the flow: which event fires, which function processes it, what it writes next, and only then I start coding, because in serverless the architecture is the product. Most of what I do is Node.js and TypeScript, and where Python ecosystem makes more sense I use Python, all organized as small single-task handlers that are easy to read and cheap to run.
I'm most valuable in event-driven work. I connect functions to SQS, SNS, EventBridge, Pub/Sub, and Kafka, add dead-letter queues and idempotency so retries don't charge twice or duplicate records, and keep cold starts under control through reasonable memory allocation, provisioned concurrency, and lightweight dependencies. Cost matters to me as much as latency: the serverless bill should drop almost to zero when there's no traffic, and I tune timeouts, batch sizes, and concurrency limits to make that happen. Everything ships as infrastructure-as-code — SAM, Serverless Framework, CDK, or Terraform, so the stack is reproducible, versioned, and safely rolls back.
I also handle what people remember only when production breaks: structured logs, tracing between functions, error alarms and throttling, staged deployments, and IAM with least privilege so each function touches only what it actually needs. Whether you need one webhook handler, a full event API, or migration of a heavy monolith into a set of focused functions — I'll take you from design to deployed and observable solution.
— AWS Lambda, Google Cloud Functions, Azure Functions
— Event-driven APIs on API Gateway and HTTP triggers
— Queues and events: SQS, SNS, EventBridge, Pub/Sub, Kafka
— Handlers in Node.js and TypeScript, Python where appropriate
— Cold start tuning, concurrency, and cost optimization
— Infrastructure-as-code: SAM, Serverless Framework, CDK, Terraform
— Observability: logs, tracing, alarms, least-privilege IAM
I'm most valuable in event-driven work. I connect functions to SQS, SNS, EventBridge, Pub/Sub, and Kafka, add dead-letter queues and idempotency so retries don't charge twice or duplicate records, and keep cold starts under control through reasonable memory allocation, provisioned concurrency, and lightweight dependencies. Cost matters to me as much as latency: the serverless bill should drop almost to zero when there's no traffic, and I tune timeouts, batch sizes, and concurrency limits to make that happen. Everything ships as infrastructure-as-code — SAM, Serverless Framework, CDK, or Terraform, so the stack is reproducible, versioned, and safely rolls back.
I also handle what people remember only when production breaks: structured logs, tracing between functions, error alarms and throttling, staged deployments, and IAM with least privilege so each function touches only what it actually needs. Whether you need one webhook handler, a full event API, or migration of a heavy monolith into a set of focused functions — I'll take you from design to deployed and observable solution.
— AWS Lambda, Google Cloud Functions, Azure Functions
— Event-driven APIs on API Gateway and HTTP triggers
— Queues and events: SQS, SNS, EventBridge, Pub/Sub, Kafka
— Handlers in Node.js and TypeScript, Python where appropriate
— Cold start tuning, concurrency, and cost optimization
— Infrastructure-as-code: SAM, Serverless Framework, CDK, Terraform
— Observability: logs, tracing, alarms, least-privilege IAM
