Click here to close now.

Welcome!

@MicroservicesE Blog Authors: Elizabeth White, Pat Romanski, Cloud Best Practices Network, Lori MacVittie, Liz McMillan

Related Topics: Agile Computing, Java IoT, @MicroservicesE Blog, Release Management , @CloudExpo Blog

Agile Computing: Article

Maximize Your Return on Data: The New Business Imperative

Part 1: Lower the cost and complexity of sustaining your business applications

Application owners / senior-level IT allocate a certain percentage of their budget to sustaining, enhancing, and transforming their applications. In most organizations, the largest percentage of the IT spend is on sustaining the applications or basically "keep the lights on" type of activities, which leaves little money to enhance them to support business agility and new business requirements, or transform them to leap frog over the competition. Organizations that implement a solid data management strategy in support of their applications can maximize the return from their application investments. They can lower the cost of sustaining their applications, thus releasing budget to do what they should be doing, which is supporting the needs of the business. Innovative CIOs are actually rethinking their application environments, from just focusing on the application - the code, middleware, infrastructure, etc., to a new focus on the underlying data that supports the application. This new focus enables them to release budget and complexity from sustaining their apps, do what they do much better when it comes to enhancing their apps, and do brand new things they couldn't do before within their applications that will give them the competitive edge they are looking for.

How to Lower the Cost and Complexity of Sustaining Your Business Applications
Of all the things that keep organizations from realizing the best possible return on their data assets, enterprise application environments reside at the very top. Face it, application environments today are large, complex and generally inflexible constructs. Most companies have dozens of different types of key applications supporting countless business processes. Not only are the data volumes huge and the different data types numerous, but the data is often duplicative and the applications redundant across various business units. Moreover, the data is frequently hard to get to, the applications difficult to integrate and the quality of the data frequently questionable. No wonder it is such a challenge to provide a single comprehensive view of the critical data that the business uses every day.

This series of articles is aimed at helping organizations maximize the value of their data and applications, by moving beyond merely sustaining applications to enhancing them to support business agility and to transforming them to drive business innovation and growth. Because many organizations spend far too much of their IT budget on sustaining applications, it is important to first discover ways to lower the costs and complexity, freeing up budget and resources for innovation.

Cutting the Costs of "Keeping on the Lights"
There is a common set of challenges that most companies face around sustaining applications. These include:

  • Application Bloat - Whether the result of mergers and acquisitions, or business units going off and buying their own applications, many companies are rife with redundant applications that soak up maintenance time and money.
  • Data Sprawl - Companies frequently experience diminished application performance as the amount of data within the application grows. This in turn makes it difficult to meet SLAs and forces the purchase of additional hardware, leading to further costs.
  • Proliferating Integration Interfaces - There is a major challenge around integrating silo'd applications, and in dealing with the number and complexity of the interfaces required, which again increases costs.
  • Security and Privacy - Finally, there are the efforts and costs involved with securing the data in non-production applications, and the specter of fines should you fail to meet regulatory requirements around information privacy.

There are a number of initiatives that companies typically pursue to try to reduce the costs and efforts of sustaining applications. These include rationalizing the application portfolio by sending duplicative or inactive applications to the "application retirement home," archiving inactive data to improve application performance, masking sensitive data to meet security and privacy requirements, and finding ways to reduce the costs and complexity around integrating applications. The hitch is that organizations are trying to do all these things on a fixed budget and with a finite set of resources. Hence these initiatives have to be pursued very intelligently, making use of the best possible technologies to yield the greatest return on effort.

Getting the Most from Application Retirement
Capable of paying major dividends, application rationalization is an initiative being pursued by a good many organizations. Consequently, according to Gartner, by 2020, half of all applications that are running in data centers as of 2010 will be retired. If true, that represents a magnificent savings.

What does it take to retire redundant or obsolete applications and still provide seamless access to the archived data? Just because the application has outlived its usefulness, that doesn't mean that the data has. And for certain kinds of data, mandates demand that it be kept for years. Hence when an application is retired, it is increasingly necessary to archive all its data across all the data's sources.

Here is what has to happen to support successful application retirement in five steps:

  1. Mine the source metadata from the legacy application - You want to archive complete business entities, not just the transactional data but also master and reference data, and metadata.
  2. Extract and move the data - You want the ability to move, extract, and archive any data, including documents, attachments, images, and audio files associated with application and database records.
  3. Compress, secure and lockdown the archived data - You need to place it in to a secure, highly compressed, immutable file for later retrieval.
  4. Define and enforce retention policies - To ensure compliance, you need to be able to assign retention policies to different classes of archived data, apply legal holds to certain data, etc.; and to reduce the costs of managing ensured compliance, you want the ability to automatically purge expired records on a scheduled basis.
  5. Provide easy search access - You need to provide easy search and discovery access to archived data from any BI/reporting tool such as such as Crystal Reports, MicroStrategy, and Business Objects, and maintain access to archived data in database instances from existing application interfaces.

Improving Application Performance Through Archiving
The same steps, and same archiving technologies, also apply to archiving inactive data from live applications in order to improve their performance and reduce their TCO. This can take several forms, including archiving inactive data to an archive database in order to benefit from faster application response times, or archiving to an Optimized File Archive to effect substantial storage and infrastructure savings.

Importantly, a truly universal data archiving solution is strongly recommended, not only to support both application retirement and archiving from live applications, but also to ensure that you are able to leverage a single solution to address the archiving needs of all enterprise applications and databases, present and future.

Sub-setting and Masking Data in Non-Production Environments
The use of real data sets in development and test environments is widespread, and is necessary for good reasons. Frequently, this data is confidential or sensitive and subject to compliance requirements and the costs of not protecting it far outweigh the costs of doing so. Nevertheless, you need to control data management costs. Hence, when it comes to managing all the data in a test environment, you want the ability to:

  • Optimize performance and control costs by data sub-setting - Instead of using full sets of production data in test, you want the ability to create a functionally intact subset of the data, keeping only the data required by your business policies while maintaining all referential integrity. By working with a smaller set of data, you can shorten development cycles and reduce storage costs and the use of system resources.
  • Support compliance through data masking - By masking production data, you obfuscate Personally Identifiable Information and other sensitive data while preserving the data's usefulness in development and test activities.

In terms of flexibly protecting data privacy and confidentiality, Dynamic Data Masking technology can take you even further by providing real-time preventive capabilities. With this technology, flexible protection rules enable different kinds of masks to be applied dynamically to different kinds of data based on user privilege levels so you are able to engage in policy-based, selective masking and blocking of production data.

Reducing the Costs of Integrating Applications
For many organizations, much of the cost of keeping the IT lights on revolves around maintaining the "integration hairball" - the intricate web of point-to-point of interfaces between applications. According to Forrester Research, 87% of respondents to a recent IT survey indicated that they rely on hand coding for integration, and 75% of those admit that writing code for each integration effort leads to increased maintenance costs.

Another cost factor is the use of disparate integration tools so that there is no standard methodology and little economy of scale, not to mention difficulty sometimes in finding people trained in the use of a particular tool.

The way to substantially reduce the costs and complexity of integrating applications is to implement - and preferably, standardize on - a unified data integration platform with universal connectivity to data sources and targets, combined with the ability to access, transform, and integrate any data type, i.e., structured, unstructured, or semi-structured. To be fully useful, the platform also needs to support the full breadth of data latency requirements found in today's enterprises - batch, real-time, and changed data capture.

Importantly, a platform approach to integration will let you leverage a codeless development environment, so that custom-coded point-to-point interfaces and their expensive maintenance requirements become a thing of the past. Instead, development teams can leverage drag-and-drop development tools coupled with extensive reuse and sharing across projects of objects such as data mappings and transformations to speed development cycles and dramatically slash overall data integration costs.

Moving Forward Towards Enhancing Applications
The actions prescribed above have been proven to radically reduce the costs of sustaining applications, so that more resources can be applied to enhancing them and to driving innovation.

More Stories By Adam Wilson

Adam Wilson is the General Manager for Informatica’s Information Lifecycle Management Business Unit. Prior to assuming this role, he was in charge of product definition and go-to-market strategy for Informatica’s award-winning enterprise data integration platform. Mr. Wilson holds an MBA from the Kellogg School of Management and an engineering degree from Northwestern University. He can be reached at [email protected] or follow him on Twitter @ a_adam_wilson

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@MicroservicesExpo Stories
DevOps tends to focus on the relationship between Dev and Ops, putting an emphasis on the ops and application infrastructure. But that’s changing with microservices architectures. In her session at DevOps Summit, Lori MacVittie, Evangelist for F5 Networks, will focus on how microservices are changing the underlying architectures needed to scale, secure and deliver applications based on highly distributed (micro) services and why that means an expansion into “the network” for DevOps.
Cloud Migration Management (CMM) refers to the best practices for planning and managing migration of IT systems from a legacy platform to a Cloud Provider through a combination professional services consulting and software tools. A Cloud migration project can be a relatively simple exercise, where applications are migrated ‘as is’, to gain benefits such as elastic capacity and utility pricing, but without making any changes to the application architecture, software development methods or busine...
Discussions about cloud computing are evolving into discussions about enterprise IT in general. As enterprises increasingly migrate toward their own unique clouds, new issues such as the use of containers and microservices emerge to keep things interesting. In this Power Panel at 16th Cloud Expo, moderated by Conference Chair Roger Strukhoff, panelists addressed the state of cloud computing today, and what enterprise IT professionals need to know about how the latest topics and trends affect t...
Data center models are changing. A variety of technical trends and business demands are forcing that change, most of them centered on the explosive growth of applications. That means, in turn, that the requirements for application delivery are changing. Certainly application delivery needs to be agile, not waterfall. It needs to deliver services in hours, not weeks or months. It needs to be more cost efficient. And more than anything else, it needs to be really, dc infra axisreally, super focus...
Sharding has become a popular means of achieving scalability in application architectures in which read/write data separation is not only possible, but desirable to achieve new heights of concurrency. The premise is that by splitting up read and write duties, it is possible to get better overall performance at the cost of a slight delay in consistency. That is, it takes a bit of time to replicate changes initiated by a "write" to the read-only master database. It's eventually consistent, and it'...
"Plutora provides release and testing environment capabilities to the enterprise," explained Dalibor Siroky, Director and Co-founder of Plutora, in this SYS-CON.tv interview at @DevOpsSummit, held June 9-11, 2015, at the Javits Center in New York City.
Many people recognize DevOps as an enormous benefit – faster application deployment, automated toolchains, support of more granular updates, better cooperation across groups. However, less appreciated is the journey enterprise IT groups need to make to achieve this outcome. The plain fact is that established IT processes reflect a very different set of goals: stability, infrequent change, hands-on administration, and alignment with ITIL. So how does an enterprise IT organization implement change...
Conferences agendas. Event navigation. Specific tasks, like buying a house or getting a car loan. If you've installed an app for any of these things you've installed what's known as a "disposable mobile app" or DMA. Apps designed for a single use-case and with the expectation they'll be "thrown away" like brochures. Deleted until needed again. These apps are necessarily small, agile and highly volatile. Sometimes existing only for a short time - say to support an event like an election, the Wor...
Containers have changed the mind of IT in DevOps. They enable developers to work with dev, test, stage and production environments identically. Containers provide the right abstraction for microservices and many cloud platforms have integrated them into deployment pipelines. DevOps and Containers together help companies to achieve their business goals faster and more effectively. In his session at DevOps Summit, Ruslan Synytsky, CEO and Co-founder of Jelastic, reviewed the current landscape of...
The cloud has transformed how we think about software quality. Instead of preventing failures, we must focus on automatic recovery from failure. In other words, resilience trumps traditional quality measures. Continuous delivery models further squeeze traditional notions of quality. Remember the venerable project management Iron Triangle? Among time, scope, and cost, you can only fix two or quality will suffer. Only in today's DevOps world, continuous testing, integration, and deployment upend...
While DevOps most critically and famously fosters collaboration, communication, and integration through cultural change, culture is more of an output than an input. In order to actively drive cultural evolution, organizations must make substantial organizational and process changes, and adopt new technologies, to encourage a DevOps culture. Moderated by Andi Mann, panelists discussed how to balance these three pillars of DevOps, where to focus attention (and resources), where organizations migh...
At DevOps Summit NY there’s been a whole lot of talk about not just DevOps, but containers, IoT, and microservices. Sessions focused not just on the cultural shift needed to grow at scale with a DevOps approach, but also made sure to include the network ”plumbing” needed to ensure success as applications decompose into the microservice architectures enabling rapid growth and support for the Internet of (Every)Things.
Mashape is bringing real-time analytics to microservices with the release of Mashape Analytics. First built internally to analyze the performance of more than 13,000 APIs served by the mashape.com marketplace, this new tool provides developers with robust visibility into their APIs and how they function within microservices. A purpose-built, open analytics platform designed specifically for APIs and microservices architectures, Mashape Analytics also lets developers and DevOps teams understand w...
Buzzword alert: Microservices and IoT at a DevOps conference? What could possibly go wrong? In this Power Panel at DevOps Summit, moderated by Jason Bloomberg, the leading expert on architecting agility for the enterprise and president of Intellyx, panelists peeled away the buzz and discuss the important architectural principles behind implementing IoT solutions for the enterprise. As remote IoT devices and sensors become increasingly intelligent, they become part of our distributed cloud envir...
Sumo Logic has announced comprehensive analytics capabilities for organizations embracing DevOps practices, microservices architectures and containers to build applications. As application architectures evolve toward microservices, containers continue to gain traction for providing the ideal environment to build, deploy and operate these applications across distributed systems. The volume and complexity of data generated by these environments make monitoring and troubleshooting an enormous chall...
Containers and Docker are all the rage these days. In fact, containers — with Docker as the leading container implementation — have changed how we deploy systems, especially those comprised of microservices. Despite all the buzz, however, Docker and other containers are still relatively new and not yet mainstream. That being said, even early Docker adopters need a good monitoring tool, so last month we added Docker monitoring to SPM. We built it on top of spm-agent – the extensible framework f...
There's a lot of things we do to improve the performance of web and mobile applications. We use caching. We use compression. We offload security (SSL and TLS) to a proxy with greater compute capacity. We apply image optimization and minification to content. We do all that because performance is king. Failure to perform can be, for many businesses, equivalent to an outage with increased abandonment rates and angry customers taking to the Internet to express their extreme displeasure.
There's a lot of things we do to improve the performance of web and mobile applications. We use caching. We use compression. We offload security (SSL and TLS) to a proxy with greater compute capacity. We apply image optimization and minification to content. We do all that because performance is king. Failure to perform can be, for many businesses, equivalent to an outage with increased abandonment rates and angry customers taking to the Internet to express their extreme displeasure.
SYS-CON Events announced today that the "Second Containers & Microservices Conference" will take place November 3-5, 2015, at the Santa Clara Convention Center, Santa Clara, CA, and the “Third Containers & Microservices Conference” will take place June 7-9, 2016, at Javits Center in New York City. Containers and microservices have become topics of intense interest throughout the cloud developer and enterprise IT communities.
The causality question behind Conway’s Law is less about how changing software organizations can lead to better software, but rather how companies can best leverage changing technology in order to transform their organizations. Hints at how to answer this question surprisingly come from the world of devops – surprising because the focus of devops is ostensibly on building and deploying better software more quickly. Be that as it may, there’s no question that technology change is a primary fac...