@inproceedings{raptors2026-c075,
  title     = {{The Honest Service Mesh Adoption Framework}},
  author    = {Pandya, Ritvik},
  booktitle = {Proceedings of the Raptors Conference},
  volume    = {1},
  year      = {2026},
  publisher = {Hackathon Raptors},
  address   = {London, United Kingdom},
  doi       = {10.68495/rc.2026.C075},
  url       = {https://doi.org/10.68495/rc.2026.C075},
  abstract  = {A service mesh is a bundle: encryption, retries, traffic control and observability arrive together, and most teams buy the whole thing for one item in it. This paper walks through four tradeoffs that show up in production, pairing each with what actually reduces it rather than what is claimed to, and supplies an Envoy response-flag triage table that turns an opaque 503 into a five-second lookup. That table is intended for a runbook rather than a slide. The paper covers where Istio's ambient mode changes the calculation, since the cost side of the decision has moved, and prices the cheaper alternatives worth considering before committing to a mesh at all. Readers take away the ability to make an explicit adopt-or-defer call for their own systems, with concrete thresholds rather than general advice, and a clear view of which narrower options, among them Cilium, SPIFFE and proxyless gRPC, might solve the requirement they actually have.}
}