Are we pretending now it's less complicated to distribute an app a cross a variety of lambda functions? So how are you deploying it? Serverless Framework? SST? Mounting complexity compared to a container... There are also a bunch of services that let you simply host a container, no server to manage. Distributing apps on lambda is a classic trap, and also just because you can, doesn't mean you should. You will quickly find out local development, deployment, debugging, monitoring is all more complex and you will wonder how you got there.
> Are we pretending now it's less complicated to distribute an app a cross a variety of lambda functions?
I treat Lambda purely as compute and ignore everything else related to "serverless". My Lambda's are monolith webapps using Axum Rust framework. Using cargo lambda I generate a static binary, upload to s3 and point the lambda at it. Sometimes I'll package as a docker image so can run in Lambda or locally by passing a `--aws-lambda` flag.
If serving HTML i'll use Function URLS with IAM auth and put a Cloudflare worker in front acting as the gateway. I also serve the static assets from cloudfront bucket i.e. static.example.com. Advantage is I use Cloudflare free tier so get denial-of-wallet prevention when my free credits run out. Using IAM auth also means the lambda doesn't execute if for what ever reason someone discovers the url and tries to DoS it so only get charged for the requests not run time.
Yeah I've worked on a website built on a bunch of Lambdas - something like 150 Lambdas that tied themselves in knots with both HTTP requests and message queues.
I ended up moving a bunch of the logic into an ECS-hosted monolith. Probably cost a bit more (warm-up plugins meant that no customers still cost us money) but it vastly simplified things and made scaling up easier (can't set scaling thresholds with Lambda).
I'd argue that a well thought UX isn't easy to copy in the first place because it's not something that can easily be put into word.
It's the same for a lot of things, I have some clothes that I love because of their, design, quality and more ... something intangible that I have hard time describing and that can easily be explained with: It was done with taste.
AFAIK this does not set a legal precedent as it has been settled and last summer finding is that Anthropic was wrong for "acquiring books illegally" not for training which is fair use.
With model distillation being so effective now nobody actually needs to pirate books to train their models. You can get an open-weight Chinese model and get all that. Or you can just buy the books or buy a library - there are many creative solutions here that aren't piracy and not going to cost you billions of dollars.
The moat right now seems to be the compute resources which might actually be worse for us common folk than a legal moat as we need compute for many more things that aren't LLMs too.
The frontend is hosted on cloudfront, the backend is a lambda and you basically just pay for the database and certificate.
I don't want to manage a server or even a docker image. I just want my code to exist there so I like the idea