· PDF fileCREATE SECURITY GUARD RAILS ESTABLISH A DATA ... business models on a company’s current value proposition and resulting ... extreme pressure on margins

Architecting for the Digital EdgeIOATM Playbook

Four Foundational Steps to Build your Digital Platform © 2016 Equinix, Inc.

© 2016 Equinix, Inc. Source: www.ioakb.com

About IOATM

© 2016 Equinix, Inc.

IOA stands for Interconnection Oriented ArchitectureTM – which is a proven and repeatable architectural framework that both enterprises and service providers leverage to directly and securely connect people, locations, clouds and data. IOA is about integrating the physical and virtual worlds where they meet.

IOA is being used (by more than 8,000 companies) to accelerate digital transformation and establish the foundation for the global digital platform. The principles of IOA are:

• Shorten the Distance between your applications and data, and the people (Customers, Employees and Partners).

• Localize Traffic and Services across all the locations and markets you need to reach and regionalize services globally.

• Integrate and Deliver via Ecosystem Exchanges leveraging multiple clouds & SaaS providers to increase your rate of change while interconnecting with the swarm of digital partners.

• Locate Data and Analytics Adjacent to improve response times and distributed scale while reducing the amount of data traversing the networks.

IOA breaks the tired old assumption that you can’t do anything about the physical distance. It is critical to understand that you need to do exactly that in order to localize your capability to digitally engage users, and integrate with clouds & digital business services. IOA shifts the fundamental IT delivery architecture from siloed and centralized to interconnected and distributed.

This playbook introduces, and will guide you in how to use, the IOA Knowledge Base.

The knowledge base is a collection of detailed Blueprints and Design Patterns that provide both an overview and a guide for architects on the steps to architect for the digital edge and map their journey to becoming a digital enterprise.

Following these steps removes traditional architectural constraints, optimizing connectivity, leveraging ecosystems and placing IT back in control — in the center of an Interconnection Oriented Architecture. Learn more at http://www.IOAKB.com

What is IOA?

What is the IOA Playbook?

© 2016 Equinix, Inc. Source: www.ioakb.com © 2016 Equinix, Inc.

Setting the Stage:Digital Disruption is Here and Now

SETTING THE STAGE

RE-ARCHITECT THE EDGE

IOA™ OVERVIEW

IOA™ KNOWLEDGE BASE

MAP THE JOURNEY

SIMPLIFY THE TOPOLOGY

CREATE SECURITY GUARD RAILS

ESTABLISH A DATA FABRIC

INTEGRATE VIA INTERSECTION POINTS

DIGITAL PLATFORM ON PLATFORM EQUINIX™

Digital disruption is the combination of digital technologies and new business models on a company’s current value proposition and resulting market position.

The shift to digital is requiring firms to implement new commerce and collaboration models to engage customers, partners and employees, and support new connectivity and data models for analytics, IoT, digital payments and other digital services. “Digital is the main reason just over half of the companies on the Fortune 500 have disappeared since the year 2000.” Pierre Nanterme, CEO Accenture

Digital disruption is not industry specific. The World Economic Forum launched DTI (Digital Transformation of Industries) in 2015 to track it, and it’s unlike other economic revolutions in that it will touch almost everything. It has the potential to render 40% of today’s companies, in each industry, immaterial by 2020+. Competition can come from outside an industry and/or internationally as digital companies can easily be global companies (e.g., Uber’s global disruption of the taxi industry).

2015 Global EconomyThe 2015 economy as a share of gross domestic product

2020 Global EconomyForcast growth of the digital economy+

$85,150bn

77.5%

22.5%

$19,159bn

$65,991bn

Digital Economy:

Non-Digital:

$98,490bn

25.0%

75.0%

Digital Economy:

Non-Digital:

$24,615bn

$73,875bn

4.9B▲30%

2.1T▲76%

4.4ZB ▲40%

$176B▲16%

Connected Devices App Usage Sessions

Data Created & Stored Hybrid Cloud

Mobile Application Spend

Cloud Services Spending

~50% ENT adopting hybrid

cloud by 2017

20B▲22%

New Commerce & Collaboration Models

New Connectivity & Data Models

B2C eCommerce

$1.7T▲18%

B2B eCommerce

$1.1T▲8%

Digital Advertising

$72B

B2B Acquired Customers via Company Blog

57%

B2B Customer Support via Facebook

44%

Skype for BusinessHours

1.6B

As digital grows to 25% of the global economy, the amount of overall global growth that digital is capturing is disproportionately larger (over 40%) than non-digital, which means that digital is seizing revenue growth.

This is even more pronounced in the U.S. economy where digital already makes up 37% of the economy, but is capturing more than 65% of the overall U.S. GDP growth.

Not only is the traditional way of doing business unsustainable (in decline); 75% of the economy will be scrambling for market share and competing for a subset of the growth — placing extreme pressure on margins.

This is digital disruption*Equinix Vertical and Market Insights

* Accenture Strategy Group - https://www.accenture.com/us-en/insight-digital-disruption-growth-multiplier+ IMD Global Center for Digital Business Transformation


Setting the Stage:Forcing Business and IT to Transform

SETTING THE STAGE

RE-ARCHITECT FOR THE EDGE

IOA™ OVERVIEW


MAP THE JOURNEY






As the digital economy continues to rapidly grow, revenues shift, and the majority of economic growth moves to digital, the traditional economy struggles with revenue decline and competes for what little growth remains. As digital introduces more commoditization and new competition, traditional margins are impacted, resulting in a focus on cost reduction and efficiency to minimize that impact. Therefore, to sustainably survive digital disruption, traditional organizations are transforming both their business architecture and IT delivery architecture together — from siloed and fixed to integrated and dynamic.

• Traditional business ecosystems (Figure 1) are serialized and haven’t significantly changed even though underlying technologies have had an increasing rate of change.

• Traditional IT delivery was heavily influenced by organizational boundaries creating centralized silos of application systems and data on aging infrastructure building IT debt.

• The challenge is that all the investment in the traditional model (business and technology architecture) — which made the company successful so far — will not address the demands of digital and will likely prohibit competing in the digital economy.

• Incumbent companies have some advantages in capital, brand and existing customer base, but must disrupt themselves — let go of the predilection “but that’s the way we’ve always done things” — and re-architect, re-skill and re-tool for continuous change to compete in digital.

• Digital business ecosystems (Figure 2), in contrast, are integrating business processes with partners for compounding efficiencies and new capabilities. Standing together, not apart. Not only moving faster, but achieving greater accomplishments that dwarf past individual capabilities. Standalone companies will not be able to compete with ecosystems.

• Digital IT delivery starts with a digital platform that is both a business and technology platform. Businesses use the platform for digital engagement with customers, employees, partners and things — and for providing and subscribing to digital products and services for inter-business processing within digital ecosystems.

• Digital companies can innovate fast, fail fast and adapt to change — pushing non-differentiating items (the “busy work” that slows you down) to integrated cloud services.

Raw Materials

Suppliers

R&D

Marketing

Sales

HierarchicalModel

Warehouse/ Retailer Customers

Customers

Privacy

Mobile Sales and Payments

Omni-ChannelStorefront

Digital Services

Research and Innovation

Digital Products

Supplier Network API

From siloed and fixed... ...to integrated and dynamic

Figure 1: Traditional Value Chain

Figure 2: Digital Integration


Re-Architect for the Digital Edge

SETTING THE STAGE


IOA™ OVERVIEW


MAP THE JOURNEY






While digital engagement is about mobile, social, digital user experience, and personal efficiency or productivity, digital ecosystems are about interconnecting application services, exchanging (monetized) data, doing business over productized APIs, digital payments, smart contracts and algorithms.

What results is the formation of multi-cloud, multi-partner, interactive workloads — where latency directly impacts business capabilities and throughput diminishes business scale as volumes of data continue to increase. Applications are assembled to respond to changing business models, which requires components of those interactive workloads to be on both sides of the firewall (Figure 3). For many reasons (regulation and compliance being among them), there will always be components on both sides of the firewall for the foreseeable future.

Reducing the latency between these components is an obvious first step, since every millisecond of latency compounds the overall impact of the process. Even the simplified interactive workload in Figure 3 would result in thousands of packets transferred across dozens of permutations of the components. With automation applied, the biggest limiting factor will always be throughput (the reality of bandwidth loss due to latency).

The physics involved in the compounding effects of latency are not the only factors driving the need for intersections points at the digital edge. All of these services need to be integrated into one digital business platform. Furthermore, regulatory and compliance requirements need to be preserved consistently in the shift to digital.

BIeCommerce

CRM

Global Markets

Partner

MobileCentric

01000101 01010001 01001001 01011000

Interactive Workloads

Private Cloud

01000101 01010001

01001001 01011000

INSIDE OUTOUTSIDE IN

EGR

ESS

ING

RES

S

MULTI-CLOUD

DIGITAL ECOSYSTEMS

HQLONGHAUL

BACKHAUL

INGRESS

EGRESS

011010

NETWORKCOMMUNICATIONS

HUB

Figure 3: Interactive Workloads

Integrated digital business processes on API-centric application workloads

The Digital Edge is where population centers and digital ecosystems meet

Figure 4: Edge Node


To solve requires an interconnection-first architecture

SETTING THE STAGE


IOA™ OVERVIEW


MAP THE JOURNEY






An Interconnection Oriented Architecture™ (IOA™) takes the fundamental delivery architecture of IT and turns it upside down. In an IOA, how you securely interconnect people, devices, locations, clouds and business partners is solved first. Solving for interconnection-first provides a foundation for information exchange, integration and digital commerce enablement. Applications are then locally assembled to respond to changing business models which depends on a responsive critical infrastructure to achieve that. Interconnecting multiple clouds and data sources on both sides of the firewall (Figure 3) — where you place these functions matters the most.

The building blocks of a Digital Platform are not industry specific. Everyone must solve the same architectural challenges. In multi-party digital exchanges the most limiting and therefore differentiating capability will be interconnection. The IOA Playbook outlines the Edge Node (Figure 5) as the point where digital and physical meet and the optimal place to integrate.

Layer capabilities on top by adding functions to that node and/or by leveraging cloud ecosystems (or direct connections). As nodes are strategically placed geographically, with optimized WAN connections between them, the result is the mesh of nodes depicted above (Figure 6). As a digital platform, the firm decides what digital services to offer in which metro markets and tailors implementations with localized ecosystems (Figure 7).

This design can be achieved one location at a time, with minimal up front investment, and leverages technologies already used by enterprises and providers today.

Design the Edge Nodes based on the localized services and integration required, including industry regulatory or sovereignty requirements.

Deploy the Edge Nodes where business presence, population centers, high volumes of user traffic and points of data gravity are needed.

Tailor the Edge Nodes to localize business services to support the global digital business strategy.

Figure 5: Edge Node Figure 6: Mesh of Edge Nodes Figure 7: Tailored Localized Services Deployed Globally

INSIDE OUTOUTSIDE IN

EGR

ESS

ING

RES

S

MULTI-CLOUD

DIGITAL ECOSYSTEMS

HQLONGHAUL

BACKHAUL

INGRESS

EGRESS

011010

NETWORKCOMMUNICATIONS

HUBAPI

STORE

API

API

$

$

$

STORE

STORE


IOA™ Knowledge Base: Anatomy of a Blueprint

SETTING THE STAGE


IOA™ OVERVIEW


MAP THE JOURNEY






1

3

4

5

6

7

8

2

NETWORK SECURITY DATA APPLICATION

= 4 BLUEPRINTS

5Steps

5Steps

5Steps

5Steps

= 20DESIGN

PATTERNS

+ + +

+ + +

The IOA Knowledge Base contains integration Blueprints and Design Patterns developed from studying over 400 customer production deployments and ongoing learning from key advanced enterprises and providers.

Icon and Name (Edge Node Integration Layer)

Highlighted Design Principles

Typical Components Involved

Highlighted Steps as Design Patterns

Quick Context With Objective Depiction

Guide to Sizing

Capabilities That Are Achieved

Reference Index in the Set

1

2

3

4

5

6

7

8


IOA™ Playbook: Mapping the Journey

SETTING THE STAGE


IOA™ OVERVIEW


MAP THE JOURNEY






Start Your Journey with the Blueprints and Design Patterns in the IOA Knowledge Base

Localize & Optimize the Tra�c

Segment the Tra�c Flows

Establish Multi-cloud Connectivity

O�oad Internet Tra�c at the Edge

Connect to Digital Ecosystems

Establis

h Boundary

Contro

l

Create

an In

specti

on Zone

Apply Polic

y Enforce

ment

Co-Loca

te Identity

& Key M

anag

ement

Integrate Secu

rity A

nalytic

s & Lo

gging

SECURITYBLUEPRINT

NETWORKBLUEPRINT

Establish Distributed Data Repository

Solve Data Cache Placement

Place Edge Analytics & Streaming Flows

Data Exchanges & Data Integration

Manage Metadata & Data Pipelines

Implement A

PI Man

agement

Plumb for M

essag

ing

Apply Dist

ributed C

oordinati

on

Position C

omplex Eve

nt Pro

cess

ing

Introduce

Predict

ive A

lgorithmic

Service

s

APPLICATIONBLUEPRINT

DATA BLUEPRINT

DIGITALPLATFORM

FROM SILOEDAND FIXED

IOA LAYER PATH CHECKLIST

NETWORK

SECURITY

DATA

APPLICATIONS

Simplify the Topology

Create Security Guard Rails

Establish a Data Fabric

Integrate via Intersection Points


IOA™ Network Blueprint

To architect for the digital edge you need to bring the WAN and LAN together and create a Digital Edge Node. Each node is tailored for the network and traffic types that have to be localized, segmented and optimized — at that geographic location. Build the nodes in a step function way, and deploy them in metro-based zones where there is density in users, traffic and data. Directly connect the nodes to reduce topological distance (# of hops) and optimize bandwidth (throughput).

To simplify the topology, follow these IOA Network Blueprint steps:1. Localize and Optimize the Traffic2. Segment the Traffic Flows3. Establish Multi-Cloud Connectivity4. Offload Internet at the Edge5. Connect to Digital Ecosystems

Establishing a communications gateway in strategic population centers (or areas of density in devices for IoT) allows you to consolidate access across the field area networks (ISP, ethernet and mobile) to localize the traffic. Solving for optimal path for OUTSIDE IN...

Leverage choice in competitive connectivity between these geographic hubs, or edge nodes, to create a mesh that maximizes bandwidth and balances load in the most cost effective way (reducing long-haul and back-haul). Solving INSIDE OUT...

Direct connect to multiple clouds (enterprises average six) locally at the edge (Layer 2 or 3), providing the most efficient way to interconnect multiple clouds with shortest distance to the users. Direct connect to the internet as well to optimize access to personal or lower risk application services. Solving MULTI-CLOUD...

To support secure digital business, cross-connect to digital partners at the edge in a meet-me fashion (peering traffic). Shortening the distance between multi-organizational digital business flows. Solving for DIGITAL ECOSYSTEMS...

THE BENEFITS of aggregating connectivity at a co-location edge node, and securely cross connecting segmented flows, are dramatic both in sustainable cost reduction and performance improvement. In digital, network flows are business flows, so performance translates to revenue, and these hubs give you back control over the flows.• The practice to improve network performance has been to

reduce the distance (and number of hops) and/or reduce the payload (requiring less throughput).

• *Internet latency (in the U.S.) to the top clouds ranges between ~60ms and ~90ms.

• Over a 100Mbps cable, at 30ms, there is already an 84% drop in throughput.

• Companies implementing this mesh of edge nodes have seen up to an 85% reduction in WAN latency (MPLS) and completely bypass the internet (i.e., average latency went from 47ms down to 8ms).

For component explanations visit the IOA Knowledge [email protected]

WAN LAN

01000101 01010001 01001001 01011000

01000101 01010001 01001001 01011000Outside In

Egress

Ingress

Backhaul

Longhaul

Inside Out

Multi-cloud

Digital Ecosystems01000101 01010001

01001001 01011000

HQ

HQ

Ingr

ess

Egre

ss

Ingr

ess

Egre

ss

*Source: CEDEXIS / NETWORK WORLD


IOA™ Security Blueprint

To architect for the digital edge you need to localize security services in the Digital Edge Node and govern multi-party flows. Each node is tailored for the traffic and digital services at that geographic location, placing you back in control of your business flows. Redefine the edge by placing boundary control for the field area networks, place an inspection zone (modern DMZ) to observe activity across multiple clouds and organizations, and automate policing of the traffic within affinity groups.

To create security guard rails, follow these IOA Security Blueprint steps:

1. Establish Boundary Control2. Create an Inspection Zone3. Apply Policy Administration & Enforcement4. Locate Identity & Key Management5. Integrate Security Analytics & Logging

The digital edge needs to be prepared for multi-cloud application and data flows, servicing people, employees and partners across multiple networks. It’s no longer a gate, or a wall, it’s equivalent to airport security with bi-directional domestic and international traffic and classes of service.

Boundary control is about security checkpoints at the edge with localized firewall, SSL termination (VPN), and other protection for malware and DDOS. Likewise, contain threats at the edge, reduce the attack surface of cyber threats, and get traffic onto the dedicated private network quickly.

Next create an inspection zone. The primary purpose is to provide transparency (deep packet inspection) to enable other security services (like detecting vulnerability exploits or lawful interception for data leakage, etc.), as well as monitoring and logging (i.e., for Security Analytics).

Policy management (PEP/PDP) is applied, in line with the traffic segmentation strategy, to detect rogue traffic or unauthorized activity, or to catch mistakes made by users or developers — hence the guard rail analogy.

Place latency sensitive security services, like identity and key management that have high traffic volumes, in proximity to multiple clouds and population centers. Improving overall performance to all dependent services.

THE BENEFITS of localizing security services at the edge extend from the capabilities granted by access aggregation, cloud integration and digital business segmentation.

• Localize controls and extend your security posture to where you do business. This can expand, scale and change as fast as digital business changes.

• Gain insight into use of cloud & SaaS services consumption with the ability to apply dynamic and real-time policy controls that govern use of those services, as well as detect packet-level anomalies.

• Capitalize on the latency advantages to implement security, governance and controls that would have otherwise negatively impacted user experience or scale.

WAN LAN

01000101 01010001 01001001 01011000

01000101 01010001 01001001 01011000Outside In

Egress

Ingress

Backhaul

Longhaul

Inside Out

Multi-cloud


01001001 01011000

HQ

HQ

Ingr

ess

Egre

ss

Ingr

ess

Egre

ss



IOA™ Data Blueprint

To architect for the digital edge you need to localize some data requirements in the Digital Edge Node, balance protection with accessibility, and govern data movement and placement. Each node is tailored for the local or shared data services at that geographic location, placing you in control of your data and performance.

To establish a data fabric follow these IOA Data Blueprint steps:

1. Establish a Distributed Data Repository 2. Solve Data Cache & Edge Placement3. Place Edge Analytics & Streaming Flows4. Build for Data Exchanges & Data Integration5. Apply Data Pipelines & Maintain Provenance

The first step is to deploy a distributed data repository that is designed for scale, is ‘eventually consistent’, and is geographically dispersed by design. Configured to leverage both private and public cloud capacity as a single distributed pool, it becomes a default tier of data service available everywhere (with both file system and API interfaces).

Data that is latency sensitive should be strategically placed in proximity to the services that require it and on a faster local cache repository. Establish this cache/copy at the edge to make it securely accessible to multiple clouds and business partners, or services running locally in the node. Placement at the edge also satisfies data sovereignty or sensitivity requirements that require data containment in the node or region/location.

Data analytics services, either standalone with large data sets or real-time event-processing based, should be placed at the edge. In addition, at an intersection point, streaming data can be aggregated at the edge from multiple sources and likewise made available as flows to multiple destinations — many sources and many subscribers.

As data is monetized, secure access to data will need to be established between multiple parties in proximity to networks and partners for lower latency.

Data sources will need to be dynamically connected because in analytical processing, more data sources directly translates to more experience. Data integration is needed for batch or real-time orchestration, servicing requests, or moving and/or translating data.

Finally, since data is delivered across a set of distributed data ‘systems’, inventory and meta information needs to be centrally managed covering data-at-rest and in-motion (data pipelines). Optimize data placement while retaining federated governance.

THE BENEFITS of localizing data at the edge starts with accessibility, security and control — without compromising the value propositions of clouds and digital ecosystems. Running multi-cloud application workloads doesn’t require moving data — just access the data locally in the edge node over secure low-latency connectivity. Minimize the risks of data loss, data leakage and data theft. Optimize business value, enforce regulatory controls and remain in control of the data at all times.

WAN LAN

01000101 01010001 01001001 01011000

01000101 01010001 01001001 01011000Outside In

Egress

Ingress

Backhaul

Longhaul

Inside Out

Multi-cloud


01001001 01011000

HQ

HQ

Ingr

ess

Egre

ss

Ingr

ess

Egre

ss



IOA™ Application Blueprint

To architect for the digital edge you need to localize application services in the Digital Edge Node as a multi-cloud, multi-party business, integration point. The shift to digital is trading complicated silos for interactive systems of digital services, which transforms application development to become API-centric in building inter-networked components. Each edge node is an application communication gateway, as well as a place to co-locate application functions with latency or volume driven workloads (i.e., improving user experience etc.).

To integrate via intersection points follow these IOA Application Blueprint steps:1. Implement API Management2. Plumb for Messaging 3. Apply Distributed Coordination4. Leverage Complex Event Processing 5. Introduce Predictive Algorithmic Services

Implement API management first to get in front of the world of digital services and create APIs, manage partner APIs, choreograph traffic, productize APIs, apply usage analytics and establish controls. APIs will be the building blocks of application assembly and lifecycle management.Digital services will have a mix of synchronous and asynchronous behaviors, and integration will be needed in the form of messaging pipelines that bring contextual cohesion to the flow (across the disparate services). Also, in the mashup of clouds, networks and application architectures, failures will occur (all the time). The edge nodes will maintain the messaging (and process) state.With digital flipping the architecture and distributing components out to the edge, coordination and configuration, including distributed governance, needs to be another foundational component of the platform. Beyond analytics, which up until now is mostly focused on detecting anomalies, the platform needs to be able to infer complex events based on multiple data sources. This will become a table stakes capability for digital business.Predictive capabilities are the next logical extension— having already determined that complex events are occurring, determine the appropriate automated actions. These capabilities need to be commoditized and readily available throughout your organization.

THE BENEFITS of localizing application services at the edge, and building them into the communication fabric, are not only about digital advantage — but also about reduced risk and improved control.

• With API management, messaging and coordination implemented on top of a secure high-speed data fabric with low-latency access to clouds and digital partners, you have successfully eliminated all of the constraints to being successful in digital business.

• The mesh of edge nodes now acts as a distributed application bus and becomes your enterprise neural network — with ‘control’ back in the center of the architecture.

WAN LAN

01000101 01010001 01001001 01011000

01000101 01010001 01001001 01011000Outside In

Egress

Ingress

Backhaul

Longhaul

Inside Out

Multi-cloud


01001001 01011000

HQ

HQ

Ingr

ess

Egre

ss

Ingr

ess

Egre

ss



IOA™ Digital Platform

This IOA™ Playbook outlines foundational steps toward building your digital platform to support digital transformation.

The journey is accelerated by removing traditional architectural constraints, optimizing connectivity, leveraging ecosystems and placing IT back in control in the center of an interconnection oriented architecture.

To solve the IOA Playbook, Platform Equinix delivers;

Performance Hub™ (PH) and Cloud Exchange™ (ECX) —which together solve the Network Blueprint and simplify the topology. PH is the communications gateway (where digital and physical meet) and ECX is a software defined cloud connectivity service, with direct connects (cables) used for all other connections. Add capabilities to the PH to fulfill the Security Blueprint and add security guard rails.

Equinix Data Hub™ (DH) is tethered into the PH and accommodates IT services co-located in the edge node to solve for the Data Blueprint — building out the data fabric and the Application Blueprint — integration via intersection points.

Take those steps on Platform Equinix™

This combination of technology, interconnection, critical-mass communities, and industry expertise comes together in the form of Platform Equinix; a global “meet-me” platform for digital business that facilitates the speed, global scale, and security needed while mitigating risk.

Equinix is home to thousands of companies in dozens of industries that come to us for the power of interconnection.

• Access to 1,400+ networks and 2,600+ cloud/IT service providers (including AWS, Cisco, Google, IBM and Microsoft).

• Today we enable more than 180,000+ connections between our customers, making us the world’s leading global interconnection platform.

• Providing 145+ locations in 40 metro cities in 15 countries, all interconnected through the world’s largest Internet Exchanges — lowering the barrier to foreign markets and regional services.

Platform Equinix

Ecosystems at Equinix

5 Continents 40 Metros 145 IBX Data Centers21 Countries

1,400 networks 500 content providers 3,500 enterprises2,600 cloud/IT providers

Wi-Fi Mobile

PublicInternet

Off-Premise Private Cloud

Azure Stack

Platform EquinixECX DHPH

Virtual Direct Public

IOA™ Playbook: Mapping the JourneyNetwork Security Data Applications

IOA Knowledge Base | IOAKB.com | © 2016 Equinix Inc.

Start Your Journey with the Blueprints and Design Patterns in the IOA Knowledge Base

Localize & Optimize the Tra�c

Segment the Tra�c Flows

Establish Multi-cloud Connectivity

O�oad Internet Tra�c at the Edge

Connect to Digital Ecosystems

Establis

h Boundary

Contro

l

Create

an In

specti

on Zone

Apply Polic

y Enforce

ment

Co-Loca

te Identity

& Key M

anag

ement

Integrate Secu

rity A

nalytic

s & Lo

gging

SECURITYBLUEPRINT

NETWORKBLUEPRINT

Establish Distributed Data Repository

Solve Data Cache Placement

Place Edge Analytics & Streaming Flows

Data Exchanges & Data Integration

Manage Metadata & Data Pipelines

Implement A

PI Man

agement

Plumb for M

essag

ing

Apply Dist

ributed C

oordinati

on

Position C

omplex Eve

nt Pro

cess

ing

Introduce

Predict

ive A

lgorithmic

Service

s

APPLICATIONBLUEPRINT

DATA BLUEPRINT

DIGITALPLATFORM

FROM SILOEDAND FIXED

IOA LAYER PATH CHECKLIST

NETWORK

SECURITY

DATA

APPLICATIONS

Simplify the Topology

Create Security Guard Rails

Establish a Data Fabric

Integrate via Intersection Points

Documents

· PDF fileCREATE SECURITY GUARD RAILS ESTABLISH A DATA ... business models on a company’s current value proposition and resulting ... extreme pressure on margins