Microsoft announced, at Inspire 2018, some additions and changes to the Microsoft Certifications surrounding the Microsoft Azure cloud that are starting to be released, and will be expanded upon in the near future around the timing of the Microsoft Ignite 2018 conference in September 2018. These announcements were made in the LER01 – The future of modern learning session at MS Inspire 2018, in addition to a blog post on the Microsoft Learning blog written by Liberty Munson. Read More
Microsoft continually updates the content of the different Microsoft Azure certification exams, but it’s been almost 2 years since they really updated the Microsoft Certification paths to be more Azure focused / integrated. Great news is that Microsoft is making further changes to keep improving the various Microsoft Azure Certifications and associated exams that are offered. During the Microsoft Inspire 2018 conference, the Microsoft Learning team announced the introduction of this brand new Azure certification track tailored for Azure Administrators. Read More
The AZ-102 Microsoft Azure Administrator Certification Transition certification exam tests and validates your expertise as an Azure Administrator around managing cloud services that span storage, security, networking, and compute capabilities within the Microsoft Azure cloud. This exam provides a upgrade / transition path from to the Azure Administrator certification for anyone who has already passed the older, existing 70-533 Implementing Azure Infrastructure Solutions certification exam. Read More
The AZ-101 Microsoft Azure Integration and Security certification exam tests and validates your expertise managing and securing cloud services that span storage, security, networking, and compute capabilities within the Microsoft Azure cloud. This is the second in a set of exams that make up the new Azure Administrator certification track. Read More
The AZ-100 Microsoft Azure Infrastructure and Deployment certification exam tests and validates your expertise as an Azure Administrator around managing cloud services that span storage, security, networking, and compute capabilities within the Microsoft Azure cloud. This is the first in a set of exams that make up the new Azure Administrator certification track. Read More
There’s so much competition in the cloud computing space. According to Forbes, the Cloud Providers at the top in the current “Cloud War” are Microsoft, Amazon, and IBM, followed by many other players in the industry. This battle is made up of these major corporations spending Billion or Trillions of dollars investing in cloud innovation and advancement. While each of these companies would like to be the victor and win the “Cloud War”; it’s probably best for everyone that there is no clear “winner” in the end.
Polynimbus is the term used to refer to the strategy of an organization utilizing multiple Cloud Providers. Polynimbus is also referred to as “Multi-Cloud”. This enables organizations to utilize the best features and pricing of each cloud provider for different solutions where they fit the solutions, data, and workload best. This is an extremely common pattern in use by all major corporations as they migrate to the Cloud to replace their on-premises datacenters.
Polynimbus Cloud Strategy: A cloud computing strategy that involves multiple Cloud Providers / Vendors.
Polynimbus is not just a great strategy to gain the benefits and features of multiple Cloud Providers within a single organization, but it’s something that benefits the technology industry in many other ways too.
Benefits of Polynimbus for the Enterprise
There are a number of benefits that a Polynimbus cloud strategy brings. These benefits range from effecting a single organization, all the way to effecting the entire Internet.
Here’s a list of the most notable benefits that a Polynimbus strategy brings to an individual organizations overall cloud strategy:
- Time to Market – Services and Feature comparison and trade-offs are able to be made to choose the best cloud provider for deploying, hosting, and managing solutions in regards to cloud capabilities, and Developer/IT Pro ramp up curve and time to market.
- Cost Optimization – Cost comparisons and trade-offs are able to be made to choose the best cloud provider for deploying, hosting, and managing solutions in regards to hosting cost and budgets.
- Integration Between Clouds – While most applications and systems will be most appropriately hosted utilizing a single Cloud Provider for that single system, there are times where it may be appropriate to utilize services and features across multiple clouds to best build, deploy, and manage that single system.
The above benefits of Polynimbus may sound a bit simple, but they are pretty broad reaching in their effect on an organization. The benefits factor into some major implications to the future of the solutions hosted, as well as the overall cloud strategy an organization is adopting.
Benefits of Polynimbus for the World
The overall Internet and technology industry benefits of Polynimbus Here’s a list of the most notable benefits that a Polynimbus strategy brings to the Internet, the overall technology industry, and beyond:
- Decentralized / Distribution of Control – While each Cloud Provider does implement multiple data centers that are geo-distributed around the world, they are still owned an operated by that single corporation that controls that particular Cloud Provider platform and ecosystem. The best design the Internet has come up with is to build the DNS system as a distributed system spread all across the world. This same strategy is probably best for Cloud Computing as well, so that no single entity is in control of the entire Cloud. This is one benefit that comes from the competitive nature of the current state of the cloud.
- Competition – Just all other industries benefit from competition, the technology industry benefits too. Having multiple players in the Cloud Provider space increases the amount of competition between players. With this increased competition comes an increase the the variety and push for innovation across the different Cloud Computing platforms being offered. If you look at the history between Microsoft and Amazon (for example) you’ll see they’ve been leap frogging each other on Cloud features and capabilities over the years. This offers great variety and innovation for all companies to take advantage of regardless of the Cloud Provider they’re using.
A Polynimbus Future
Just about every organization adopting the Cloud, as well as migrating their on-premises or co-lo hosted data centers to the Cloud, are adopting a Polynimbus Strategy involving multiple Cloud Providers. They might only be adoption a single Cloud Provider, such as Microsoft Azure, at first. However, down the line the pattern in the industry is showing that corporations are adopting multiple Cloud Providers.
Just about every organization adopting the Cloud, as well as migrating their on-premises or co-lo hosted data centers to the Cloud, are adopting a Polynimbus Strategy involving multiple Cloud Providers.
One such example of a major corporation utilizing a Polynimbus Strategy is that of Apple. For a long time Apple was utilizing both Amazon AWS and Microsoft Azure to host the backend of its iCloud service. More recently, there’s been indication that Apple may not be using Microsoft Azure anymore, as they may have migrated to using a combination of Amazon AWS and Google Cloud instead.
It can be extremely beneficial to utilize a Polynimbus Strategy, as well as a Hybrid-Cloud Strategy that still make use of the on-premises data center investments where they make sense. Going all in on any specific technology or platform is generally not the best approach to building out any solution. It’s best to choose the right tool for the job at hand, and to utilize multiple tools to truly customize the solution to fit the need and requirements in the best possible way.
It can be extremely beneficial to utilize a Polynimbus Strategy, as well as a Hybrid-Cloud Strategy that still make use of the on-premises data center investments where they make sense.
If you have any suggestions on designing a Polynimbus Strategy, Hybrid-Cloud Strategy, or Both, please post them in the comments. I’m sure everyone joins me in their eagerness to hear the communities suggestions on what to keep in mind when designing your organizations Polynimbus and Hybrid Cloud strategies.
History Fact: The term “Polynimbus” used to refer to a “Multi-Cloud” strategy of adopting multiple cloud providers / vendors was first coined by John Adams in 2016 while he was working as a Senior Cloud Solutions Architect at Opsgility.
Microsoft Project Natick is an innovative research project to discover new ways of hosting datacenters underwater. The goal of this research project is to determine the feasibility of subsea datacenters powered by offshore, renewable energy. Since 50% of the Earths population lives near the coast, this has potential to host data and compute capacity for Cloud computing much closer to customers and end users. There are also some other benefits as well.
Automate Everything. That’s my new mantra, and it should be yours…
Like many of you, I’m an infrastructure guy and grew up with the crutches of setup.exe and the massive installers that MSFT built in the late 90’s and 2000’s. But, that was then, and today all of us need to become DevOps engineers! It used to be when we built servers they would have a lifespan of many years, but now there is a new type of VM that might only live for a day or even less.
The concept of deleting a server would have scared the daylights out of me in 2002!? Yikes!
In this new world of Azure, we should be building VMs that are purpose-built and automated in their deployment end to end. We want the teams that are consuming these servers to be ready to work as soon as they login.
Windows, Linux, and Azure provide us with many tools to make that happen such as ARM templates, PowerShell or Yum and Apt on Linux. These tools can work together with the custom script extension for Windows or Linux to build out our VMs. Read More
When I first heard that you could run nested VMs with Azure, I ran over to my laptop to deploy one of those shiny new Version 3 VMs!
Once my Host was provisioned, I got right to work. Quickly adding the Hyper-V role and after a quick reboot, I started downloading ISOs! And before you know it I was disappointed. Yeah, I had a VM running, but after searching the internet for hours, I gave up. I never could get the thing talking to the Internet.
Well, fast forward a few months and a client of mine asked if we could build a self-provisioning Nested Hyper-V Host in Azure that would pull down pre-configured VMs and start them with only one click? I was excited. There is nothing cooler than getting to figure something out while you are getting paid. Well, it wasn’t easy to figure out, but what I have for you here is the fruit of that labor! Read More
This is top of mind for everyone these days and Azure has many security features. Today we are going to explore the world of Network Security Groups (NSGs) and their use on Virtual Machines and traffic into and out of Virtual Networks.
A network security group (NSG) is a networking filter (firewall) containing a list of security rules allowing or denying network traffic to resources connected to Azure VNets. These rules can manage both inbound and outbound traffic. NSGs can be associated to subnets and/or individual Network Interfaces attached to ARM VMs and Classic VMs. Each NSG has the following properties regardless of where it is associated:
- Name for the NSG
- Azure region where the NSG is located
- resource group
- Rules either Inbound or Outboard defining what traffic is allowed or denied
When a NSG is associated to a subnet, the rules apply to all resources connected to the subnet. Traffic can be further restricted by also associating a NSG to a VM or NIC. NSGs that are associated to subnets are said to be filtering “North/South” traffic (in other words, packets flowing in and out of a subnet). NSGs that are associated to Network Interfaces are said to be filtering “East/West” traffic (in other words, how the VMs within the subnet connect to each other). Read More