There is no excerpt because this is a protected post.
Let’s explore how being in the “Zone” or being in “Flow” ain’t static and changes throughout your career. Prerequisite to getting into Flow Short feedback loops sets Software Engineering apart from every other profession. Just take a second and think about it. A Cellular Bioengineer applies a substance to a set of cells and has
Learn the elements of the Envoy Proxy by getting a microservice application up and running and configuring the routes to every service, in less than 10 minutes.
I would have never believed that I would be excited about Authentication and Authorization. What on the technological spectrum could Istio possibly do to make me excited about these dreadful topics, and more importantly why should it excite you as well? Because, Istio takes these responsibilities from our services and offloads them to the Envoy
Authorization with Auth0 Authentication enables us to know who a user is, but we need the authorization to know what they can access. Istio provides the tools for this as well! As an example, we’ll create two groups of users (shown in figure 24): Users: with access to only the SA-WebApp and SA-Frontend service. Moderators:
Tap yourself on the back, you are amazing for sticking with this it definitely wasn’t easy, there were bumps along the way and it wasn’t as smooth as I presented. But now you mastered this amazing technology! Istio? Let’s call it Beast-io!! Because it’s such a BEAST! It provided us with: Observability over our services
It’s not always that the code is buggy. In the list of “The 8 fallacies of distributed computing” the first fallacy is that “The network is reliable”. The network is definitely NOT reliable, and that is why we need Timeouts and Retries. For demonstration purposes, we will continue to use the buggy version of sa-logic, where
Canary Deployment is the process of rolling out a new version of an application to a small set of users, as a step to verify the absence of issues, and then with a higher assurance of quality release to the wider audience. Let’s continue with the same buggy subset of sa-logic to demonstrate canary deployments,
Shadowing or Mirroring is used when we want to test a change in production but not affect end-users, so we mirror the requests into a second instance that has the change and evaluate it. To phrase it simpler it’s when one of your colleagues picks the most critical issue and makes a Big ball of
Traffic Management Using the Envoy’s Istio provides a host of new capabilities to your cluster enabling: Dynamic request routing: Canary deployments, A/B testing, Load balancing: Simple and Consistent Hash balancing Failure Recovery: timeouts, retries, circuit breakers. Fault Injection: delays, abort requests etc. In this series, we will showcase these capabilities in our application and get
Istio features out of the box By intercepting all network communication Istio is fed with metrics and data that can be used to gain observability of the whole application. Kiali, an open source project uses this data to provide the answer to the question: What microservices are part of my Istio service mesh and how
The VirtualService resource The VirtualService instructs the Ingress Gateway how to route the requests that were allowed into the cluster. For our application requests coming through the http-gateway must be routed to the sa-frontend, sa-web-app and sa-feedback services (shown in figure 1). Let’s break down the requests that should be routed to SA-Frontend: Exact path