concept software in category istio

This is an excerpt from Manning's book Istio in Action.
Software is the lifeblood of today’s companies. As we move to a more digital world, consumers will expect convenience, service, and quality when interacting with these companies and software will be used to deliver these experiences. Customers don’t conform nicely to structure, processes, or pre-defined boxes. Customer’s demands and needs are fluid, dynamic and unpredictable. For this reason, our companies and software systems will need to have these same characteristics. For some companies (e.g., startups), building software systems that are agile and able to respond to unpredictability will be the difference between survival or not. For others (e.g., existing companies), the inability to use software as a differentiator will mean slower growth, decay, and eventual disruption.
Once we have code deployed into production, we can make a business decision about how to release it to our users. Releasing our code means bringing live traffic over to our new deployment. This is not, however, an all-or-nothing proposition. This is where a decoupling between deployment and release becomes crucial to reduce the risk of bringing new code to production. We can decide to release our new software to just our internal employees. If we are an internal employee, we can control the traffic such that we’d be exposed to this new version of the software. As operators of the software we can then observe (using our logging and metrics collection) and verify our code change had the intended affect.