5 ms·

Most of my programming peers want to focus on solving product-related problems rather than authe, authn, tls config, failover, throttling, discovery… We want t

Most of my programming peers want to focus on solving product-related problems rather than authe, authn, tls config, failover, throttling, discovery… We want to automate everything not related to the code we want to write. Service meshes sound like a good way to do that.

Scubabear68 4y ago
Right - by why not use something like an API gateway then?
- steviesands 4y ago
  API gateways are primarily used for HTTP traffic coming from clients external to your backend services eg. an iOS device (hence the term 'gateway' vs. 'mesh'). I don't think they support thrift or grpc (at least aws doesn't, not sure about other providers). https://aws.amazon.com/api-gateway/ https://aws.amazon.com/api-gateway/
  - alasdair_ 4y ago
    Google cloud supports grpc on their api gateway: https://cloud.google.com/api-gateway/docs/grpc-overview https://cloud.google.com/api-gateway/docs/grpc-overview
- pbalau 4y ago
  That can work, but it means you simply outsourced the problem to AWS. It's not a bad idea per se, but it means your service needs to talk, in some way, http. You could use the service mesh thing from AWS, along with cognito jwts, for authenticatetion and authorization
  - Too 4y ago
    You can easily self host your own proxy. I bet API gateway is just Nginx, Traefik or HAProxy under the hood anyway.
deleted 4y ago
[deleted]