In recent years, the adoption of cloud computing services has increased tremendously, especially given the onset of the pandemic. According to a report from the International Data Corporation (IDC), the public cloud services market grew 24.1% year over year in 2020. This increase in popularity is credited to the benefits provided by cloud including flexibility, on-demand capacity planning, cost reductions, and ability for users to access shared resources from anywhere.
No matter where you are in your cloud journey, understanding foundational concepts like the different types of cloud service models is important to your success in the cloud. These cloud computing service models provide different levels of control, flexibility, and management capabilities. With a greater understanding of the models, their benefits, and the different ways to deploy these infrastructures, you can determine the method that matches your business needs best.
What are the 3 Cloud Computing Service Delivery Models?
Different cloud computing service delivery models help meet different needs, and determining which model is best for you is an important first step when you transition to the cloud. The three major models are IaaS, PaaS, and SaaS.
Infrastructure as a Service (IaaS)
IaaS is one of the most flexible cloud computing models. The infrastructure and its features are presented in a completely remote environment, allowing clients direct access to servers, networking, storage, and availability zones. Additionally, IaaS environments have automated deployments, significantly speeding up your operations in comparison to manual deployments. Some examples of IaaS vendors include Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform. In these types of environments, the vendor is responsible for the infrastructure, but the users still have complete control over the Identity Access Management, data, applications, runtime, middleware, operating system, and virtual network.
Platform as a Service (PaaS)
Another cloud computing service delivery model is Platform as a Service (PaaS). PaaS is a subset of IaaS, except customers are only responsible for Identity Access Management, data, and applications and it removes the need for organizations to manage the underlying infrastructure. Rather than having the responsibility over hardware and operating systems as with IaaS, PaaS helps you focus on the deployment and management of your applications. There is less need for resource procurement, capacity planning, software maintenance, and patching. Some examples of PaaS include Windows Azure, Google AppEngine and AWS Elastic Beanstalk.
Software as a Service (SaaS)
Perhaps the most well-known of all three models is SaaS, where the deployment is redistributed to third party services. The customer’s only responsibilities are Identity Access Management, data, and the task of managing software. SaaS offers the entire package offered between IaaS and PaaS, as infrastructure, middleware, and applications deployed over the web can be seamlessly accessed from any place at any time, no matter the platform. Vendors of SaaS include CRM services like Salesforce and productivity software services like Google Apps. One major benefit of SaaS is that it reduces the costs of software ownership and eliminates the need for IT staff to manage the software so your company can focus on what it does best. Another benefit of SaaS that its relevance to businesses today, as SaaS is considered the best option for remote collaboration. With SaaS, your applications can be accessed from any geographical location and your company is not responsible for managing the hardware.
Choosing the Cloud Computing Model that is Right for You
Each cloud computing service model has different benefits to consider when determining the model that will work best for your business needs, projects, and goals.
While IaaS gives you complete control over your infrastructure, some businesses may decide they do not need to fully manage their applications and infrastructure on their own. IaaS is considered a good fit for SMEs and startups who do not have the resources or time to buy and build the infra for their own network. Additionally, larger companies may prefer to have complete control and scalability over their infrastructure, so they too may opt for IaaS for a pay-as-you go, remote option with powerful tools. One downside to IaaS is that it is more costly in comparison to PaaS and SaaS cloud computing models, yet it does minimize costs in the sense it eliminates the need to deploy on-premises hardware.
Reduced vendor lock-in
GUI and API-based access
Potential for vendor outages
The cost of training how to manage new infrastructure
PaaS is a good choice if you are looking to decrease your application’s time-to-market, because of its remote flexibility and accessibility. Thus, if your project involves multiple developers and vendors, each have quick accessibility to computing and networking resources through a PaaS. PaaS might also be used by a team of developers to test software and applications.
Rapid product development through simplified process
Eliminates need to manage basic infrastructure
Increased dependency on vendor for speed and support
SaaS is a feasible option for smaller companies that need to launch their ecommerce quickly or for short term projects that require quick, easy, and affordable collaboration from either a web or mobile standpoint. Any company that requires frequent collaboration such as transferring content and scheduling meetings will find SaaS convenient and accessible.
Automated provisioning/management of your cloud infrastructure
Allows for full remote collaboration
Reduced software costs
The 3 Cloud Computing Deployment Models
Another foundational concept of cloud are the deployment models. A deployment model is where your infrastructure resides and also determines who has control over its management. Like the cloud computing service delivery models, it is also important to choose the deployment model that will best meet the needs of your business.
There are three types of cloud computing deployment models:
A cloud deployment means your applications are fully run in the cloud and accessible by the public. Often, organizations will choose a public cloud deployment for scalability reasons or when security is not a main concern. For example, when testing an application. Businesses may choose to create or migrate applications to the cloud to take advantage of its benefits, such as its easy set-up and low costs. Additionally, a public cloud deployment allows for a cloud service provider to manage your cloud infrastructure for you.
An on-premises cloud deployment, or private cloud deployment, is for companies who need to protect and secure their data and are willing to pay more to do so. Since its on-premises, the data and infrastructure are accessed and managed by your own IT team. Due to in-house maintenance and fixed scalability, this deployment model is the costliest.
A hybrid cloud deployment connects cloud-based resources and existing non-cloud resources that do not exist in the cloud. The most common way to do this is between a public cloud and on-premises infrastructure. Through a hybrid cloud integration, you can segment data according to the needs of your business. For example, putting your highly sensitive data on-premises while putting less-sensitive data on the public cloud for accessibility and cost-effectiveness. This allows you to enjoy the benefits of the cloud while maintaining a secure environment for your data.
Determining the cloud computing service delivery model and deployment model best for your organization are both critical steps to the success of your company’s cloud computing journey. Get it right the first time by consulting with 2nd Watch. With a decade of experience as a managed service provider, we provide cloud services for your public cloud workloads. As an AWS Consulting Partner, Gold Microsoft Partner, and Google Cloud Partner, our team has the knowledge and expertise to efficiently guide you through your cloud journey. Contact us to learn more or talk to one of our experts.
In 2020, a year where enterprises had to rethink their business models to stay alive, Google Cloud was able to grow 47% and capture market share. If you are not already looking at Google Cloud as part of your cloud strategy, you probably should.
Google has made conscious choices about not locking in customers with proprietary technology. Open-source technology has, for many years, been a core focus for Google, and many of Google Cloud’s solutions can integrate easily with other cloud providers.
Kubernetes (GKE), Knative (Cloud Functions), TensorFlow (Machine Learning), and Apache Beam (Data Pipelines) are some examples of cloud-agnostic tools that Google has open-sourced and which can be deployed to other clouds as well as on-premises, if you ever have a reason to do so.
Specifically, some of Google Cloud’s services and its go-to-market strategy set Google Cloud apart. Modern and scalable solutions like BigQuery, Looker, and Anthos fall into this category. They are best of class tools for each of their use cases, and if you are serious about your digital transformation efforts, you should evaluate their capabilities and understand what they can do for your business.
Three critical challenges we see from our enterprise clients here at 2nd Watch repeatedly include:
How to get started with public cloud
How to better leverage their data
How to take advantage of multiple clouds
Let’s dive into each of these.
Ask any architect if they would build a house without a foundation, and they would undisputedly tell you “No.” Unfortunately, many companies new to the cloud do precisely that. The most crucial step in preparing an enterprise to adopt a new cloud platform is to set up the foundation.
Future standards are dictated in the foundation, so building it incorrectly will cause unnecessary pain and suffering to your valuable engineering resources. The proper foundation, that includes your project structure aligned with your project lifecycle and environments, and a CI/CD pipeline to push infrastructure changes through code will enable your teams to become more agile while managing infrastructure in a modern way.
A foundation’s essential blocks include project structure, network segmentation, security, IAM, and logging. Google has a multi-cloud tool called Cloud Operations for logs management, reporting, and alerting, or you can ingest logs into existing tools or set up the brand of firewalls you’re most familiar and comfortable with from the Google Cloud Marketplace. Depending on your existing tools and industry regulations, compliance best practices might vary slightly, guiding you in one direction or another.
Google has, since its inception, been an analytics powerhouse. The amount of data moving through Google’s global fiber network at any given time is incredible. Why does this matter to you? Google has now made some of its internal tools that manage large amounts of data available to you, enabling you to better leverage your data. BigQuery is one of these tools.
Being serverless, you can get started with BigQuery on a budget, and it can scale to petabytes of data without breaking a sweat. If you have managed data warehouses, you know that scaling them and keeping them performant is a task that is not easy. With BigQuery, it is.
Another valuable tool, Looker, makes visualizing your data easy. It enables departments to share a single source of truth, which breaks down data silos and enables collaboration between departments with dashboards and views for data science and business analysis.
Hybrid Cloud Solutions
Google Cloud offers several services for multi-cloud capabilities, but let’s focus on Anthos here. Anthos provides a way to run Kubernetes clusters on Google Cloud, AWS, Azure, on-premises, or even on the edge while maintaining a single pane of glass for deploying and managing your containerized applications.
With Anthos, you can deploy applications virtually anywhere and serve your users from the cloud datacenter nearest them, across all providers, or run apps at the edge – like at local franchise restaurants or oil drilling rigs – all with the familiar interfaces and APIs your development and operations teams know and love from Kubernetes.
Currently in preview, soon Google Cloud will release BigQuery Omni to the public. BigQuery Omni lets you extend the capabilities of BigQuery to the other major cloud providers. Behind the scenes, BigQuery Omni runs on top of Anthos and Google takes care of scaling and running the clusters, so you only have to worry about writing queries and analyzing data, regardless of where your data lives. For some enterprises that have already adopted BigQuery, this can mean a ton of cost savings in data transfer charges between clouds as your queries run where your data lives.
Google Cloud offers some unmatched open-source technology and solutions for enterprises you can leverage to gain competitive advantages. 2nd Watch has helped organizations overcome business challenges and meet objectives with similar technology, implementations, and strategies on all major cloud providers, and we would be happy to assist you in getting to the next level on Google Cloud.
Often times, organizations want to modernize their applications to increase agility and efficiency, jumpstart growth and accelerate time to market. They are looking to build applications, which adopt new application architectures and cloud-native services without disrupting the business. In many cases, some modernization may already be occurring in pockets throughout the organization, but the complexity of proprietary IT stack, dependencies on legacy applications, and slow speed of migration has inhibited organizations from gaining the desired outcomes.
To achieve your modernization goals while maintaining flexibility to choose where applications reside, Google Cloud created Anthos. Anthos is a 100% software solution, designed to work where you want – on-premise or in the cloud. It brings the same Google Kubernetes Engine you would find in Google Cloud to your data center, providing the maximum hybrid flexibility for application placement. By abstracting the infrastructure from the application, Anthos allows your development teams to focus on building applications, not managing infrastructure.
For organizations embarking on their modernization journey or for where adopting Kubernetes seems intimidating, Google has taken this into consideration with Migrate for Anthos. Migrate for Anthos performs the heavy lifting on your existing applications and containerizes applications that benefit from containerization. It automates the extraction of existing applications from servers and VMs into containers, without having to rewrite or re-architect applications, eliminating much of the complexity that has inhibited your modernization efforts.
Once you embrace and adopting Kubernetes, hybrid application placement becomes easier with Anthos. Google Anthos provides a unified management experience across deployments, making everything from your binaries and your application configuration to your security policies and rollback processes, portable between on-premises and other public clouds. As a result, instead of training all your teams on several platforms, you train them once, preserving your existing investments utilizing a common management layer to help your teams deliver quality services with low overhead.
To help you through your modernization journey, 2nd Watch has created Hybrid Cloud Solutions with Google Anthos. Designed to accelerate your modernization effort by operationalizing your organization on Anthos and implementing Kubernetes quickly, you can progress on your digital transformational journey at the pace that works best for your development teams and accomplishes your organizational goals.
With more than 10-years assisting clients in transitioning from legacy compute to highly agile cloud native teams, our proven methodology is designed to enable you to become a multi-cloud organization with a consolidated view, at a speed that works best for your business.
2nd Watch’s Hybrid Cloud Solutions with Google Anthos includes:
Set-up and configuration of Anthos
Migrate for Anthos
Istio and configuration management
Optimize security, observability, and resiliency
Creation of post migration image update process
It’s never been easier for your organization to adopt a multi-cloud application architecture. Whether you are just starting your transformation or already well into the process of modernizing your applications, Google Anthos allows you to consolidate all your operations across on-premises, Google Cloud, and other clouds, while giving you the flexibility to run and move applications where you need them without added complexity. Download our datasheet for more details.
-Dusty Simoni, Sr Product Manager, Hybrid Cloud
Assumes <100 workloads. Pricing based on actual time and materials. Google Anthos, infrastructure, and networking are sold separately. Kubernetes training, application modernization or re-architecture, high-availability, and multi-data center implementations are additional. Assumes Migrate for Anthos is utilized and only supported Linux VMs.
Everyone’s journey to the cloud is different. Before deciding your direction, you should consider your business goals, risk tolerance, internal skills, cost objectives, and existing technology ecosystem. For some, the choice is a 100% native cloud-first strategy on a single Cloud Service Provider (CSP). Others will use a mixture of services across multiple providers. And some others will choose a hybrid strategy in some form. For a hybrid approach, an interesting option worth considering is leveraging VMware Cloud (VMC) on AWS.
VMware Cloud on AWS is a great solution to consider whether you are integrating your on-prem work environment into the cloud, evacuating your datacenter, scaling datacenter extensions, looking at disaster recovery (DR), or focusing on remote workforce enablement.
What is VMware Cloud on AWS?
About three years ago, hundreds of engineers from VMware and AWS spent more than two years bringing the VMware Cloud solution to market. VMware Cloud on AWS refers to the VMware infrastructure stack or VMware cloud foundation. It encompasses the three infrastructure software pieces that VMware is known for: vSphere, NSX and vSAN. vSphere provides virtualization of compute, NSX is virtualization of the network, and vSAN virtualizes storage. VMC is an instance of the vCloud foundation being executed on AWS bear metal hardware. When you sign up for a VMware Cloud account, you can get access to the entire VMware stack in an AWS availability zone in just 90 minutes.
Traditionally, VMware has been in datacenters. Now, you can combine those servers into one piece of hardware. With AWS, you can now move functionality to the cloud and enjoy the many benefits of this platform.
1. Expanded functionality
There is so much more functionality in the VMware stack than in the cloud alone. There’s also more functionality in the cloud than you can build in your own environment. VMware Cloud on AWS is more than just a traditional VMware stack. It’s all the functionality of NSX, vSAN, and vSphere, plus the latest additions, at your fingertips, allowing you to always run the latest version of VMware to have access to the newest features. VMware takes care of the maintenance, upgrading, and patching, and with VMC being placed in AWS, you have instant access to all of the AWS cloud features in close physical proximity to your application, allowing you to experience improved performance.
2. Easy adoption
If you’re new to the cloud and have experience with VMware, you will easily be able to apply those existing on-prem skills to VMC on AWS. Because vShere on-prem is the same as the vSphere on AWS, it’s backwards compatible. The traditional management interface of the vCenter has the same look and feel and operates the same in the cloud as it does on-prem. These mirrored interfaces allow you to preserve the investment you have made in your existing VMware administrators, keeping headcount and employee costs down because you don’t have to hire for new skills or ask existing techs to increase their skillset. This quick familiarity lets you ramp up and use the service much faster than bringing in a completely new platform.
3. Agile scaling capability
After COVID-19 safety precautions sent 80-90% of the workforce home, organizations scrambled to enable and protect their new remote workers. Datacenters and BDi farms weren’t built to scale for the influx, and it’s just not possible to build additional datacenters as fast as necessary. Organizations needed to find already-built hardware and available datacenters and software that could meet their needs quickly. VMC on AWS solves the problem because it is built to scale without the limitations of on-prem environments.
4. Transition from CAPEX to OPEX
A fundamental change people are seeing from VMC on AWS is the ability to move from a capital expenditures (CAPEX) model to an operating expenditures (OPEX) model, freeing you from exceptionally long and expensive contracts for datacenters and DR locations.
With VMC, you can move to an OPEX model and spread your cost out over time, and the hardware, maintenance, and upgrades are no longer your responsibility. On top of that, the savings in headcount, manpower, and man hours creates a conversation between IT and financial staff as to what’s best for the overall organization.
5. Lower costs
Chances are, you’re already using VMware and recognize it as a premium brand, so if you’re looking at cost solely from a compute point of view, it might appear as if costs are higher. However, if you add up the individual expenses you incur without VMC – including real estate, hardware, software maintenance, headcount, management, travel costs – and compare that to VMC on AWS, you see the cost benefit ratio in favor of VMC. And additional resources are saved when you consider all the management roles that are no longer your responsibility. VMware also offers a hybrid loyalty program with incentives and savings for customers who are already invested in the VMware ecosystem.
Hybrid cloud strategies require a fair amount of effort and knowledge to construct, including for infrastructure, orchestration, application, data migration, IT management, and potential issues related to silos. There are a number of complexities to consider to enable seamless integration of a well-constructed hybrid cloud strategy. We recommend employing these 5 best practices as you move toward a multi-cloud or hybrid cloud architecture to ensure a successful transition.
Utilize cloud management tools.
Cloud management providers have responded to the complexities of a hybrid strategy with an explosion of cloud management tools. These tools can look at your automation and governance, lifecycle management, usability, access and more, and perform many tasks with more visibility.
Unique tooling for each cloud provider is especially important. Some partners may recommend a single pane of glass for simplicity, but that can be too simple for service catalogues and when launching new resources. The risk with going too simplistic is missing the opportunity to take advantage of the best aspects of each cloud.
Complete a full assessment of applications and dependencies first.
Before you jump into a hybrid cloud strategy, you need to start with a full assessment of your applications and dependencies. A common misstep is moving applications to the public cloud, while keeping your database in your private cloud or on-prem datacenter. The result is net latency drag, leading to problems like slow page loads and videos that won’t play.
Mapping applications and dependencies to the right cloud resource prior to migration gives you the insight necessary for a complete migration with uninterrupted performance. Based on the mapping, you know what to migrate when, with full visibility into what will be impacted by each. This initial step will also help with cloud implementation and hybrid connect down the line.
Put things in the right place.
This might sound obvious, but it can be challenging to rationalize where to put all your data in a hybrid environment. Start by using the analysis of your applications and dependencies discussed above. The mapping provides insight into traffic flows, networking information, and the different types of data you’re dealing with.
A multi-cloud environment is even more complex with cost implications and networking components. On-prem skills related to wide area network (WAN) connectivity are still necessary as you consider how to monitor the traffic – ingress, egress, east, and west.
Silos can be found in all shapes and sizes in an organization, but one major area for silos is in your data. Data is one of the biggest obstacles to moving to the cloud because of the cost of moving it in and out and accessing it. The amount of data you have impacts your migration strategy significantly, so it’s critical to have a clear understanding of where data may be siloed.
Every department has their own data, and all of it must be accounted for prior to migrating. Some data silo issues can be resolved with data lakes and data platforms, but once you realize silos exist, there’s an opportunity to break them down throughout the organization.
An effective method to breaking down silos is by getting buy-in from organizational leaders to break the cultural patterns creating silos in the first place. Create a Cloud Center of Excellence (CCoE) during your cloud transformation to understand and address challenges within the context of the hybrid strategy across the organization.
Partner with proven experts.
Many companies have been successful in their hybrid cloud implementation by leveraging a partner for some of the migration, while their own experts manage their internal resources. With a partner by your side, you don’t have to invest in the initial training of your staff all at once. Instead, your teams can integrate those new capabilities and skills as they start to work with the cloud services, which typically increases retention, reduces training time, and increases productivity.
Partners will also have the knowledge necessary to make sure you not only plan but implement and manage the hybrid architecture for overall efficiency. When choosing a partner, make sure they’ve proven the value they can bring. For instance, 2nd Watch is one of only five VMware Cloud on AWS Master Services Competency holders in the United States. That means we have the verified experience to understand the complexities of running a hybrid VMware Cloud implementation.
If you’re interested in learning more about the hybrid cloud consulting and management solutions provided by 2nd Watch, Contact Us to take the next step in your cloud journey.