Step 2: Decoding the Cloud Landscape (Without Melting Your Brain)

Welcome to the second article of The Cloud Blueprint, where we make cloud decisions easier than picking what to watch on Netflix (seriously, why is that so hard?). If you haven’t read the first one, you can do so here. In the first article we reviewed, at a bird’s eye-view, how the blueprint works. Now we must take some time to explore the cloud ecosystem so that you can understand how it keeps your apps running and your data safe.

Think of this as learning the anatomy of the cloud, but without the overwhelming jargon that makes you want to unplug everything and move to a cabin in the woods. A

By the end of this article, you’ll not only understand the fundamental service and deployment models (spoiler: IaaS, PaaS, and SaaS are the stars of this show) but why it matters in the context of cloud key considerations. We will go through all seven cloud key considerations that you get a firm understanding of each one.

In article three, we will begin assigning weight values to those key considerations, so what you’re about to learn matters a lot.

What Is Cloud Computing?

Picture this: you used to need a room full of buzzing servers to store and process your data. Or a close in some cases. Now, thanks to cloud computing, you get all that power and storage through the internet, and you get to rent as much or as little of it as you want. Cloud computing lets you access computing services on demand. Companies like Microsoft, Amazon and Google have created an enormous network of buildings throughout the world filled with servers for you.

Very much like renting a car, you get to choose the type of Cloud Model you want based on your needs. This is where laaS, PaaS and Saas come in, which are essentially different models available for you to choose from. They are all great, they just serve different purposes.

1. Infrastructure as a Service (IaaS)

IaaS is the raw materials of cloud computing. Think of it as renting a bare-bones apartment: you get walls, a roof, and plumbing, but you’re responsible for decorating and maintenance.

• Use Cases: Perfect for businesses that need flexibility to configure environments, like hosting websites, running complex applications, or disaster recovery.
• Providers: Azure Virtual Machines, AWS EC2, and Google Compute Engine.
• Pros: High control and customization.
• Cons: You’ll need to know what you’re doing (or hire someone who does) … Hi!!! That’s me.

2. Platform as a Service (PaaS)

PaaS takes IaaS and throws in some pre-furnished essentials, like a comfy couch and a working kitchen. It’s a dream come true for developers who just want to build and deploy apps without worrying about managing infrastructure.

• Use Cases: Great for creating web apps, APIs, or microservices quickly.
• Providers: Azure App Service, AWS Elastic Beanstalk, and Google App Engine.
• Pros: Speeds up development; you focus on your app, not the plumbing.
• Cons: Limited control over infrastructure.

3. Software as a Service (SaaS)

SaaS is the penthouse suite: fully furnished, services included, and zero maintenance. You just walk in and start using it. Apps like email, CRM tools, and collaboration software live here.

• Use Cases: Perfect for businesses needing ready-to-use solutions like Microsoft 365, Salesforce, or Google Workspace.
• Providers: Microsoft, Salesforce, Google.
• Pros: No setup, no maintenance, just plug-and-play.
• Cons: Limited customization and you’re reliant on the vendor to keep the lights on.

Public, Private, and Hybrid Clouds

Now that you’ve got the service models down, let’s talk about where this cloud lives. It’s like choosing between city living, the suburbs, or a mountain retreat:

1. Public Cloud: Resources shared with others, making it cost-effective and scalable. It’s like living in an apartment building with shared amenities but your own space.
• Example: A startup hosting their app on AWS.
2. Private Cloud: Dedicated resources for your organization. Imagine your own gated mansion, perfect for high-security needs.
• Example: A hospital using Azure for storing patient data securely.
3. Hybrid Cloud: You get a bit of both, combining public and private cloud features. Think of it as your home office, part shared workspace, part private sanctuary.
• Example: A global company using Google Cloud for analytics and an on-prem data center for sensitive financial data.

Cloud Key Considerations

This is where the rubber meets the road. These points of consideration will help you evaluate what matters in your scenario and HOW MUCH it matters so that you can assign weights later in our blueprint. Let’s break them down so that it makes sense:

1. Integration with Existing Tools
• Why It Matters: Will this cloud fit seamlessly with tools you already use, like Microsoft 365 or Salesforce? Compatibility equals fewer headaches.
• Model Connection: SaaS is king here, but IaaS can be customized to fit like a glove if you have the budget to have someone set it up for you (Hi again! That’s MOI).

1. Pricing
• Why It Matters: Nobody likes surprise bills. Does the pricing fit your budget, whether it’s pay-as-you-go or reserved instances, where you commit to a certain amount of usage for a better deal?
• Model Connection: Public clouds are wallet-friendly for variable needs; private clouds, lesser so, but if you’re a hospital, privacy, or lack of, could cost you both arms and legs.

1. Security and Compliance
• Why It Matters: Handling sensitive data? You better make sure your cloud follows the rules (GDPR, HIPAA, SOC 2). One of the fabulous things about the cloud is it makes security and compliance SO MUCH easier.
• Model Connection: Private and hybrid clouds win for high-security scenarios.

1. Scalability
• Why It Matters: Will the cloud grow with your business or leave you scrambling for a bigger box? If you plan on needing A LOT of space, this is going to be important because you don’t want to pay for a 5 bedroom right now if you only need 1 bedroom, yet if you know it’s on the horizon, your plans need to allow enough room to add in a few rooms.
• Model Connection: Public clouds are the scaling champs, while private clouds are steady but less dynamic.

1. AI/ML Capabilities
• Why It Matters: Need machine learning for smarter analytics? Look for robust AI tools baked into the platform. As an AI Engineer, one of the biggest priorities I have whenever I set up a cloud architecture Is how ML and AI friendly it will be for various use types. The way AI and ML searches for information is different. Platforms like Azure have pre-baked AI tools in the cloud that can be game changing if you plan on AI being a big part of what you do.
• Model Connection: PaaS and public clouds are the go-to for AI/ML needs.

1. Support Options
• Why It Matters: When things break (and they will), who’s got your back, a chatbot or a dedicated team? Or do you have your own internal IT team who feel they can take care of most of the infrastructure?
• Model Connection: SaaS typically includes great support, but IaaS might leave you fending for yourself.

1. Vendor Lock-In Risk
• Why It Matters: Will switching later be a nightmare? Open standards help keep your options open.
• Model Connection: Hybrid cloud solutions reduce lock-in risk better than single-vendor setups.

Aligning Models with Workloads

Here’s how you align the right model with your needs:

• Static Workloads: Predictable needs (like hosting an internal tool) are best for private or hybrid clouds.
• Dynamic Workloads: Seasonal or unpredictable spikes (like holiday sales traffic) thrive in public clouds. You DO NOT want to be the website that breaks down because sales are going TO WELL…
• Development and Testing: PaaS is the golden ticket for fast deployment.
• AI/ML Workloads: Google Cloud, with its cutting-edge AI tools, often takes the lead here.

So now, what you want to do is slowly reconsider the seven points of consideration above and start writing down, if they matter, how much they matter and why specifically based on the new knowledge you’ve just accumulated. In article three, we will take those notes, and turn them into weights so that we can start ‘mathin’ a solution.

Click here for step 3