Skip to main content

Agility Has Its Limits

Automation and orchestration have given us free two-day shipping via Amazon Prime; next day shipping via the major postal companies; delivery via Uber or drone; and so on. These are all concepts that we are either intimately familiar with as consumers of these services or at least are cognizant of them because of news reports, TV commercials or YouTube videos.

Convenience and Digital Transformation

The value of convenience cannot be overstated.  However, there will always be times when these methods of delivery will not be enough.  For example, a freak snow blizzard in my area wasn't a big deal for me since I have snow removal equipment.  But as I drove past kids sledding in the field at the end of the street I wanted to buy a sled for my children also.  Next day shipping wouldn't have satisfied my need to have this now. Of course, Uber or drones could have delivered such an item theoretically.  But unless you live in NYC or a similarly sized metropolitan area and the goods purchased were something that either service would deliver then you're still forced to get in your car and drive to the nearest Walmart.

Measuring your way to revenue
It is during times like these that we must keep in the proper perspective the benefit that agility from a technology perspective gives a company.  For online shopping, the ability to deliver new functionality on an as-needed basis is critical to staying ahead of the competition.  For example, Amazon has a production deployment once every 25 seconds on average. For the brick and mortar companies, however, the need for agility is somewhat different since the quality of the end user experience isn't dictated by how good the Point of Sale software looks.  The focus in this situation is in the quality of the in store inventory, the cleanliness of the store, the helpfulness of the staff, etc.

Regardless of what defines "a quality experience" for a business, it can be measured.  And if it can be measured, then the measurements can be gathered and analyzed.  And if the measurements can be gathered and analyzed, then there is a need for the gathering and analysis.  This need exists whether you are a brick and mortar business, an online business, or a hybrid of the two.  The results can be stunning.
  • Take Netflix, for example.  Netflix does real time analysis of their customers' viewing habits to suggest new movies they may want to watch.  This starts with an ETL process that gathers the data and normalizes it into a format that is more easily digestible by the balance of the algorithmic analysis engine that results in recommendations.

  • Or consider LinkedIn.  LinkedIn does real time analysis of their users' network to suggest people that they may know based on degrees of separation.  This starts with several ETL processes that run on Hadoop, Teradata, and other data sources to enable this functionality to work.

  • Finally, look at AMC Theatres.  AMC does real time analysis of ticket and concession sales to automate their social media feeds.  This starts with an ETL process on Hadoop to gather, normalize, and process information to post updates to various social media sites with no user intervention.
Digital Growth

Anything that defines "a quality experience" for a business is quantifiable and should be measured. Why not? After all, this need exists whether you are a brick and mortar business, an online business, or a hybrid of the two like AMC. The process of measuring, gathering, analyzing and reporting unearths what is and is not working so success can be capitalized on in real time.

As you can see from the examples above, the results can be stunning. But the quantity of data that these companies generate means none of this would be possible without data automation, which is geared specifically at real-time execution of jobs to gather and then process large amounts of data in real-time.

Orchestration Backbone

There are a number of platforms to process large amounts of data (Hadoop, Hortonworks, and Cloudera, to name a few). However, the orchestration to coordinate the activities around gathering and reporting, is critical. Without it, you would be stuck with the task of building a custom set of solutions to do these two very important activities. It is this orchestration that distinguishes a large data processing platform like Hadoop from a data automation platform that enables you to effect a change in your company based on what the data contains.

The other thing all the above examples have in common? They all chose Automic to provide the orchestration capabilities to allow them to transform their businesses into something that responds in real time to the needs of their customers and users.

As Vijay Aruswamy, Big Data Operations at LinkedIn, put it, “We're using Automic to automate data transformation on Hadoop, Teradata, User Input and External sources of information. It supports our data driven products like ‘People You May Know’ or ‘Jobs You May Be Interested In’.”

Automation, when properly harnessed, means the difference between being able to continuously innovate and rapidly becoming irrelevant. And though large scale adoption of automation is not an endeavor to be undertaken on a whim, examples of data automation like those listed above show the outstanding benefits that come as a result of this investment that you make for your company’s future.

Popular posts from this blog

"Ni jiang yi yang de hua ma?"

Last week, I wrote about the necessity of having a clear message . Because this topic is so important I decided to follow-up with another entry on this general subject. This week we will approach it from another angle. (For the curious, the title says " Do you speak the same language? " in pinyin, which is a transliterated Mandarin Chinese.) Recently, a good friend of mine (who is Chinese, ironically) and I were playing pool. He had to bank the 8-ball in the pocket to win the game, and since it was an informal game and bank shots are my area of expertise, he asked me for advice. I told him, "you just need to strike the cue ball with medium speed so that it hits the 8-ball right in the middle." He didn't believe me so we marked the positions of the balls, and then he took his shot only to watch the 8-ball sail past the pocket. "A-ha!" he exclaimed. "I told you it wasn't that easy." But when we reset the positions and I made an attemp

It's Easier to Fail at DevOps than it is to Succeed

Slippery when wet Since the term DevOps was coined in Belgium back in 2009, it is impossible to avoid the term whether in discussions with colleagues or in professional trade magazines.  And during the years while this movement has gained momentum, many things have been written to describe what elements of a DevOps strategy are required for it to be successful. Yet in spite of this, there is an interesting data point worth noting: not many organizations feel there is a need for DevOps.  In a Gartner report entitled DevOps Adoption Survey Results (published in September 2015),  40%  of respondents said they had no plans to implement DevOps and 31% of respondents said they hadn't implemented it but planned to start in the 12 months after the survey was conducted. That left only 29% who had implemented DevOps in a pilot project or in production systems, which isn't a lot. "Maybe it's because there truly isn't a need for DevOps," you say.  While that

Is No/Low-Code the Key to IT Nirvana?

 Unless you've had your head in the sand for the past year or so, you've seen the phrases low-code  and no-code  bandied about quite frequently everywhere you look.  You've probably wondered if this is something new that's here to stay or just a "flash in the pan."  Although the terms have been in the fore of the IT trade publications recently, Low Code Development Platforms (LCDP) (and the corresponding No Code Development Platforms) have been in existence since 2011.  Their roots can be traced to the 90's with 4th generation programming languages and GUI-assisted programming paradigms, e.g. IBM VisualAge for Basic, which was discontinued in 1998. For those of you who aren't familiar with either, the premise is that these platforms allow someone to quickly build applications using a WYSIWYG interface and a "click and configure" paradigm to Isn't this the source code to Roblox? rapidly build full applications with little or no coding requ