4 ms·

I love how everyone always shat on PHP (the original serverless technology...convince me otherwise) and now everyone is scrambling to reinvent PHP.

toddh 8y ago
Don't forget perl and CGI as the even more original serverless tech.
- fuball63 8y ago
  That's why I made http://bigcgi.com http://bigcgi.com. It's just CGI behind a reverse proxy that handles file sync between hosts. My blog runs on it.
  - captainperl 8y ago
    BigCGI looks interesting. I signed up for your newsletter.
    - fuball63 8y ago
      Thats great, thanks! Im working on getting the blog up and running, and plan to cross post there, along with any news about the platform. Feel free to email me any suggestions... my address is on the bigcgi site.
CharlesW 8y ago
> I love how everyone always shat on PHP (the original serverless technology... I like and use PHP, and you absolutely can create serverless solutions with PHP, but you may be confusing "serverless" with "stateless". PHP itself is in no way intrinsically more "serverless" than other options.
mypalmike 8y ago
Does PHP automatically scale infrastructure to meet demand? Can you bring up 1000 instances of your service for spikes in volume? And then scale back down when the spike is over? Without writing code? Nobody is reinventing PHP.
- CamTin 8y ago
  Totally stateless PHP apps (retrieving and storing state at the top and bottom of each request) plus autoscaling based on CPU load starts to look pretty close to Lambdas + scheduled tasks to keep them "warm". This is how most LAMP apps are/were built, notably Wordpress. The real pain point in any auto-scaling/cloud/serverless application is and will probably always be the stateful bits. I think the first cloud provider to really figure out this killer bit will be the ultimate winner of the cloud wars. It will probably look something like Amazon's "Aurora Serverless" but be even more frictionless.
- bartread 8y ago
  > Does PHP automatically scale infrastructure to meet demand? Can you bring up 1000 instances of your service for spikes in volume? And then scale back down when the spike is over? Without writing code? People talk about this a lot. I wonder, for what percentage of systems, this kind of scalability is really a requirement. I also wonder what percentage of devs work on these kind of systems.

toddh 8y ago

Don't forget perl and CGI as the even more original serverless tech.

fuball63 8y ago
That's why I made http://bigcgi.com http://bigcgi.com. It's just CGI behind a reverse proxy that handles file sync between hosts. My blog runs on it.
- captainperl 8y ago
  BigCGI looks interesting. I signed up for your newsletter.
  - fuball63 8y ago
    Thats great, thanks! Im working on getting the blog up and running, and plan to cross post there, along with any news about the platform. Feel free to email me any suggestions... my address is on the bigcgi site.

CharlesW 8y ago

> I love how everyone always shat on PHP (the original serverless technology... I like and use PHP, and you absolutely can create serverless solutions with PHP, but you may be confusing "serverless" with "stateless". PHP itself is in no way intrinsically more "serverless" than other options.

mypalmike 8y ago

Does PHP automatically scale infrastructure to meet demand? Can you bring up 1000 instances of your service for spikes in volume? And then scale back down when the spike is over? Without writing code? Nobody is reinventing PHP.

CamTin 8y ago
Totally stateless PHP apps (retrieving and storing state at the top and bottom of each request) plus autoscaling based on CPU load starts to look pretty close to Lambdas + scheduled tasks to keep them "warm". This is how most LAMP apps are/were built, notably Wordpress. The real pain point in any auto-scaling/cloud/serverless application is and will probably always be the stateful bits. I think the first cloud provider to really figure out this killer bit will be the ultimate winner of the cloud wars. It will probably look something like Amazon's "Aurora Serverless" but be even more frictionless.
bartread 8y ago
> Does PHP automatically scale infrastructure to meet demand? Can you bring up 1000 instances of your service for spikes in volume? And then scale back down when the spike is over? Without writing code? People talk about this a lot. I wonder, for what percentage of systems, this kind of scalability is really a requirement. I also wonder what percentage of devs work on these kind of systems.