Serverless is often touted as a panacea for software delivery. It will let you write code must faster, deliver to production faster, be cheaper to run, make the tea, fix world hunger, etc. It's not, of course, but it can still be a good way to go in certain circumstances.
So many tutorials and examples are written from the point of view of a single endpoint, or at best a couple. And as an API only service, with no client using it. That's great for absolute starters, but real life applications very quickly outgrow it.
I'm going to attempt a series of articles that cover how to write a larger Serverless application, with a reasonable architecture to the backend, services that depend on each other, databases/queues/etc, a web frontend that can talk to it, and so on. There will also be an eye on how the actual code can be structured.
These will be more aimed at solo or indie developers, rather than larger companies. As such, there will be more emphasis on free tooling and keeping complexity down - for example I'll probably aim for a monorepo because that's easier for a small set of people to handle.
I can't guarantee it'll work. I can't promise that this will be any better than anything else out there. But we'll see how it goes.