Enterprise Data Architecture and Big Data
Enterprise Data Architecture and Big Data
Join the DZone community and get the full member experience.Join For Free
Hortonworks Sandbox for HDP and HDF is your chance to get started on learning, developing, testing and trying out new features. Each download comes preconfigured with interactive tutorials, sample data and developments from the Apache community.
By treating big data as a “one-off” project, rather than an ongoing foundation that provides the context, environment, and capabilities to enable value creation and delivery to the organization…we might be sowing the destructive seeds for another crisis.
To what extent have you embraced big data? Is it still an experiment or has it become the foundation of your IT strategy? As data capabilities evolve (structured AND unstructured; application centric AND shared platforms; big AND small data models) and the operational realities settle in, enterprise data architectures are undergoing a high stakes transformation.
Managing application, platform, services and data architecture has always been a big IT challenge. Now the spotlight has shifted to enterprise data, which is growing in importance and in a state of constant flux. As a result, business processes and platforms are becoming increasingly more difficult to change and more costly to keep up-to-date. The solution to this predicament is an Enterprise Data Architecture that can provide a framework for a flexible data asset portfolio.
History has repeatedly taught us that the bigger the IT shift, the more care is needed in planning and architecture. Managing the high stakes impact of big data requires a comprehensive set of architectural principles that ensure consistency, coherence and make applications more responsive, efficient and economical.
What is your data roadmap and maturity level?
Do you understand the overall data roadmap? Does your data architecture exhibits these characteristics:
- Fragmented, duplicated
- Poorly understood
- Not easily accessible
Data is an unlikely raw material but it’s a valuable asset. Data rationalization, standardization, and consolidation process forces organizations to understand their current data maturity level and move forward on the appropriate roadmap. As firms undertake the Big Data journey, the enterprise architecture matures through several stages.
- Maturity Level 1: Data Silos (data trapped in applications – No EA Principle)
- Maturity Level 2: Standardized Technology (Applied EA Principle: Rationalization)
- Maturity Level 3: Optimized Data Core (Applied EA Principle: Virtualization, Consolidation, and Automation)
- Maturity Level 4: Data as a Service (Applied EA Principle: Shared Services / Cloud Computing)
The first step involves helping a company develop its Data architecture vision and operating model, with attention to cost, globalization, investiture, or whatever is driving the company strategically. Once that vision is in place, enterprise data architects can guide the organization through an iterative process of rationalization, consolidation, and eventually shared-services and even cloud computing.
Data Rationalization Yields Standardization
The data rationalization exercise helps an organization identify what structures and standards to move towards as they eliminate the complexities and silos they have built up over the years, along with the specific technologies that will help them get there.
Depending on the company, data rationalization could start with a technical discussion and be IT-driven; or it could start at a business level. For example, a company might have distributed operations across the globe and desire to consolidate and standardize its business processes. That could drive change in the application portfolio. Or a company that has gone through M&A might have redundant business processes to rationalize.
Rationalizing involves understanding the current state of an organization’s data asset portfolio and business processes, and then mapping business capabilities to IT capabilities. This is done by developing scoring criteria to analyze the current portfolio, and ultimately by deciding on the standards that will propel the organization forward. A more cohesive data architecture is the outcome of a rationalization exercise.
Standardized technology represents the second level of EA maturity. Organizations at this level have evolved beyond isolated independent silos. They have well-defined corporate data governance and policies, which yields measurable cost savings and the elimination of redundant systems and skill sets.
Data Consolidation Initiatives
Consolidation entails reducing the footprint of your data asset portfolio. That could involve consolidating the number of database servers, application servers and storage devices, consolidating redundant security platforms, or adopting virtualization, grid computing and related consolidation initiatives.
Consolidation may be a by-product of another technology transformation, or it may be the driver of these transformations. But whatever motivates the change, the key is to be in alignment with the overall business strategy. Enterprise data architects understand where the business is going so they can pick the appropriate consolidation strategy.
Execution Roadmap to a Enterprise Data Strategy
Companies that don’t manage their data wisely risk becoming overwhelmed, a poor position from which to extract value. The 3 V’s – volume, velocity and variety – can become a problem in a hurry if not managed.
One of the key outcomes of a data architecture exercise is the creation of a strategic data portfolio that continually keeps IT in line with where the business is going.
Having a roadmap is especially important when you move down the path to data-as-a-service strategy. For a company that has a very complex IT infrastructure and application portfolio, having a strategic roadmap helps the organization to move forward incrementally, minimizing risk and giving the IT department every opportunity to deliver value to the business.
Key Questions to Address in a Data Architecture effort
An exploding demand for data and connectivity brings both challenges and opportunities to IT organizations of every size. Surviving requires answering basic questions like:
- What are the operational realities of big data?
- What are best practices in developing a data asset catalog?
- How big data initiatives should change how you value and price IT across the business.
- Benchmark – how are competitors overcoming the architectural challenges associated with big data?
- What are some of the common pitfalls to avoid along the big data journey?
Do you have a Data Architecture Development Process?
- Business Architecture
- Architecture Vision
- Current State
- Future State
Notes and References
- According to TOGAF… the purpose of enterprise architecture is to optimize across the enterprise the often fragmented legacy of processes (both manual and automated) into an integrated environment that is responsive to change and supportive of the delivery of the business strategy.
Published at DZone with permission of Ravi Kalakota , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.