Vercel Build Output API: Infrastructure-as-Filesystem
vercel.com
vercel.com
I wouldn't be surprised if Cloudflare or someone wanted to acquire them soon if they successfully pull off cross-language support. Heroku really fumbled the ball here, despite having a multi-year headstart.
I think open-sourcing it wouldn't be beneficial. More work for @dang to moderate the content and feedback to remain organic.
I haven't tried Vercel, but with App Platform it seems like I get everything Vercel offers, but on top of that I can add managed databases, spaces, functions, and have overall more flexibility.
I've also contemplated a Cloudflare acquisition or merger with Vercel several times. Some of their products compete with each other, but I think they target very different customers.
But maybe this is shifting as Vercel moves towards the back of the stack and Cloudflare moves towards the front.
I expected the base Python use case to support common Python function deploy setups, say Flask, FastAPI / Starlette, etc.
It didn't seem like that's actually possible (if it is, the docs should mention it!)... and instead this is "Advanced Usage".
I really don't consider Hello World running in Flask to be "Advanced Usage".
But the alternative with the verbosity of using BaseHTTPRequestHandler with no framework is just nuts. Of course, no one is doing that on other platforms.
Python is still a second-class citizen on Vercel.
Heroku made this smooth... a decade ago... I really don't understand why Vercel doesn't make a serious investment in Python. It would unlock so much more potential for their platform. [Vercel, my email is in bio if you're listening ;).]
I currently use [1] to be able to deploy a nextjs app to AWS with API Gateway. Would be nice to have standard patterns for cloud deployments for mulitple frameworks.
[1] https://github.com/serverless-nextjs/serverless-next.js/blob...
[1] https://fab.dev/
edit: I see from reddit discussions it is initially cheaper but quickly gets even more expensive than AWS.
https://www.reddit.com/r/nextjs/comments/ra1whm/bye_vercel_h...
imagine just having a repo of your web app, and just committing via git is enough to get it online, and scalable.
imagine forgoing these knowledge because you are lazy only to pay it out of your pocket when you realize vercel's pricing is significantly larger for your employers.
its not going to be fun when your startup runs out of money and you can't afford vercel anymore.
Or... Just use vercel or similar packaged solution.
AWS has everything you could ever need, but that means you have a ton of trade offs to consider whenever you want to start something new.
I often want a one-off website deployed live on the internet to test something. For AWS I’m juggling in my head:
- Load Balancers
- API Gateway
- CloudFront
- S3 for static files
- Route 53
- Lambda config (or use Serverless to manage this or maybe ECS or EKS or maybe just spin up an EC2 instance…)
- Elastic beanstalk or Amplify instead of or in addition to the above?
- Cloudformation or Terraform to manage it? Or just build tech debt by doing it all manually?
- And how are we automating deployments? Maybe something custom in GitHub actions? I know AWS has some offerings here but they were cludgey last time I tried them.
Or with Vercel I:
- Type “vercel” and hit enter in the folder containing my web app.
They’re completely different worlds.
Sometimes I need the full power of AWS. Often I don’t.
In addition you can use Pulumi, Terraform, CDK but you could just do it from the web console and then generate those.
I don't know for me these are not enough of a pain for me to move off AWS.
That's why people pay a premium for vercel(and other similar services like heroku) for hosting.
If you are starting out in AWS and you are overwhelmed its understandable but the if barrier to entry to Vercel is much lower you are not going to be differentiating yourself in the job market either.
The cost savings in the long run of having good AWS knowledge is always going to shine over whatever short term cognitive lift perceived by inexperienced AWS devs.
I would actually put Vercel in a lower tier of cloud practioners. For startups, that might be just what you need since there is a 99% chance you won't ever hit its unlimited tier limits (hyperbole).
I've used AWS Lambda professionally for years, Vercel is a totally different beast. I recently span-up a hobby project recently on Vercel rather than AWS Lambda (using Serverless Framework) to try out next.js and it took about 10 minutes to get it working whereas AWS Lambda would have taken a lot longer.
If you've been really using Lambda on AWS and still struggling with IAM/VPC I would have to chalk this up as not amazon's fault