My advise would be to learn how to set infrastructure and deploy your app on it. Then, and only when you're confortable with infrastructure, you can use these serverless services. So you always know how to deploy on your own infrastructure as an alternative.
To people saying Coolify & a VPS are replacements: no, they aren't - they are fun for pet projects, but they won't substitute for the CDN, DDoS protection and resiliency coming with Netlify, Vercel or Cloudflare.
@@ChristianKolbow 100% agreed, one should choose the tool for the project, I just don't like the narrative that a single self-managed VPS is a generic replacement for such services :)
@@adityaanuragi6916 I haven't used it myself but I've heard really good things. Unfortunately, I can't speeak to the difference between coolify and sst
The only true vendor lock-in for me is overall cloud provider. I took the time to learn AWS services and terraform. I'm no expert but I am able to do most of the things the 2nd tier providers do for you. Most of those services are just wrappers over the larger provider. Aws and terraform make those tasks pretty approachable.
Each of them has its own advantages and appropriate uses. Recently, I received a notification that one of my open-source projects would no longer be supported under their open-source plan. This made me realize that my website was too dependent on their ecosystem. As a result, I am reconsidering the architecture and leaning towards separating the website and APIs. This separation will make it easier to move the website and APIs independently, reducing reliance on a single host and framework.
In my opinion I have all my projects in vercel, both clients and own and I only pay the 20$/m plan and as is well known is one of the most efficient platforms in terms of user experience for devs. And I think they have improved a lot the security and the way to avoid you get a 95k invoice haha, good video James thanks for giving your opinion is clear and concise.
4:17 nah doesn't work that way this will only happen if you're on serverless since you don't have control over you spend, for a vps you pay a fixed amount for the resources you need. and if someone ddos-ed you you server will go down 🤷
In my entire 14 year career, I have migrated a database once... The reason was because we decided to build the app with a lightweight service first instead of an industry standard well tested service.
My advise would be to learn how to set infrastructure and deploy your app on it. Then, and only when you're confortable with infrastructure, you can use these serverless services. So you always know how to deploy on your own infrastructure as an alternative.
To people saying Coolify & a VPS are replacements: no, they aren't - they are fun for pet projects, but they won't substitute for the CDN, DDoS protection and resiliency coming with Netlify, Vercel or Cloudflare.
That is true. But many who follow here don't have a project that really relies on CDN or DDOS protection.
@@ChristianKolbow 100% agreed, one should choose the tool for the project, I just don't like the narrative that a single self-managed VPS is a generic replacement for such services :)
Agreed with all of the above. I think I need to check out Coolify though. I've heard good things!
@@JamesQQuick There is another tool. CapRover. Easier to use, but with minor limitations. I personally like coolify.
Coolify seems a promising middle ground which I will certainly consider on a vps.
I've been told several times I need to try it out. Maybe it's time!
@@JamesQQuick it's definitely time. i use coolify on hetzner servers. Coolify is really fun
Dokploy is a pretty good option too
What about sst?
PS - I haven't used the cloud very much and don't even fully understand the difference between coolify and sst
@@adityaanuragi6916 I haven't used it myself but I've heard really good things. Unfortunately, I can't speeak to the difference between coolify and sst
The only true vendor lock-in for me is overall cloud provider. I took the time to learn AWS services and terraform. I'm no expert but I am able to do most of the things the 2nd tier providers do for you. Most of those services are just wrappers over the larger provider. Aws and terraform make those tasks pretty approachable.
Each of them has its own advantages and appropriate uses. Recently, I received a notification that one of my open-source projects would no longer be supported under their open-source plan. This made me realize that my website was too dependent on their ecosystem. As a result, I am reconsidering the architecture and leaning towards separating the website and APIs. This separation will make it easier to move the website and APIs independently, reducing reliance on a single host and framework.
Oh interesting. Where are you looking at moving?
Serious question, why are JavaScript developers so afraid of setting up infrastructure?
Stupid question.
We just have a higher drive to ship a working product day one.
@@WebDevCody I can do the same and won't come back to tell people I was wrong later.
@@siya.abc123 🤫
@@WebDevCodyyou mean garbage you'll never be able to scale
In my opinion I have all my projects in vercel, both clients and own and I only pay the 20$/m plan and as is well known is one of the most efficient platforms in terms of user experience for devs. And I think they have improved a lot the security and the way to avoid you get a 95k invoice haha, good video James thanks for giving your opinion is clear and concise.
4:17 nah doesn't work that way this will only happen if you're on serverless since you don't have control over you spend, for a vps you pay a fixed amount for the resources you need. and if someone ddos-ed you you server will go down 🤷
This is something I will eventual look into. Right now I'm using supabase to handle auth, storage and DB. Hopefully I never have to change.
In my entire 14 year career, I have migrated a database once... The reason was because we decided to build the app with a lightweight service first instead of an industry standard well tested service.
Coolify + VPS = Problem Solved
it's fascinating how people want tight integration but then also avoid vendor lock it, to me they both are somewhat opposite
Base on the title Only, yes
We don't want apologies.
They're done with.
Coolify bro
I think we should only move away from Cloudflare just because it is not good for the internet to be to centralised in one big organization.
I rather not build at all that deploy my stuff on a vendor locked in platform. I'll proudly sacrifice my time and skills
Yes. Absolutely avoid. Just learn on how to use a vps and nginx or caddy
Caddy is the easiest.