For many organizations the cloud holds a promise of delivering better applications faster and some even argue more securely. While private clouds democratize access to the underlying compute, storage and network resources presented by a hypervisor they also introduce unpredictable demand on the underlying environment often slowing down the time to get resources up and ready for end-users to leverage.
One of the biggest challenges in looking over the Amazon Web Services catalog of available products, is understanding what everything is, and how it all works. Both individual guides and inter-service guides are spread around the internet. This makes searching out the right guides a challenge in many cases, until the open-guides came along!
I’ve seen a few tweets around about Microsoft and the open source journey, and it made me take a look back at the Microsoft account on GitHub to see whether there was something that I’d missed. Whether or not there are all new projects loading up onto GitHub or not, there as absolutely a lot going on in a lot of different repositories. This is great!
What is “Serverless Computing”
By now we are all familiar with the terms SaaS, IaaS and PaaS but prepare yourself for a new wave of offerings “as a service”. Serverless computing, Event Driven Computing or Function as a Service (FaaS for short) is an emerging trend that cloud providers are offering to their clientele. While the name sounds counterintuitive, servers are still involved but in a revolutionarily different way.
There was a very interesting conversation at an event I attended the other day. The focus was around getting to the cloud. Questions that came up were the usual ones that you would expect, including the classic “what is the ROI with the public cloud?"
Today there are more choices than ever of where and how to run applications. Virtualization has made it easy to spin up a VM, containers make deployment even faster and public cloud services remove the need to procure, rack and mount hardware altogether.
Last year was the year of the Openstack. People talked about it, they deployed it, they tested it, and they had grandiose plans on rolling it into production. Few in my experience succeeded on schedule or without technical challenges and difficulties in skill-set gaps on their teams. While this is still being leveraged in many of my customer accounts; I am finding more and more people gravitating to alternatives like Azure, AWS and for elastic compute and development project needs.
We've looked at traditional approaches to optimizing costs in AWS and why these tactics often fail. This week, we investigate what AWS recommends organizations consider when seeking to lower costs in the public cloud, based on a presentation given at the AWS Enterprise Summit in Boston.
We covered a bit of the operational docs in our first article, but this is a chance to tap into a few of the actual technical features that have landed in Newton. There are also some serious improvements in existing parts of the ecosystem which pack more reliability and resiliency into the infrastructure.
October 6th marked the calendar for the OpenStack community as release day for OpenStack Newton. To start us off on learning about the OpenStack environment, a great job was done on what I’d say is the OpenStack 1-2-3.