From web servers to CDNs, stateless applications are the perfect solution for any application that does not require any state information to function.  ...

Does every system or component in a cloud-native app need its own code repository? Or can they all share a single code repository? ...

Cloud-native applications are scalable, resilient and flexible – but they also introduce a new set of user management challenges ...

Technical debt is the cost of doing additional work caused by choosing an easy, limited or sub-optimal solution now rather than using a better approach that would take longer or cost more ...

Make sure your applications can fail. Sounds weird, doesn’t it? But nothing is more critical to creating a highly reliable, cloud-native application than to ensure you can fail successfully. The key is ...

Using the cloud means you can focus on your application and use a third party for most of your infrastructure. The cloud provides virtual interfaces that abstract away the details of operating ...

One of the main motivations for using cloud-native application methodologies is to simplify our applications and their infrastructures. Cloud-native methodologies are designed around creating larger and more sophisticated applications without unnecessarily increasing ...

Have you seen the movie Crimson Tide? Every person architecting a cloud-native application should see this movie. In it, a breakaway Russian government threatens a nuclear attack on the United States. A ...

Cloud-native architectures are perfect for creating and operating modern, innovative applications. Cloud-native applications provide many advantages both to consumers of the applications and to those building and managing them. But bad actors ...

Simplicity is at the heart of our desire to use cloud-native application methodologies. Service-based applications are designed to decrease complexity in individual service components. Using cloud-native infrastructure focuses and reduces our available ...