Depends on bottlenecks, choose the right solution. I'm not fans of fancy things, all I want to achieve is simple stable and performance.
Container is really good things for make sure environment consistensy, speedy deploy and testing.
Serverless is good for Webhook-like and resource spiking scenario, billed by invoked calls, it might save a lot cost but different story with high resource usage. Development is also depends on framework/environment/provider, probably you need abstract your code base very well, else need to rewrite. (As my understanding)
But if you are more to PHP based, it is not recommended to do orchestrating, 1 PHP website container, can equal my whole hosting server usage. About 15 website, MySQL, Nginx, PHP 5.6, 7.0, 7.1, 7.2, 7.3 via managed panel, and also running two JAVA web service (SparkJava), just about 400mb ram usage, created 2yr ago, > 96% up time.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Depends on bottlenecks, choose the right solution. I'm not fans of fancy things, all I want to achieve is simple stable and performance.
Container is really good things for make sure environment consistensy, speedy deploy and testing.
Serverless is good for Webhook-like and resource spiking scenario, billed by invoked calls, it might save a lot cost but different story with high resource usage. Development is also depends on framework/environment/provider, probably you need abstract your code base very well, else need to rewrite. (As my understanding)
But if you are more to PHP based, it is not recommended to do orchestrating, 1 PHP website container, can equal my whole hosting server usage. About 15 website, MySQL, Nginx, PHP 5.6, 7.0, 7.1, 7.2, 7.3 via managed panel, and also running two JAVA web service (SparkJava), just about 400mb ram usage, created 2yr ago, > 96% up time.