How is artificial intelligence development going in your environment? That question might make you pause for a moment as you ponder the idea and then find yourself scratching your head wondering what artificial intelligence (AI) I could possibly be referring to. Let me present this construct. Artificial intelligence, much like cloud computing, has a definition that varies depending on who you are talking to.
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.
I’m going to diverge ever so briefly from my “Reversed Assumptions” posts to share some happenings in this current engagement I’m on and to tie in some of the previous posts on design and architecture. This post focuses on what architecture is and what it isn’t. As I have engaged with many different sizes of customers over the years, one thing remains true: architects and architecture are many things to many people. There has been a lot of talk and debate on this, and I thought it necessary to be sure about what architecture truly is, and who is qualified to practice it.
On January 5, 2016, I was joined by Mike Foley, senior technical marketing architect for VMware vSphere Security, and Kapil Raina, HyTrust VP of product marketing, on the Virtualization and Cloud Security Podcast to discuss moving to a hybrid cloud IaaS model. As always, we strive to provide actionable advice. The key question we tried to answer was “Can you just extend your security into your cloud?” The answer was not as simple as one would expect. Have a listen and let us know what you think. In the meantime, here are our thoughts.
No matter how much technology we have, everything is about people. Even the best tools and automation can fail if the people operating them are not good at IT. Often we buy tools to fix problems, only to find that the tool is not the solution. The problem is not with the tool: more often, there is a problem with the people who operate the tool. Many times, there is also a problem with the people who manage the people who operate the tools.
The plain fact is that no matter how hard one entity is to deal with, it’s exponentially harder to deal with more than one. Everything is more complex when you go from one thing to more than one thing. The additional complexity may not be visible, or detectable, or appear to cause problems, but it’s still there and needs attention paid to it. At some point, when scaling begins to bite, problems inevitably appear.
Will 2017 be the year of the self-healing data center? One might consider this to be the holy grail of IT operations: having an infrastructure that can, to a certain level, maintain and resolve issues as they arrive.