Live data from Hacker News

Go + Services = One Goliath Project

engineering.khanacademy.org

1–10 of 449 posts

Re: Go + Services = One Goliath Project

#9
We turned our monolith into a bunch of micro services almost 6 years ago to the day. For a long time I was very happy with the new pattern but over the years the weight of keeping everything updated along with the inevitable corners that fall behind and have...questionable..security due to how long they sit neglected has really left me wondering if I am happy with it after all.

I would love hear some thoughts from others that made the move, especially anyone that decided to move back to a monolith repo.

Re: Go + Services = One Goliath Project

#10
post #4

I was under the impression that Go was more performant than Kotlin. TMYK :)

Go was written for servers, Kotlin for mobile apps. Seems an obvious choice really.

Kotlin is just a less verbose, more modern language targeting the JVM. It has nothing to do with mobile apps beyond that Google, much later, decided to support it for Android development.

Go is an efficient platform, however in these switches it usually goes something like "we took something hugely overbuilt, with layers and layers and layers and abstractions and abstractions, and rebuilt it with minimalist Go and now it's faster", which, of course it is.

Post reply on HN