I spent the last couple of weeks preparing for the Amazon Web Services Certified Solutions Architect – Associate exam. Coming from a long history of on-premises data centers, I find the messaging and training from AWS to be totally different. In VMware training, we spent a lot of time looking at designing and setting up networking and storage. The remaining time was spent creating and managing VMs on the infrastructure. In more advanced courses, we looked at automating these configurations. More recently, courses have covered deploying software-defined networking (SDN). But always, we directed our effort toward making sure the VM was up and getting the resources it wanted. In Amazon Web Services, the ability to deploy vast numbers of VMs and have multi-tenant SDN is a given. It’s not even the interesting part of the AWS platform. AWS is all about the services that supplement the applications inside your VMs.
Transformation & Agility
Transformation & Agility concerns the utilization of the technical agility derived from the benefits delivered by virtualization and cloud computing, coupled with Agile Development practices that improve business agility, performance, and results. This includes the agility derived from: (Read More)
- The implementation of Agile and DevOps methodologies
- The application and system architectures
- The implementation of IaaS, PaaS, and SaaS clouds
- Monitoring of the environment, coupled with processes for resolving problems quickly
- Having continuous availability through the use of high-availability and disaster recovery products and procedures
Transformation covers the journey from A to Z and all points between: how you get there and the roads you will travel; how decisions made on day zero or one, or even day three, will affect later decisions; and what technical, operational, and organizational pitfalls can be associated with an implementation. We examine what tool sets are required for Agile Cloud Development, and it delves into other aspects of Agile Development that integrate with cloud computing, SaaS, and PaaS environments, including DevOps, Scrum, XP, and Kanban.
Cloud this, cloud that…it seems that the cloud will heal all your woes. But will it really? Some vendors are using the term “cloud” to signify various services, such Software as a Service (SaaS), private cloud, public cloud, hybrid cloud, and more. With so many clouds, how can you be sure that you’re getting the right cloud for you or whether you even need a cloud?
There has been a rash of new web UIs based on HTML5. Is a web UI the same as an API? Can we assume that a new HTML5 web UI is making use of an API on the back end, creating a new API, or is it using an older API? Presenting a web-scale UI today usually means an HTML5 UI. In many ways, this is better than the security bug-ridden flash APIs that existed in the past. Is this really about graphical front ends, user experience, or APIs? Or is it a question of all three?
Data drives the modern business. It drives the modern development process. And it drives IT operations analytics in the NOC and the SOC. This raises the questions “Who owns all this data? Do data sovereignty rules apply?” Data is everywhere, and it is used in many ways. In many cases, the same data is used in multiple ways by distinctly different groups, working methods, and ivory towers.
The IT industry is abstracting everything it can, from hardware, to networking, to storage and more. “Abstract and build an API, and the world becomes better” seems to be the motto. Abstraction has become the goal of many subsystems. Many people seem to believe that if you move everything to software, everything will be better—and that if you use the API, things will move faster. This is all true, up to a point. Abstraction is a good thing, and we are now seeing levels of abstraction even within the hardware itself. This is also a good thing.