Yan Cui

Yan Cui

@theburningmonk.com

I help engineers build better software faster with serverless | AWS Serverless Hero Newsletter: https://theburningmonk.com/subscribe

2K followers333 following205 posts

Yan Cui reposted

I have not paid a ton of attention to the uproar over RTO policies, bc we are all in on distributed teams and not going back. My impression (via social media) has been that these were shadow layoffs. Last month I asked an investor why they are doing RTO. He said: "Retention, mostly. And morale."

Saying "coding is dead" is missing the point. Coding isn’t just about producing code, it’s also a way of thinking. It teaches us structure, systems thinking, abstractions and problem decomposition. If you don’t learn those skills, AI won’t make you productive, it’ll make you dependent.

View full thread

You can also put CloudFront in front of your API and cache and handle these preflight requests at a lower cost. This doesn’t eliminate preflight request-related charges entirely, but it goes a long way to minimize it.

View full thread

Of course, subdomains aren’t inherently bad, and many organizations prefer them to organize multiple APIs and environments. And maybe even let teams have their own subdomains and allow them to be more autonomous.

Every time the browser makes a cross-origin request, it first makes a preflight request to make sure it can actually send the request. Since API Gateway charges per request, you’re billed for both the preflight and the main request.

I'm speaking at AWS Community Day Romania this April, in the beautiful city of Timisoara. Hope to see you there 👋 Their CFP is open until February, so there's still time to submit your talk. More details here: aws-community.ro

View full thread

I saw some WAF charges on my bill and it took me a while to work out where they came from because I couldn't see any web ACLs in the WAF console! To see if you have any classic web ACLs, go to the WAF Classic console: https://buff.ly/4gElXQa and either delete or migrate them before Sep 30, 2025.

AWS WAF Classic (or v1) was recently deprecated, and classic Web ACLs no longer appear in the new WAF console. So it's easy to miss any classic web ACLs you have that are no longer in use, especially if you don't spend much time in the AWS console because you do everything through IaC!

I just burned $10,000 on marketing, and it taught me the hardest lesson of my career. I spent $10,000 on an ad agency and only got 3 sign-ups for my workshop, despite months of ad campaigns and plenty of clicks. Yet, 30% of students joined through word of mouth, another 30% through social media.

Here’s what I learned (the hard way)... 1) Online ads are easy to measure, but they are not always the most effective channels. 2) Clicks is a bullsh*t metric; don't get distracted by it. 3) Trust beats clicks/impressions. The most powerful marketing comes from relationships, not campaigns.

An eng manager at Netflix once told me that "It'd cost 7x to run Netflix if Netflix ran on Lambda". But what he said next was even more insightful. "But, not everything at Netflix runs at Netflix scale." And that's true for most enterprises!

View full thread

But outside of that critical path, Lambda was used heavily across many workloads, including critical business areas like payment processing & account management. Even some services on the critical path were able to use Lambda and API Gateway because their API responses were highly cacheable.

So a quick rule-of-thumb from a throughput POV is: * Stable high-traffic workloads => containers * Bursty, occasional workloads => lambda And don't forget about caching. It's literally a cheat code for building scalable and high-performance systems!

An eng manager at Netflix once told me that "It'd cost 7x to run Netflix if Netflix ran on Lambda". But what he said next was even more insightful. "But, not everything at Netflix runs at Netflix scale." And that's true for most enterprises!

When I was at DAZN, we didn't operate at Netflix scale, but we still had to deal with millions of concurrent users at peak. Services along our critical path will experience sudden spikes from hundreds reqs/sec to tens of thousands reqs/sec in a matter of seconds.