- The cloud and cloud-native architectures can help deliver resilience.
- Distributed applications and services.
- Immutable data sets to detect and surface such attacks.
- Modern cloud architectures are moving from monolithic.
The cloud offers many tools for building systems that follow this paradigm. For example, Amazon recently announced “Chaos Engineering” as a service that allows companies to introduce elements of chaos into their production workloads. For example, shutting down running instances to ensure overall performance is not impacted and workloads are overloaded. Time becomes resilient in the face of these types of operational setbacks.
Getting to this point is a journey, and companies may need to take several steps to get there. For example, if you’re moving your pets from a local world to the cloud world without significantly changing the architecture of the applications, that’s just one step. The common term for this is “lifting and switching”. Once your applications are in the cloud and you are comfortable with the native cloud tools, you can work on transforming these pets into modern architectures that are distributed, immutable, and ephemeral (e.g., cattle).
The cloud – and cloud-native architectures:
-
Distributed Applications and services:
If your applications use a distributed delivery model; For example, cloud-based services such as content delivery networks (CDNs) mean you need to worry less about DDoS attacks, as these attacks work best by focusing their firepower in one direction.
-
Immutable Records:
If your applications use solutions that do not change records but are appended as they are written, that is, your record is immutable, you need to worry less about attacks on the integrity of this data, as it is easier to detect and detect such attacks.
-
Volatile Workload:
If your applications are short-lived in nature, you may be less concerned about attackers establishing the persistence and moving sideways. The value of sensitive information (e.g. tokens associated with this application instance) is reduced because these assets are simply taken out of service and new ones are instantiated within a relatively short period of time.
Pets versus cattle as to distinguish the health of pets
This brings us to a concept that has already been discussed a lot in the context of the cloud. Pets have cute names and can be recognized individually. When a pet gets sick, the owner takes it to the veterinarian. The owners give their pets lifelong care and ensure they live healthy lives for as long as possible.
Traditional uses are like pets. Each instance is unique. If the application gets infected, it will be taken to the cyber vet. “Patch in Place” is common in traditional applications that make these instances unique. The job of IT is to keep the applications running for as long as possible.
Cattle, on the other hand, have no names, they have numbers. They generally cannot distinguish the cattle in the herd and do not develop relationships with them. When cattle get sick or become infected, you kill the herd. Modern cloud applications are like cattle. You create many running instances of the services, and each instance is indistinguishable from the other
