4 ms·

No, I see it the other way. This is a great business model and potentially product too. A fully integrated platform lets you sell libraries, infrastructure and

No, I see it the other way. This is a great business model and potentially product too. A fully integrated platform lets you sell libraries, infrastructure and support all in one package. Rather than you configuring a Laravel storage provider to use Redis and your developer configuring infra and permissions, you could just click a checkbox in an admin panel. The service could even generate you code to act as your interface. Rather than setting up a log provider to go to OpenTelemetry and having an exporter pipe to Datadog, you hit a button which replaces the logger in your DI stack with all the wiring handled already. For an org that wants to move FAST it could be a really compelling product. It's also very tight vendor lock in. For some contexts, that's absolutely fine. It's something I had an idea of doing in the NodeJS space, but I'm too wary to start my own startup. Basically designing a combined DI framework and bundling tool, then selling infrastructure adapters on top of that.

upmostly 2y ago
Could not agree more. In fact, we’re tackling this exact problem with Hypership (https://hypership.dev https://hypership.dev) but in the React/Next.js and JavaScript space. Infra, auth, events, analytics, forms, database, API, everything you need to ship a product, all configurable in minutes with no glue code. Laravel is 100% going all in on their cloud, tightly integrating their entire ecosystem. I mean, have you seen how many products they have?! The trade-off is clear: speed vs lock-in. I'm betting on flexibility without the setup overhead. Agencies will gobble this service offering up in no time.
- o1o1o1 2y ago
  May I ask how Hypership differs from Vercel etc? Coincidentally I'm currently looking for a new hoster / platform to start a new project with (probably nextjs or laravel) but having a difficult time deciding on one of the modern cloud providers like you because of the heavy vendor lock-in and hidden costs collecting in the shadows and threatening to crush my product before it can break even. How would I prevent this from happening using e.g. Hypership?
echelon 2y ago
Sounds like a great way to get locked into paying for more than you need. There's a venerable history of this, from Oracle to Heroku. Solve today's problems slightly faster (minus a few days of plateng/DevOps work), and forever be exposed to having the screws tightened. Hard pass. Infra should be commodity and replete with dozens of like kinded alternatives. The worst offenders are those fancy JS CI/CD, one-click deploy solutions that cost 10,000x the underlying primitives. Roll your own and save yourself.
- tonyhart7 2y ago
  true, don't listen to these guys lol these guys have bias because that's their entire bussiness model, open source cloud deploy is the future and not tied only to laravel deployment but agnostic scalable + open source is the way
- thomaslord 2y ago
  I disagree, at least in this specific context. With Laravel Cloud you build a standard Laravel application which can be deployed anywhere, then use the service to handle DevOps for you. Because it doesn't include any unique services of its own, you can always decide to hire a DevOps team and run all the required services yourself. You're totally correct in scenarios where you need to build your project around the service, but this service is specifically a DevOps shortcut with no lock-in. Should your Fortune 500 company use this? Maybe not. Should a one-man dev shop use this? Quite possibly - you pay for the convenience, but it frees up more time to improve your application.

upmostly 2y ago

Could not agree more. In fact, we’re tackling this exact problem with Hypership (https://hypership.dev https://hypership.dev) but in the React/Next.js and JavaScript space. Infra, auth, events, analytics, forms, database, API, everything you need to ship a product, all configurable in minutes with no glue code. Laravel is 100% going all in on their cloud, tightly integrating their entire ecosystem. I mean, have you seen how many products they have?! The trade-off is clear: speed vs lock-in. I'm betting on flexibility without the setup overhead. Agencies will gobble this service offering up in no time.

o1o1o1 2y ago
May I ask how Hypership differs from Vercel etc? Coincidentally I'm currently looking for a new hoster / platform to start a new project with (probably nextjs or laravel) but having a difficult time deciding on one of the modern cloud providers like you because of the heavy vendor lock-in and hidden costs collecting in the shadows and threatening to crush my product before it can break even. How would I prevent this from happening using e.g. Hypership?

echelon 2y ago

Sounds like a great way to get locked into paying for more than you need. There's a venerable history of this, from Oracle to Heroku. Solve today's problems slightly faster (minus a few days of plateng/DevOps work), and forever be exposed to having the screws tightened. Hard pass. Infra should be commodity and replete with dozens of like kinded alternatives. The worst offenders are those fancy JS CI/CD, one-click deploy solutions that cost 10,000x the underlying primitives. Roll your own and save yourself.

tonyhart7 2y ago
true, don't listen to these guys lol these guys have bias because that's their entire bussiness model, open source cloud deploy is the future and not tied only to laravel deployment but agnostic scalable + open source is the way
thomaslord 2y ago
I disagree, at least in this specific context. With Laravel Cloud you build a standard Laravel application which can be deployed anywhere, then use the service to handle DevOps for you. Because it doesn't include any unique services of its own, you can always decide to hire a DevOps team and run all the required services yourself. You're totally correct in scenarios where you need to build your project around the service, but this service is specifically a DevOps shortcut with no lock-in. Should your Fortune 500 company use this? Maybe not. Should a one-man dev shop use this? Quite possibly - you pay for the convenience, but it frees up more time to improve your application.