Microservices in Java? Never.
Elliot Forbes

In my view this is just trading operational overhead for development overhead. The convention over configuration approach of Spring Boot in Java reduces boilerplate significantly over Go. Debugging and stepping through code becomes also becomes easier with JVM based languages. The imperative style of Go is also somewhat bloated compared to using the Stream API.

So yes you might pay less for the environment but if development man hours is doubling then it’s not necessarily a cost saving exercise.

This is course a gross simplification (You would be insane to write something like a CLI in Java instead of Go), but it’s something that should often be factored in with equal weighting to resource consumption.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.