3 ms·

The point is to do all this between services, not between the user-facing apps and the users.

• KronisLV 4y ago
  In the above example, that's where Docker networking would come in (load balancing, health checks, transparent encryption of traffic) for many of those concerns. Not all of them, unless you'd want to run a web server sidecar for your apps, which would be very much like a slightly simplified implementation of a service mesh anyways! Then again, in my eyes the "sweet spot" of simple architecture is something like: [users] <==> [ingress] <==> [service] <==> [database/message queue/key-value store] with maybe some middleware. If you have a lot of traffic between the internal services, then maybe your architecture mandates a more fully fledged solution.
  • remram 4y ago
    You don't have to use a service mesh. What you describe is not a service mesh. It's just a little weird to start your comment with "It pains me to see that the concept of a service mesh often become Kubernetes centric" and then describe an architecture that doesn't have a service mesh.
    • KronisLV 4y ago
      Fair enough, thanks for your input.