3 ms·
Most companies > 1000 employees that were founded before 2000 will have most of their critical internal systems written in Java and/or .NET. If you don't know
by runako 3y ago
Most companies > 1000 employees that were founded before 2000 will have most of their critical internal systems written in Java and/or .NET.
If you don't know anything about a large company and have a meeting with someone in IT there, it's a safe bet that boning up on Spring Boot before the meeting will be beneficial.
- icepat 3y agoRight, but my question is if new projects, products, and companies are electing to use it now. I'm aware that much of legacy software is still Java.
- bzzzt 3y agoIf there's a lot of Java knowledge around in a company it can certainly be beneficial to use it ;). I set up a simple REST backend service last year using Quarkus and can think of worse frameworks I could have picked. Also, if a new system has to connect to a legacy system using SOAP there are about 2 languages with a complete and interoperable implementation: Java and .NET. There are lots of toy libraries for other languages but I've never found one fully supporting the entire WS-* standard set.
- runako 3y agoSorry, I should have clarified. Yes, if a company has most of its legacy code in Java, it likely also still does new projects in Java. The Java ecosystem is robust, well-supported, and performs well. When you are working in big enterprise tech, third parties with whom you work will often only support Java and .NET as first-class citizens for interop. It's not trendy, but that alone is not enough to overcome the advantages of choosing the fleet standard in a company that already has a substantial investment in Java.