Hello World! I just started on a new team where requirements are unclear and we have not yet decided on any sort of architecture yet. I’m doing this as an exercise for myself to determine when to use what technology; also, so I have more things to talk about with my coworkers at Happy Hour.
The preferred choice has always been Java and most people I work with are very comfortable with the Spring framework. I personally prefer Node because I hate Maven and Gradle and never want to use it. However, we don’t live in an ideal world where I get everything I want. I am going to list pros/cons of each technology.
Let’s start off with Java/Spring:
1. Better IDE (IntelliJ and Eclipse), easier to debug
2. Tried and tested. Spring has a large user base, lots of libraries and has been around for a while.
3. A lot of enterprise software is built on Java/Spring
1. Takes longer to develop and steeper learning curve
2. Dealing with XML configurations
3. Dependency issues
4. A downward trend in general usage of Spring
5. Only people that have previously used Spring use Spring
1. Testing. Junit sucks and Chai/Mocha are great
2. Build Management (npm install and npm start and you are ready to go. No need to worry about dependencies)
4. Simple and easy to work with
6. Node is “cool” and it is the future. It is newer than Spring and is only rapidly growing. A lot of big companies like Netflix, Walmart, etc have been using Node.
7. Less code to maintain
1. Great memory usage (great for cutting down AWS cost)
2. Code is easy to read and understand
4. New/cool right now and more startups and companies are adopting Go
5. “Go is an answer to problems of Scale at Google”
6. Great for concurrency!!! It was built by Google for scaling quickly and for concurrency.
7. Go is backed by Google
8. High performance
9. Growing number of gophers
Answer (1 of 4): I like Mojahedul Hoque Abul Hasanat's answer, but I also want to highlight some more things here. Note…www.quora.com
Right now, Spring is the de-facto standard framework for Java-based development, especially in corporate environments…www.nerdery.com
See what developers are saying about Go vs Spring-Boot. Some developers prefer Go over Spring-Boot because...stackshare.io
Welcome to Part 6, The final part of the great RESTful API framework showdown! Last time we had a look at the pros and…optimalbi.co
In Lisp, you don't just write your program down toward the language, you also build the language up toward your program…opencredo.com
I find that creating go backend services is super easy and simple. The builtin web server is amazingly performant. I've…news.ycombinator.com