4 ms·
"Popular", because of legacy systems or knowledge, not popular because they are the most reasonable choice these days... And then, following this train of thou
by Mo3 4y ago
"Popular", because of legacy systems or knowledge, not popular because they are the most reasonable choice these days...
And then, following this train of thought, how many legacy systems do you think are being re-implemented in a serverless function environment?
How many completely new systems are being implemented in .NET or Java in a serverless function environment?
- anaganisk 4y agoI don’t know where you get your news from but thats just plain wrong. Java and .net are just not legacy, I agree they’re not hipster enough, but definitely in use and new server stuff are still being written in Java everyday. There are stuff like Graal, Fn, OpenFaas has support for Java, there is a beautiful framework called Vert.X also Quarkus whose entire point is > Quarkus tailors your application for GraalVM and HotSpot. Amazingly fast boot time, incredibly low RSS memory (not just heap size!) offering near instant scale up and high density memory utilization in container orchestration platforms like Kubernetes. We use a technique we call compile time boot.
- NicoJuicy 4y agoEuh, Azure is much bigger than Google cloud. And Azure functions + OpenFaas exists for serverless in .net. For Microservices, spring ( Java) and Dapper seems to be the way to go.