Storage on Vercel • Hacker News Board

Re: Storage on Vercel

#141

Post by teaearlgraycold » Tue, May 02, 2023, 6:01 PM UTC

tudorg wrote: post #120

teaearlgraycold wrote: post #76

Earlier quoted context omitted.

I don't quite follow, but I totally believe that solutions to these problems can be made and maybe your solution really does work well. The issue is that solutions here are not standard yet and thus there will not be much collective knowledge to draw upon. I'd much rather ask engineers to fix age-old RDBMS issues than novel ones that are unsearchable with solutions whose repercussions are not yet known. There's also…

> The issue is that solutions here are not standard yet and thus there will not be much collective knowledge to draw upon. I'd much rather ask engineers to fix age-old RDBMS issues than novel ones that are unsearchable with solutions whose repercussions are not yet known. I definitely understand this. One step at a time, but I think we can move incrementally to a workflow that is much better that what we have today,…

Hey, someone’s got to pave the way!

Re: Storage on Vercel

#142

Post by rykuno » Wed, May 03, 2023, 4:54 PM UTC

le_sigh_88 wrote: post #113

I really can't stand this company and it's business model. It preys on inexperienced engineers, locks them into an ecosystem of SaaS products that abstracts away important concepts they should learn, and charges an absolutely absurd premium while doing it. No serious company is ever going to use these criminally expensive software, so it's quite clear what their target market is. Unfortunately, they have such a stron…

> It preys on inexperienced engineers

For a weekend/side project that needs db and storage, why would I spend days correctly setting up, securing, and provisioning all my infra when I could just pay a little extra and never worry about it?

When creating a new project I wear all hats. Project management, UX/UI designing, Frontend, Backend, Infra, User testing, security.

Having to maintain multiple projects that all bring income in as a solo developer wearing all the hats is very time consuming, this is an absolute godsend and I'll pay for the DX happily.

Re: Storage on Vercel

#143

Post by zenstack » Fri, May 05, 2023, 9:19 AM UTC

pier25 wrote: post #93

> Simultaneously, as the world moves away from monolithic architectures to composable ones It's been the opposite for me. Back around 2015-2016 I was very excited about cloud functions, serverless, etc, but these past years I've gone back to mostly running VMs with regular persistent apps. Complexity has gone down considerably and there's zero lock in. With Docker I have full control over the platform and can run the…

We have been there too. We feel so much happier after abandoning microservices in our previous product. I also wrote a post about it: “where did the microsservice go”(https://zenstack.dev/blog/microservice)

Re: Storage on Vercel

#144

Post by ncphillips » Fri, May 05, 2023, 10:28 AM UTC

rykuno wrote: post #142

le_sigh_88 wrote: post #113

I really can't stand this company and it's business model. It preys on inexperienced engineers, locks them into an ecosystem of SaaS products that abstracts away important concepts they should learn, and charges an absolutely absurd premium while doing it. No serious company is ever going to use these criminally expensive software, so it's quite clear what their target market is. Unfortunately, they have such a stron…

> It preys on inexperienced engineers For a weekend/side project that needs db and storage, why would I spend days correctly setting up, securing, and provisioning all my infra when I could just pay a little extra and never worry about it? When creating a new project I wear all hats. Project management, UX/UI designing, Frontend, Backend, Infra, User testing, security. Having to maintain multiple projects that all br…

I definitely agree with this

But also I just started a side project with Rails. I got a CI/CD production environment with GitHub Actions, Postgres, Redis, sidekiq, and storage on Fly.io in an hour or two.

The thing that makes me more comfortable here is that none of my application code references Fly.io at all. If the project needs to grow beyond Fly I just change some environment variables and migrate the data.