Re:Slack’s Migration to a Cellular Architecture
by eikenberry on Saturday August 26, 2023 @03:48PM
(#37276193)
What mess? That sounds like a healthy internal language ecosystem to me. You need at least 2 primary languages to avoid accidental lock-in and maintain good developer diversity. That very paragraph is a great example of how the diversity helped them avoid the trap of plumbing it through their RPCs.
[ Parent
| on HN ]
Re:Slack’s Migration to a Cellular Architecture
by t0mas88 on Saturday August 26, 2023 @04:13PM
(#37276448)
Since when is an "internal langue ecosystem" a good idea? Technology in a company like Slack exists to deliver useful features and good performance/stability to users faster than competitors can do it. For an app like theirs it doesn't sound like something that needs several disparate internal platforms that are slowing them down.
Re:Slack’s Migration to a Cellular Architecture
by nostrebored on Saturday August 26, 2023 @04:24PM
(#37276539)
How is choosing the right language for a task/team slowing them down?
For large scale, cross cutting initiatives you’ll have some pain. For feature velocity, you’ll see great results. Everything is a trade off.
Re:Slack’s Migration to a Cellular Architecture
by eikenberry on Tuesday August 29, 2023 @04:13PM
(#37313280)
Standardizing on a single language/toolset is a form of tech debt and has similar up/downsides. Comparable to, for example, how skipping testing will increase your velocity in the short run, but it will hurt it in the long run.
Re:Slack’s Migration to a Cellular Architecture
by lopkeny12ko on Saturday August 26, 2023 @05:57PM
(#37277287)
You're suggesting that needing to reimplement the same thing 5 times for every single language in use is a hallmark of a "healthy internal language ecosystem"?
Re:Slack’s Migration to a Cellular Architecture
by eikenberry on Sunday August 27, 2023 @12:42AM
(#37279479)
That's the red flag, the thing you are trying to avoid. You don't want to implement things in each language and you always have more than one language even if you standardize (over time). You don't want libraries, you want services. This is why things like Istio are way better than libraries for mesh networking. Using external services for common things keeps you from being locked into a single tech stack and the limitations that entails.