IBM Cloud Deployment 4 Ways: IBM Cloud Code Engine

Jenna Ritten - Aug 3 '21 - - Dev Community

Welcome back to Tutorial Tuesday!

This week we'll be exploring cloud and hybrid Platform-as-a-Service (PaaS) deployment models, and we'll take a look at the IBM PaaS products and offerings. If you're new to cloud computing, you might have been put off by the overbearing amount of acronyms used. Just about everything is sold as a service (aaS) these days, even transportation.

Alt Text

To clarify some of the deployment models, let’s have a look at some of these aaS acronyms. IaaS is Infrastructure-as-a-Service, PaaS is Platform-as-a-Service, CaaS is Containers-as-a-Service, and FaaS is Serverless, which is also known as Function-as-a-Service.

Platform-as-a-Service (PaaS)

PaaS, or Platform-as-a-Service, is a cloud computing model that provides customers a complete platform—hardware, software, and infrastructure—for developing, running, and managing applications without the cost, complexity, and inflexibility of building and maintaining that platform on-premises.

The PaaS provider hosts everything—servers, networks, storage, operating system software, databases—at their data center; the customer uses it all for a for a monthly fee based on usage and can purchase more resources on-demand as needed. In this way, PaaS lets your development teams to build, test, deploy, maintain, update, and scale applications (and to innovate in response to market opportunities and threats) much more quickly and less expensively than they could if you had to build out and manage your own on-premises platform.

IBM PaaS Products & Offerings: IBM Cloud Kubernetes Service, IBM Cloud Foundry & Red Hat OpenShift on IBM Cloud

Pros to PaaS:

Faster Time to Market

Faster, Easier, Less-Risky Adoption of a Wider Range of Resources

Easy, Cost-Effective Scalability

Lower Costs

IBM Cloud Code Engine

Focus on writing code, not on managing infrastructure.

What is IBM Cloud Code Engine?

IBM Cloud Code Engine is a fully managed, serverless platform. Bring your container images, batch jobs, or source code and let IBM Cloud Code Engine manage and secure the underlying infrastructure for you. No need to size, deploy, or scale container clusters yourself. No networking skills required, either.

Benefits

Go Live in Seconds
Build great apps in the language of your choice, then deploy them in seconds on a serverless platform.

Focus on Your Code
No infrastructure management needed. Cluster sizing, scaling and networking covered.

Security Included
Your apps are automatically secured with TLS and isolated from other workloads.

Unified Experience
Deploy and more securely integrate web apps, containers, batch jobs and functions.

Features

A single runtime environment. Any workload. Scale on demand.
Pick the type of workload that best fits your needs without learning multiple serverless products.

Fully Managed Infrastructure
Open source frameworks for container orchestration, service mesh and more — all managed and optimized for you.

Autoscaling Down to Zero
Automatically scale your workloads up and down – even down to zero – and pay only for what you use.

Simplified App Security
Secure networking, pod security policies, resource quotas and limit ranges.

No Kubernetes Training Needed
Cluster complexity is invisible to you. Focus on your code and not on configuring and securing clusters or VMs.

IBM Cloud Code Engine Resources

Try It Out!

Check Out the Code Engine 101 & 201 Workshop Replays:

Alt Text

IBM Code Engine 101: Run Your Code, Containers & Batch Jobs

Alt Text

IBM Code Engine 201: Deploy Apps from Source Code

CONGRATULATIONS!

Alt Text

Tune in next week for our next Tutorial Tuesday post.

Connect w Me!
https://linktr.ee/jritten

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .