Elasticity: Cloud-native apps scale as needed.
Modular Design: Cloud-native apps are modular with functions broken into microservices, allowing them to be shut off when not needed and for updates to be rolled out to that one module.
Statelessness: Cloud-native apps aren’t tied to infrastructure, which means they can run in a highly distributed manner while maintaining their state independent of the elastic nature of the underlying infrastructure. Many on-premises apps store the state of the app on the infrastructure the code runs so the app can be broken when adding/removing server resources.
Infrastructure abstraction: Cloud-native app architecture lets developers use a platform to abstract
away from underlying infrastructure dependencies. With traditional app architecture, developers often build close dependencies between the app and underlying hardware, storage, and backing
services, which makes migrating and scaling the app across new infrastructure complex and risky, working against the cloud model.
Right-sized capacity: A cloud-native app platform dynamically allocates and reallocates resources based on the ongoing needs of the application. Traditional IT designs a dedicated, custom
infrastructure solution that’s often over-sized based on worst-case capacity estimates with little capability to scale beyond to meet demand.