Often, technology choices are often guided and decided either by wide market rumor or speculation. However, in an ever expanding and intensely competitive market, little room exists for those willing to risk large and critical infrastructure components supporting current business operating models.
As technology begins to rapidly shift, there becomes a necessity to provide infrastructure technologies that have agile qualities enabling the ability to decouple services. Decoupling services are inherently vital within today’s cloud architectures and the next generation information management frameworks.
Aligning these thoughts, let’s consider the continually expanding organization. Over time, the organization changes either through, acquisitions, mergers, re-alignments, or organic growth. External factors as well as internal factors often prompt organization culture to build decisions based on certain risk models. Business cases supporting a return on investment coupled with a reduction of risk often dictate the outcome.
In order to support these changes, underlying IT information management frameworks demand decoupling to minimalize risk and provide agility to support growing organizational changes. Misconceptions behind common technology engines suggest a major revolution in the industry. However, when examining it further, without data backup, the common technology engine soon becomes an incongruent process, leaving stranded business islands.
That said, Symantec takes an information-centric and agile solution offering approach versus a rigid common technology engine. The information-centric approach provides technology that provides agility, availability (business continuity), information integrity and security for the next generation of information-centric architectures. Customized solution and Information-Centric models broadly build the foundation to establish and build consistent technology processes across organizations, thereby creating efficiencies of IT and business teams enabling economies of scale. Consistent agile rules, aligned with the business, enable information lifecycle scenarios to unfold and data to be processed in a predictable, measurable, agile and secured fashion.
Since information management infrastructures are IT ecosystems, decisions made at each layer have a ripple effect throughout the remainder of the infrastructure. So, before making a final decision to elect a common technology engine, ensure business operating models support the changes and can accommodate the induced risk. Ask the bigger question: Does it align with an information-centric model by offering an agile approach to data and information management?
In the end, this means that tactical decisions made independent of a longer term strategy exposes the company to high levels of cost and risk, allowing your business infrastructure to lose its ability to react immediately to market changes. Below are some quick questions to consider if contemplating on choosing your next vendor.
Questions to consider:
- Does a common technology engine provide the rapid ability to selectively split, merge information management domains once data is gathered to promote agility for the organization as it changes over time?
- Does the common technology engine platform provide the ability for true information management capabilities such as application high availability, storage virtualization and integration with today’s advanced cloud architectures?
- Large scale deduplication places huge demands on underlying architecture components and the deduplication management points become time consuming, burdensome and risk adverse. What are the extended costs for these management points?
- Mandated command and control server platforms negate agility by reducing options for future organization and market changes.