News for hackers. Stuff that matters.
Re:Go + Services = One Goliath Project by solidasparagus on Saturday December 21, 2019 @09:31PM (#21854758)
I don't really understand moving to microservices if you aren't going to give the service teams the autonomy to make their own decisions and move at their own pace. Microservices always seemed to me to be more of an organizational strategy than a technical one - if you have services, but they can't operate independently, it feels a bit like you are just creating a distributed monolith.
Re:Go + Services = One Goliath Project by dangoor on Saturday December 21, 2019 @09:42PM (#21854807)
We're making a certain set of tradeoffs. For example, we're not adopting the "write code in whatever language you want" form of microservices that some folks adopt, because we don't feel like we're large enough to support that.

Like I said, though, we do want to minimize the library footprint. The vast majority of deploys in this new world will be single service deploys, with the benefits that come with that. We already deploy our monolith several times a day. These services will speed that further.

Re:Go + Services = One Goliath Project by solidasparagus on Sunday December 22, 2019 @05:29AM (#21856349)
It'll be interesting to see how it works. I would probably fight to not have shared dependencies because the relatively small benefit does not seem to merit the increased coupling between teams - if all teams needs to agree before a library can be upgraded, I can't imagine it will be very easy to keep libraries up-to-date. To a certain extent it depends on how large your engineering org is, which I don't know.

I've been in companies that moved from monolith to microservices and I saw it work well except when teams had such tight cross-service dependencies that they had to get other teams' ok before making changes to internal details of their service. Then developer velocity was slower than before because it took time to make the cross-team discussion happen and political capital to make other team care when they have other priorities.

Re:Go + Services = One Goliath Project by dangoor on Sunday December 22, 2019 @12:42PM (#21858466)
We'll see how it plays out, but the situation that I've described isn't really different from the one we have today (because we have a monolith). Hopefully, it will be better because of how the Go project is trying to get library maintainers to follow semver and avoid breaking changes. When we need to upgrade a dependency, we can do so in one diff, catching the errors with the compiler and test runs. If the upgrade seems risky, we'll watch that deploy carefully, and we already have a process for "risky" deploys. Plus, these are likely some of the easiest changes to rollback if need be, because they are unlikely to change persisted data.

Ultimately, though, if we find that this plan reduces velocity, it won't be that hard to change later.

Re:Go + Services = One Goliath Project by vips7L on Saturday December 21, 2019 @11:01PM (#21855095)
Didnt you guys recently decide to write some services in kotlin? Are you rewriting those in go now since everything is going to be one language?
Re:Go + Services = One Goliath Project by dangoor on Sunday December 22, 2019 @12:23PM (#21858371)
We have some dataflow jobs written in Kotlin (we blogged about that in June 2018[1]). We also have an internal service written in Kotlin.

We ideally want one language. But Apache Beam (which is behind Google Dataflow) doesn't yet have production support for Go. More importantly, though, we have no time pressure on switching the Kotlin code over, so that's a long way out.

[1]: https://engineering.khanacademy.org/posts/kotlin-adoption.ht...

Re:Go + Services = One Goliath Project by vips7L on Sunday December 22, 2019 @12:27PM (#21858393)
Thanks for answering! That was the specific article I remember reading.
Re:Go + Services = One Goliath Project by gtirloni on Saturday December 21, 2019 @09:36PM (#21854783)
Choosing the dependencies' version is not all there's to decide. Teams have a lot of control of basically everything else.
Re:Go + Services = One Goliath Project by andyroid on Saturday December 21, 2019 @10:52PM (#21855063)
So, no choice of language and no choice of the libraries used. What’s “everything else” exactly? Sounds like missing out on the more interesting parts of a micro service architecture.
Re:Go + Services = One Goliath Project by sangnoir on Sunday December 22, 2019 @12:37AM (#21855420)
Yeah, I'll never work for a company[1] where service teams are free to choose any language; 2 or 3 options at most is fine, but more than that is a hard no. I'll have to read/work on that code sooner or later, and I have no time to be dealing with a hodgepodge of languages

1. In the 10-5000 employee range: tech giants are a different beast when it comes to team accountability.

Re:Go + Services = One Goliath Project by solidasparagus on Sunday December 22, 2019 @05:18AM (#21856306)
> I'll have to read/work on that code sooner or later

In the microservices organizations I've seen, this isn't true. The other service teams provide an API and, like any other SaaS you use, you do not need to be able to read the implementation. You would only work on that code if you switch service teams.