4 ms·
Spring Boot is very productive but things can get very hairy when debugging auto configuration or understanding why a bean is missing from the context. Running
by ojhughes 3y ago
Spring Boot is very productive but things can get very hairy when debugging auto configuration or understanding why a bean is missing from the context.
Running Boot in a container is also not great due to the memory requirements needed for bootstrap (min 0.5 Gi). I know GraalVm makes this better but compile times are still too painful.
I also think the push to make Reactor the default choice was a mistake (deprecating RestTemplate). The reactive model in Java feels unnatural and it can be very hard to debug.
I am working with Go now and don’t miss Spring Boot that much but it still has a place in my heart for the amazing community and docs.
- gabereiser 3y agoSpring and the JVM (even modularized) is a huge sore for cloud ops due to container size. Great that you pointed that out. Go's chi router or Fiber along with gorm gets us not so far away if you're doing crud. I also love go's ability to bundle assets into the binary and serve them (front-end code). It's so good that if I want to run the entire web application on another machine, I just copy the binary and run. Docker memory requirements are in the 64m range and even that is probably a bit of overkill. I can run thousands of these on a raspberry pi 4. I can only run like 4 spring boot apps on it.
- haarolean 3y agoWhich stack/frameworks in Go would you recommend to achieve a somewhat close developing experience? AFAIK the default library doesn't have much and there are no huge frameworks like Spring.