Recently, in the market driven by ever-changing software and customer needs, almost every company is required to use cloud infrastructure to keep pace with the demands of the modern world. To do this, both the application and its data need to be externalized from the company's infrastructure. This cloud orientation must be kept in mind during software and application development. Applications need to fit into the microservice architecture, i.e., has to be cloud-native.

Cloud-native applications, in contrast to traditional monolithic software, use a microservice architecture. This means instead of a large indivisible software, the application is made up of many smaller and simple components. These service components operate independently, but communicate with each other to ensure collaboration. We can develop the these service components ourselves, but also we can use third-party applications provided by the cloud provider.

The components of a cloud-native application are packaged in containers, so an application is made up of the collaboration of multiple containers. This approach has several benefits: containers provide isolation between components, they are easily accessible and can be scaled separately. A container can be created or stopped quickly and easily at any time, and perhaps most importantly, they ensure the hardware and platform independence of the application.

As their name suggests, cloud-native applications run in cloud systems. However, this does not mean that the used software necessarily have to be externalized into a public cloud provider's infrastructure, as we can also use a private or hybrid cloud to run our applications. Cloud provides almost “infinite” computing and storage capacity as well as application lifecycle event management. Consequently, the developers can focus on what they do best, the application developing. Cloud-native applications can be managed dynamically and automatically thanks, they are started and stopped on demand, and scaled to suit the current customer needs.