4 ms·

I don't get it. We run a production headless workload on Vercel and it is slower, has fewer features, yet is more complex and expensive than traditional LAMP se

I don't get it. We run a production headless workload on Vercel and it is slower, has fewer features, yet is more complex and expensive than traditional LAMP server stacks.

leerob 4y ago
Hey there, sorry about this experience. Would love to help investigate – want to send me an email (lee at vercel dot com)?
- diordiderot 4y ago
  Your hustle is bonkers Lee. Content, engagement, etc. Much respect
alex_suzuki 4y ago
It’s called progress.
- rglover 4y ago
  I chuckled. 10/10.
Mo3 4y ago
.. a traditional LAMP stack is not in any way comparable to what Vercel (and other similar services) offer. We don't use Vercel either for it is slower and offers less functionality than competitors but comparing the general concept to a LAMP stack is definitely not valid.
- beatboxrevival 4y ago
  Curious what you use instead and what features you use that Vercel doesn’t have.
  - Mo3 4y ago
    AWS Amplify and Firebase However I have to admit that we don't necessarily run the "target" applications that Vercel was really designed for. We have a full suite of Lambda backend services that communicate with each other in VPCs and over SQS. We have scheduled executions using CloudFront and listen to events happening in several other AWS subservices. Now, we also have two "simpler" React applications that we have actually test-driven on Vercel before, but the cold start time of functions was honestly quite horrible and detrimental in comparison, and the problem that really drove us away very quickly was the lack of integrated database and authentication solutions (e.g. AWS Amplify/DynamoDB/Cognito and Firebase/Firestore/Auth). I know about Railway and 0auth, but we have no interest in using several different providers with uncertain confidence in them just for basic application logic, especially because they don't integrate back into Vercel at all (like e.g. functions being called when a DB record changes) and seem to be more expensive than even AWS itself. If Vercel was more like a "Heroku for serverless", and at the very least offered some of these basic features directly, and then had some good ways of connecting them together, we would potentially reconsider.
solardev 4y ago
Vercel let us get rid of our LAMP stack. No more sys admin or dev ops or updates or Docker or PHP debugger or VMs to maintain. Just the frontend to write, plus a headless CMS. Freed up sooooo much dev time. You no longer need backend devs or devops for simpler sites.

I don't get it. We run a production headless workload on Vercel and it is slower, has fewer features, yet is more complex and expensive than traditional LAMP server stacks.

leerob 4y ago

Hey there, sorry about this experience. Would love to help investigate – want to send me an email (lee at vercel dot com)?

diordiderot 4y ago
Your hustle is bonkers Lee. Content, engagement, etc. Much respect

alex_suzuki 4y ago

It’s called progress.

rglover 4y ago
I chuckled. 10/10.

Mo3 4y ago

.. a traditional LAMP stack is not in any way comparable to what Vercel (and other similar services) offer. We don't use Vercel either for it is slower and offers less functionality than competitors but comparing the general concept to a LAMP stack is definitely not valid.

beatboxrevival 4y ago
Curious what you use instead and what features you use that Vercel doesn’t have.
- Mo3 4y ago
  AWS Amplify and Firebase However I have to admit that we don't necessarily run the "target" applications that Vercel was really designed for. We have a full suite of Lambda backend services that communicate with each other in VPCs and over SQS. We have scheduled executions using CloudFront and listen to events happening in several other AWS subservices. Now, we also have two "simpler" React applications that we have actually test-driven on Vercel before, but the cold start time of functions was honestly quite horrible and detrimental in comparison, and the problem that really drove us away very quickly was the lack of integrated database and authentication solutions (e.g. AWS Amplify/DynamoDB/Cognito and Firebase/Firestore/Auth). I know about Railway and 0auth, but we have no interest in using several different providers with uncertain confidence in them just for basic application logic, especially because they don't integrate back into Vercel at all (like e.g. functions being called when a DB record changes) and seem to be more expensive than even AWS itself. If Vercel was more like a "Heroku for serverless", and at the very least offered some of these basic features directly, and then had some good ways of connecting them together, we would potentially reconsider.

solardev 4y ago

Vercel let us get rid of our LAMP stack. No more sys admin or dev ops or updates or Docker or PHP debugger or VMs to maintain. Just the frontend to write, plus a headless CMS. Freed up sooooo much dev time. You no longer need backend devs or devops for simpler sites.