Last year at work we started migrating our backend from PHP on a dedicated server to Node.js on AWS lamda functions

We went from 10 second calls to 70ms calls...

At this point our frontend is not even ready for this kind of speed 😅

Lol pretty much exactly what we're doing rn

Only difference, our frontends can handle the speed

It's probably a darn sight cheaper, too. Quick running lambda calls are as good as free.

If only Java could work in the same way without the cold-start times...

PHP is perfectly capable of showing similar times.

@Quirinus Go ahead, run db queries or file operations in parallel in PHP, and don't forget the time each developer will spend setting up their environment before they get all extensions for async operations up & running...

@dUcKtYpEd that's why we went for the microservices approach :)

@hitko facts

@dUcKtYpEd Source? Best I could find was 200 billion lines in 1997 (when an estimated 5 billion lines were added annually, so 320 billion lines at best by now), with a significant portion of COBOL code being replaced following Y2K (in 2006, only 60% businesses still reported to use COBOL, compared to 80% in 1997, and further 36% had plans to migrate from it in near future or as soon as maintenance costs outgrow migration costs).

COBOL has been used for crucial business software since 1960, PHP appeared in 1995 aimed at small web pages and home users and it never played a strategic role in core business systems, so it's much easier and faster to replace. Though it's used by a great amount of websites, w3 reports 3/4 of PHP websites run one of approx. 100 most popular PHP CMSs which brings the amount of PHP code down significantly, and while COBOL code is either maintained and in use, or it doesn't run at all, PHP code just remains in limbo on some .com era server in someone's basement.

Sounds like a business opportunity, offering services translating from PHP stacks to other stacks.

Thank you