3 ms·
Sounds more like moving away from a big jvm monolith is how they gained their speed. Our Scala based microservices build in seconds. Anyway, no idea who movio
by joneholland 10y ago
Sounds more like moving away from a big jvm monolith is how they gained their speed.
Our Scala based microservices build in seconds.
Anyway, no idea who movio is, but cool they like go. Not sure why they needed to write Scala FUD in the process.
- Daishiman 10y agoI think that if you have to move to microservices just to avoid atrocious compilation times that means there's something horribly wrong in the language stack. Microservices should be used to solve architecture problems, not a workaround for compiler slowness.
- scalatohaskell 10y agojust cyclic dependencies between project's generated source codes of exposed interfaces/contracts. ez. It's not hard to fuck up ur sw eng. practices and blame language.
- tapirl 10y agohow about the deploy duration and memory consumption?
- joneholland 10y agoDeploy in seconds as well. We create executable jars using grpc.
- tapirl 10y agoDeploy in seconds is too long. Most Go programs are deployed in less than one second.