4 ms·
Hi Courtney, thanks for the post. Others have mentioned that there are some gotchas with Envoy, and you mention a few about the migration bumps. Did you encoun
by shay_ker 8y ago
Hi Courtney, thanks for the post.
Others have mentioned that there are some gotchas with Envoy, and you mention a few about the migration bumps. Did you encounter other gotchas? And do you have any suggestions on how to avoid/mitigate their impact?
- ckwang 8y agoLet me start by saying: The gotchas that we've experienced have been far eclipsed by the benefits. Aside from what what discussed, there weren't many things with Envoy specifically. We did have a few minor issues with the Thrift tooling, e.g. https://github.com/envoyproxy/envoy/commit/a3c744294bca2cbf612a5c8dc8d6ea13c63f3f38 https://github.com/envoyproxy/envoy/commit/a3c744294bca2cbf6... but as the above indicates, they were resolved _very_ quickly. The most important thing when making a transition like this is to have as much monitoring and observability as possible without the new tech. We were able to quickly identify and respond to issues we had with Envoy based on existing application and system instrumentation that weren't directly provided by Envoy, along with the vigilance of our engineering team.