The What, Why And How Of Building Apps On The Cloud
Explore cloud-native ecosystems, why every business needs to understand this area of technology & how you can build your very own cloud app.Download The Free eBook
About This eBook
A decade ago, if you wanted to build an application, you went out and bought a computer, an operating system, wrote your program, and created your very own little data center. You would maintain it, keep it secure, and every once in a while expand it with more storage and computing power.
But now… now you have the cloud. That means when building a modern application, you don’t have to think about the infrastructure, the security protocols, or future scaling. That’s the short version of it.
In This eBook:
What is a Cloud Native Ecosystem
What are Cloud Native Applications
The Benefits of Cloud Native Applications
Whether to Refine or Rebuild Applications
The 6 R’s of Cloud Migration
Building Cloud Applications from Scratch
Cloud Native Tools and Features: AI, ML, Data Analytics
Specific Managed Services Provided By Google Cloud
Download the Free eBook
Understanding The Cloud-Native Ecosystem
The term “cloud-native” can be thought of as a design ideology that extends beyond just applications. For instance, when talking about infrastructures, processes, and practices that are cloud-native, we mean that they are specifically for cloud computing. Therefore, all of these things have the following characteristics in common:
- Easily scalable
- Quick deployment
The infrastructure which refers to your architecture and cloud-services provider forms the foundation of any cloud-native ecosystem, but it’s the cloud-native applications that are at the core.
What Are Cloud-Native Applications?
A better way of understanding what cloud-native applications are is to understand what they are not - they are not monolithic. Most traditional applications are built on the monolithic architecture, whereas most modern cloud-native applications are built on a serverless architecture using microservices.
Let’s visualize the difference between these two types of applications.
Imagine a complex maze full of overlapping rooms and interconnected passages that make navigation a nightmare - this is a monolithic application. Each room is a feature/update in your application and changing a single feature would mean affecting the entire maze. Naturally, finding and separating faults is a pain.
Now imagine a maze full of rooms that are laid out in perfect symmetry and equal gap between them. None of the rooms overlap each other but are connected through pipes. This is an app built with microservices. Each room inside the box represents an isolated feature (or a microservice) that can communicate with the rest of the application with APIs (pipes). The beauty of microservices that you can change or even shut down microservices without having to shut down the entire application. For more, download the entire eBook for free.