Welcome!

Java IoT Authors: Zakia Bouachraoui, Elizabeth White, Pat Romanski, Liz McMillan, William Schmarzo

Related Topics: @CloudExpo, Java IoT, @DXWorldExpo

@CloudExpo: Blog Feed Post

Change Management Got Bigger By @DMacVittie | @CloudExpo #Cloud

Today, we have to have far more thorough change analysis in place than most organizations needed 20 or 10 or even 5 years ago

While we were busy throwing parts of our organizations into the cloud, and (for those who don’t count it as cloud) SaaS, while we were moving parts of our organization over to Python, or Node, or Swift, while we were looking into Software Defined Everything, and containers started sounding like the hosting spot for a humongous jigsaw puzzle, something was growing that we should be paying more attention to.

The growth of these technologies and many more share one thing… A dependence upon other technologies. And those dependencies cascade as we get into ever more layered systems. Think of the number of technologies required to make a simple (in terms of use) application – like my own employers’ Stacki automated datacenter provisioning software –  work. Or perhaps more fitting for those on the other end of the spectrum, think of all of the technologies required to make an Android app (and its dev tools) work.

And if any of those underlying technologies goes through a fundamental change – no matter how well meaning or necessary the change – the cascade effect gets ugly quickly.

That means that today, we have to have far more thorough change analysis in place than most organizations needed 20 or 10 or even 5 years ago. Agile development, for all the good it brings in rolling out features at a steady, measurable rate, exacerbates this problem by making change more frequent, shortening the timeline before you have to worry about the changes in underlying technologies.

If you’re wondering what “fundamental changes” I’m talking about, here are three simple examples.

The first is easy. Write a web service in Python 2.x. Now access that web service in Python 3.x. It doesn’t work as expected at all. The reason it doesn’t is valid… 2.X was not internationalized, 3.X is – or more to the point, Unicode support and internal representations of said support are better. That was the impetus for 3.X to exist in the first place. But that doesn’t change the fact that interoperability issues abound between two versions of the same language… Preforming actions that are supposed to work between any two languages.

The next is more subtle, but just as impactful. The change to Red Hat 7.0 caused some amount of consternation in the Big Data world, while the changes needed to support containers natively caused other apps to have to adjust before offering upgrade paths.

And the third example I’ll offer is the one that spurred this article on in the first place. Oracle replaced all of the Date/Time classes to better support internationalization, and more importantly to be thread safe. Unfortunately, those changes did not propagate to JDBC, so any enterprise use of Java has to go through a conversion process before upgrades can occur. JDBC still expects the Date and Time objects, but they’ve been deprecated… So code must be (temporarily, one assumes) introduced to translate between them.

No matter how you adapt to these changes, they slow down the process, introduce bugs, and potentially make your IT look bad, unless you have a plan, and the time to execute it. In the agile world, time to execute is the killer. On top of normal goals for a stretch, you now have to introduce changes coming from beneath your application.

This is where change management shines. While I’m not a fan of delaying adoption of newer versions of support/infrastructure, the goal of the enterprise must be to manage the volume of change – particularly temporary change – that underlying tools, OS’s, databases, networks, etc introduce. A thorough understanding of what those changes will mean to apps, servers, switches, etc. is almost mandatory. When you get to a massive technology like OpenStack or Hadoop, the problem gets worse – because the law of multiplication drives the number of changes up commensurate with the number of underlying technologies.

You see this in both SSL and DNS in-the-wild. Over the last few years there has been heavy pressure to upgrade both, and yet if you follow security people, you know that there is a heavy inertia to upgrading. That is because organizations are uncertain what the impacts will be, or don’t have the hours to adjust the entire infrastructure to get there. These being security – an important aspect of change when improving – we can kind of get a gauge for the level of resistance to overall infrastructure change in most organizations. It’s huge. Generally speaking, when the change must occur, then it will.

Changes introduced in underlying technologies are normally aimed at improving the overall environment – be it general usability (Python above), performance (Java above), new feature implementation (Red Hat above), or security (DNS and SSL above).

Dealing with this type of issue is part of what Change Managers do, it has just gotten harder as the dependency tree of useful software has grown. How many apps out there are impacted by a change to underlying Java classes? How many purchased apps that your org doesn’t have source for? While we talked of one change to Red Hat 7.0, there were a ton more changes, how do those impact a given org’s servers?

We’ve gotten pretty good at the “dealing with” part – Tools like Stacki can reimage your servers, a subclass of LocalDate can be created that contains automatic conversions to Date until JDBC catches up, any reputable Python group will tell you to pick 2.X or 3.X and run with it… The list goes on.

What we’re not as good at is analysis. It’s tough, and lots of organizations don’t have a change management function, but rather have individuals about the organization perform the task as part of their daily job. This is part of the reason for inertia. There are of course a lot of other reasons – like the productive hours spent changing because the ground shifted instead of because you’re forwarding business cases. But again, Stacki can upgrade servers – one or one thousand – in minutes or hours, so this is less of an inertia issue than the cost/benefit analysis.

Give someone Change Mangement responsibility. You know your org, but I like putting them in PM, because changes cascade apps and infrastructure internally too, so often these are cross-team projects. Let them determine everywhere that needs to change to adapt for a given underlying technology change, and then offer recommendations. The fact is that weakness in SSL should never be tolerated at organizations for security reasons – particularly large or international organizations – but it is. Knowing the real cost of upgrading versus the risk management that it offers would be a great first step to setting a timeline for your upgrade process. When the change is inevitable… “Either we use RHEL/CentOS 7, or container support is limited, and we need high-use containers”, this same individual can weigh the cost of point solutions (install this rack with RHEL 7) and upgrade solutions (We can move 89% of our RHEL servers to 7 with no impact). These assessments need to occur, the question is whether you have an individual who has some (or all) of their time dedicated to figuring this stuff out, so you know before it becomes a “Oh. We have to upgrade X…” analysis. Those last minute “we must” changes are the ones that’ll get you. Every. Single. Time.

So think about it. Change is coming whether you want it or not. Either from the side (cloud, etc) or from beneath you (SSL, etc). Be prepared. Know what it will take before you upgrade, and be consistent. A large org has enough trouble with multiple everything, don’t multiply it with multiple versions of multiple everything unless there is a definitive benefit that makes sense for the larger org.

Read the original blog entry...

More Stories By Don MacVittie

Don MacVittie is founder of Ingrained Technology, A technical advocacy and software development consultancy. He has experience in application development, architecture, infrastructure, technical writing,DevOps, and IT management. MacVittie holds a B.S. in Computer Science from Northern Michigan University, and an M.S. in Computer Science from Nova Southeastern University.

IoT & Smart Cities Stories
In his general session at 19th Cloud Expo, Manish Dixit, VP of Product and Engineering at Dice, discussed how Dice leverages data insights and tools to help both tech professionals and recruiters better understand how skills relate to each other and which skills are in high demand using interactive visualizations and salary indicator tools to maximize earning potential. Manish Dixit is VP of Product and Engineering at Dice. As the leader of the Product, Engineering and Data Sciences team at D...
Dynatrace is an application performance management software company with products for the information technology departments and digital business owners of medium and large businesses. Building the Future of Monitoring with Artificial Intelligence. Today we can collect lots and lots of performance data. We build beautiful dashboards and even have fancy query languages to access and transform the data. Still performance data is a secret language only a couple of people understand. The more busine...
Nicolas Fierro is CEO of MIMIR Blockchain Solutions. He is a programmer, technologist, and operations dev who has worked with Ethereum and blockchain since 2014. His knowledge in blockchain dates to when he performed dev ops services to the Ethereum Foundation as one the privileged few developers to work with the original core team in Switzerland.
René Bostic is the Technical VP of the IBM Cloud Unit in North America. Enjoying her career with IBM during the modern millennial technological era, she is an expert in cloud computing, DevOps and emerging cloud technologies such as Blockchain. Her strengths and core competencies include a proven record of accomplishments in consensus building at all levels to assess, plan, and implement enterprise and cloud computing solutions. René is a member of the Society of Women Engineers (SWE) and a m...
Andrew Keys is Co-Founder of ConsenSys Enterprise. He comes to ConsenSys Enterprise with capital markets, technology and entrepreneurial experience. Previously, he worked for UBS investment bank in equities analysis. Later, he was responsible for the creation and distribution of life settlement products to hedge funds and investment banks. After, he co-founded a revenue cycle management company where he learned about Bitcoin and eventually Ethereal. Andrew's role at ConsenSys Enterprise is a mul...
Whenever a new technology hits the high points of hype, everyone starts talking about it like it will solve all their business problems. Blockchain is one of those technologies. According to Gartner's latest report on the hype cycle of emerging technologies, blockchain has just passed the peak of their hype cycle curve. If you read the news articles about it, one would think it has taken over the technology world. No disruptive technology is without its challenges and potential impediments t...
If a machine can invent, does this mean the end of the patent system as we know it? The patent system, both in the US and Europe, allows companies to protect their inventions and helps foster innovation. However, Artificial Intelligence (AI) could be set to disrupt the patent system as we know it. This talk will examine how AI may change the patent landscape in the years to come. Furthermore, ways in which companies can best protect their AI related inventions will be examined from both a US and...
Bill Schmarzo, Tech Chair of "Big Data | Analytics" of upcoming CloudEXPO | DXWorldEXPO New York (November 12-13, 2018, New York City) today announced the outline and schedule of the track. "The track has been designed in experience/degree order," said Schmarzo. "So, that folks who attend the entire track can leave the conference with some of the skills necessary to get their work done when they get back to their offices. It actually ties back to some work that I'm doing at the University of San...
When talking IoT we often focus on the devices, the sensors, the hardware itself. The new smart appliances, the new smart or self-driving cars (which are amalgamations of many ‘things'). When we are looking at the world of IoT, we should take a step back, look at the big picture. What value are these devices providing. IoT is not about the devices, its about the data consumed and generated. The devices are tools, mechanisms, conduits. This paper discusses the considerations when dealing with the...
Bill Schmarzo, author of "Big Data: Understanding How Data Powers Big Business" and "Big Data MBA: Driving Business Strategies with Data Science," is responsible for setting the strategy and defining the Big Data service offerings and capabilities for EMC Global Services Big Data Practice. As the CTO for the Big Data Practice, he is responsible for working with organizations to help them identify where and how to start their big data journeys. He's written several white papers, is an avid blogge...