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)(Read Less)
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.
Oracle have been quietly building out their next generation cloud environments, building up a cloud practice with seasoned professionals that includes Ex-VCE, VMware and AWS personal. They have released a completely new version of their IaaS layer cloud. Dipping into their not insignificant loose pocket change to make several key purchases or acquisitions this year.
Now in what should be their last acquisition of 2016 they have now acquired Dyn for an undisclosed amount; but according to Dan Primack, a former senior editor at Fortune it is expected to be in the region of $600million.
Recently, I made two interesting support requests, each to a different company. Both companies asked for the output of many different commands and log files. Both balked once I explained my organization’s security policy. The policy reads simply:
No anonymized data shall be delivered to a 3rd party.
It is a simple statement, but it has a powerful effect on all data being delivered to third parties, even for support. It implies that all user, machine, and service identifiers must be tokenized, encrypted, or outright removed. What must truly remain anonymous within our data? This is not simply a support question, but rather a major issue with all data today. Do we even know what is in our data? Do you?
There is no doubt that the pace of business change is not slowing. With this business rate of change comes the need for business applications to change at great speed. What may be less visible is the direct relationship between the speed of application change and the need for new application architectures.
My friend and colleague Alastair Cooke recently published an article entitled Advanced Simplification: You Want It. In it, he argues that simplification is something that “deep geeks tend to scoff at” while at the same time embracing the wizards and silent install scripts that help them manage applications and platforms and deploy them into their environments.
We are all moving to the future. The election has, hopefully, forced us to rethink basic fundamentals of society. Individuals are usually easy to deal with, but larger and larger groups are much harder. Data scale changes everything. Even Isaac Asimov had this in mind when he wrote the Foundation trilogy. In his case, scale worked to smooth out predictions. We are not at that scale yet; hopefully, we will reach it. However, our data has far exceeded the scale we take for granted. Let us think about scale. What is high scale to you? For some businesses, high scale might mean a few hundred million queries and associated records a day. For others, it’s tens of billions of queries and ten times that in records a day. Where do you fit? As your application scales, what do you need to consider?
For half of the nation, it has been a day of shock and dismay. It may be that way for a while now. In the meantime, as you journey to the hybrid cloud, you need to get a handle on costs—and not just the costs of migrating to the cloud, but also those associated with training, documentation, maintaining institutional knowledge, data management, legal, and development. This includes the raw costs of the service on a per-day, -hour, or -minute basis, or by a megabyte or gigabit measurement, whichever the cloud supports. How do you begin to get a handle on costs? It is easy to say the cloud will be cheaper, but proving it is another matter. You should not be in shock or dismay when you see your cloud bill.