Okay, let's talk about how @awscloud Lambda now supports EFS in this thread.

I see a lot of confusion, vitriol, and concern going around, so let's try and settle it out.

First, this is awesome as far as features go. It unlocks and empowers Lambda use cases that weren't possible yesterday. The 15 minute limit is no longer a hard obstacle for workloads that can checkpoint to disk.

Second, it lets you bring a pile of tooling to your Lambda that won't fit in the runtime environment natively. I'm excited to see what this unlocks!

Third, it means Lambda is now going to be considered in shops where it was previously rejected due to (real or imagined) limitations that this offers a way past.

Now, are there issues? Sure!

I use Route 53 as a database for god's sake; of course people are going to misuse the hell out of it!

Some people will misuse anything. We're super good at it.

It's an @awscloud feature release, so of course they didn't provide guardrails, best practices, giant red warnings about how not to use this, etc. And that's going to cause pain. We can debate whether this is the better path or not, but it will hurt customers.

But on balance this is a net positive.

Everything you could do yesterday in Lambda still works today. If you dislike this, don't use it. Nothing's forcing you to adopt it.

If you're down on NFS as a technology, I hear you, but consider that you may be scaring away new folk.

I'm excited to see people build neat things with this, then @awscloud completely fail to explain them to the market.

This has the potential to be a transformative release. I can't wait to build something terrifying with it.