That's not vibecoding anymore.

True microservices have never been tried.

Do I smell a true Scotsman here?

Not everyone that smells like peaty whisky is a Scotsman!

Like some bizarro world of Unix Philosophy-esque tools mashed into the approach people have when creating "serverless" applications?

Or define what a true microservice is because I think there are many takes on that.

My friend, it's possible you missed the joke.

Oh, I did indeed miss it facepalm.

Vibecoding is just not looking at the code. You can not know code, but still know what to ask for. That's already a thing we expect of LLM use; if you don't ask it right, give the right context, etc, it's not as useful. So give it the right architectural guidelines, compartmentalize your use of it, and you'll get good results.

Then we should be seeing something already, this approach exists for many years by the serverless folks. Vibe coding it should be rather straightforward since there's loads of tutorials, example code, etc. available.

The problem of this approach is the problem of "correct microservices". You are moving complexity up from the application layer to the architecture layer. If you ever had to work on "correct microservices", you will know that even for humans it becomes hard to have a mental model and reason about the system as a whole. Good luck having your LLMs tackle it, when at times the best way to describe those services is through diagrams instead of text descriptions.