3 ms·
Having well set expectations & standards for building out your microservices seems like a fairly obvious way to claw back many of the advantages / normalizing b
by rektide 6y ago
Having well set expectations & standards for building out your microservices seems like a fairly obvious way to claw back many of the advantages / normalizing behaviors that the pro-Monolith camp advocates.
This article seems to argue that making everyone use an RPC library is enough. But rarely is there good monitoring & observability built in to that. Other tasks like discovery &c may seem superflous, but it brings a well-defined set of expectations that incoming engineers stand a good chance of knowing. You're not just bringing in Monolith style genetic material & practice, you're bringing in common genetic material that others will know & be familiar with.
The overhead seems debateable. Performance can be quite good in some cases, depending on choices of underlying tech. The author talks about the cost of maintaining the system, but in the two modest sized environments I've seen (under 100 nodes), the transition was extremely painless & fast & required little effort, & nearly no maintenance. It also drastically reduced the effort we had spent & intended to spend instrumenting our existing services, so it felt to us like the maintenance cost was hugely negative.
The arguments about the proxies limiting your available options are somewhat interesting. For 99.999% of companies, I'd say that using RSocket or Aeron is way more fancy tech than you should be targeting. I do hope HTTP3 support emerges relatively quickly. My hope is that gRPC has some plans in the works somewhere, and that once gRPC starts to progress, the proxies will rapidly catch up.
- medium_burrito 6y agoConsistent metrics and retry/circuit-breaker behavior are my number one reasons for advocating a service mesh. There are other advantages, such as offering a consistent interface across multiple languages client to some shared resource- redis being a prime example, with various client implementations that behave very differently. But, like everything there is a cost- in this case another level of complexity.
- lmm 6y ago> This article seems to argue that making everyone use an RPC library is enough. But rarely is there good monitoring & observability built in to that. On the contrary, a proper RPC library tends to have those things built in. If your services are homogeneous enough that you can have everyone use the same RPC library, you can hook up that library's monitoring, discovery etc. functionality, and achieve the benefits of service mesh with much less overhead. IME it's much the same for a lot of microservice scenarios - if your environment is heterogeneous then it makes sense, but in a homogeneous environment making a library instead often gets you most of the benefits at a much smaller cost.