Re:Microservices in Java – A Second Look
by mmargerum on Thursday October 19, 2017 @06:16AM
(#15506720)
Go comes with pretty much everything you would need for micro services in the standard library and linking those parts in isn’t likely to change the memory profile very much.
Re:Microservices in Java – A Second Look
by empthought on Thursday October 19, 2017 @12:25PM
(#15509289)
Not really seeing anything in the Go standard library for https://docs.spring.io/spring-boot/docs/current/reference/ht..., most of which we need for microservices.
Yes of course, for a single service with one endpoint that does nothing it is bloat. But which microservice does nothing?
Think about a database backend, actuator endpoints, etc. They are all possible with a memory footprint of ~200mb. It can be less is you use another language, but I doubt that Go will give you such a major framework for developing a microservice. And this will save you a lot more time than taking an hour to reduce your memory footprint.
And one thing you missed too: Using the JVM should also be combined with a basic knowledge about how the heap works. And if you do not limit it, it will get a lot bigger than required, this should be common knowledge. Comparing this to Go it seems like a much better way. In Go there is afaik no way to limit the heap. In worst case it will grow and grow and grow.