6 ms·
what did the Go solution replace? I only read about DB changes, and cannot draw any conclusions.
by sankyo 8y ago
what did the Go solution replace? I only read about DB changes, and cannot draw any conclusions.
- fleitz 8y agoIt replaced a couple sub queries/ common table expression. Somehow using the same data store makes it a microservice rather than a distributed monolith. Of course it’s a lot less 2018/webscale to just optimize your DB rather than replace something with Go
- firasd 8y agoRight. The blog post is a good narrative over time but isn't super clear about how they solved the problem. If I understand correctly they broke down the big MySQL query into separate queries that the Go service processes/caches?
- maloga 8y agoBlogpost author here. That is correct. Sorry if the explanation isn't super clear; for this particular question, you can consider the two diagrams as a before and after. They pretty much convey what you have explained here.
- mlvljr 8y agoshhhhhhhhhhhh, people are raving!
- f1notformula1 8y agoI found this linked from the article https://movio.co/en/blog/migrate-Scala-to-Go/ https://movio.co/en/blog/migrate-Scala-to-Go/ So if the alternative was Scala I can see why Go may have helped tighten things up a bit.