Accenture Liquid Architectures (for Master EMSE UPM-FI - April 2017)

LIQUID
ARCHITECTURES
MASTER EMSE UPM-FI APRIL 2017
JORGE HIDALGO

WHOIAM
Jorge Hidalgo @_deors
Software Engineering Manager - Senior Technology Architect
Accenture Delivery Centre in Spain, Malaga
Global Java Professional Community Co-Lead in Accenture
Custom Distributed, Architecture & DevOps Lead in Spain DC
Father of two children, husband, whistle player, video gamer, sci-fi ‘junkie’,
Star Wars ‘addict’, Lego ‘padawan’, Raspberry Pi fan...
https://deors.wordpress.com

CHALLENGES IN
MODERN
ARCHITECTURE

WE’VE COME A LONG WAY BUT…
Resistance to change
Copyright © 2017 Accenture. All rights reserved. 5

Code change paralysis

Lack of automation

Inadequate code review

Obsolete processes – IT waste

Limited computing resources

Tightly coupled applications

Undocumented interfaces

Brittle software

Runtime difficult to observe

Unready for digital disruption

DEALINGWITHFAILURE
Family Guy clip © FOX

LIQUID
ARCHITECTURES
TO THE RESCUE!

CHALLENGES CAN BE MITIGATED BY
SYSTEMATICALLY APPLYING…
DevOps mindset

Solid configuration management practices

Zero-touch build, test & deploy

Automated & extensive code analysis

Continuous delivery & orchestration

Elastic supply of resources – Cloud

Fine grained architecture (microservices)

Resilient & self-healing service platform

Pervasive business-oriented metrics

API oriented services

Mobile-first inception & design

FEELINGANYBETTER?
Video clip © Unknown Author

IT’S ALL ABOUT DEVOPS
DevOps is about speeding up the time to market and the continuous
delivery of business value by the close collaboration of Development and
Operations groups.
DevOps empowers collaboration and empathy over
silos and barriers, and automation over manual
repetition of build, test, deploy and run tasks
throughout the software delivery life-cycle.
Development Operations
In DevOps, every single team shares a common objective, and are governed under Lean IT
principles to eliminate inefficiency (IT waste), empower agility of processes and attain
excellence through continuous improvement.
This is a product-centric vision, where the only measure of progress is software finalized
and working in production.

DEVOPS VALUE PROPOSITION
CYCLE TIME
New features in days or
hours, not months
Small production
increments to continuously
tune business services
Metric-driven feedback
loops improve productivity
RELEASE CONFIDENCE
Changes introduced in real-
time & trivial to revert
Tests executed in
representative environments
on code check-in
Elimination of regression
defects
RISK OF CHANGE
Managed roll-out of new
features via A/B testing
Business-centric metrics for
real-time service
management
Security vulnerabilities
identified at build-time

CLOUD COMPUTING
Cloud computing is a model for enabling ubiquitous,
convenient, on-demand network access to a shared
pool of configurable computing resources that can be
rapidly provisioned and released with minimal
management effort or service provider interaction.
Cloud computing definition and characteristics by NIST: USA National Institute of Standards and Technology
Software as a
Service
Applied to
Applications
e.g. email, productivity, CRM,…
SaaS
Platform as a
Service
Applied to
App. Infrastructure
e.g. app. runtimes, DB,
messaging,…
PaaS
Infrastructure as a
Service
Applied to System
Infrastructure
e.g. compute, storage,
network,…
IaaS
Essential
Characteristics
Resource
pooling
Broad network
access
Measured
service
Rapid
elasticity
On-demand
Self-service

CLOUD COMPUTING
This diagram compares a classic, on premise deployment with the service
models in cloud computing, and to which extent management is transferred
into the service provider
Provider ManagedConsumer Managed
On Premises
comparison
Infrastructure
as a Service
Platform
as a Service
Software
as a Service
Network
Storage
Servers
Virtualisation
Operating System
Database
System Software
Application Architecture
Application
Network
Storage
Servers
Virtualisation
Operating System
Database
System Software
Application
Network
Storage
Servers
Virtualisation
Operating System
Database
System Software
Application
Network
Storage
Servers
Virtualisation
Operating System
Database
System Software
Application

INFRASTRUCTURE AS CODE
Infrastructure as code is the key to optimised IT operations, maximizing
computer resources utilisation while reducing cost
• Number of server nodes is growing exponentially with each computing generation
• No longer viable to manage servers on a 1:1 basis ► Cattle vs. Pets
• Servers are transient, disposable, elastically provisioned when required, discarded when no longer needed
• All assets are centrally managed, simplifying OS patch, software distribution and audit activities
• As an added benefit, hardware and software inventories are accurate and always up-to-date

INFRASTRUCTURE AS CODE
Infrastructure as code relies on a workflow based on recipes and images,
which are ready to use and fast to instantiate
All environments are created equal, except for how much are they allowed to
scale up/out

IT’SALLABOUTCONTAINERS
Picture © Unknown Author

VIRTUAL MACHINES & CONTAINERS
Virtual machines and containers are technology options to carry on multiple,
distributed workloads in isolation, facilitating the optimised usage of compute
resources

VIRTUAL MACHINES & CONTAINERS
Another significant strength is that this approach simplifies the process of
applying updates without any application downtime (rolling updates)

MICROSERVICES
Microservices is an architectural approach that shares with DevOps the goals
of rapid development, continuous delivery and robust and resilient software
These are the basics principles underpinned by every microservice-based
architecture
They are capable of self-monitoring and self-healing
Microservices have an automated and independent lifecycle
They are loosely coupled to other microservices in the system
They may change their physical deployment location at any time
They can scale out independently to other microservices in the system
They are the ones and only owners of the data they manage (bounded contexts)

MICROSERVICES
Microservices have bounded contexts. There is absolutely no direct
interaction with the business logic or data from other microservices.
Copyright © 2017 Accenture. All rights reserved. 43* Purely mentioned as examples of possible names of microservices

MICROSERVICES
Although not strictly a requirement, a microservice-based architecture works
much better when used along with a container based platform at runtime

Monitoring environments and resources enables to objectively fine-tune the
business, configuration and scale resources dynamically in an elastic way
CONTINUOUS MONITORING
Data-centre level monitoring: systems health, workload distribution, elastic resource assignment
Ability to orchestrate actions across data-centres (e.g. increase capacity in DC A if B is down)
Resource usage at the machine-level: CPU, memory, network, storage
Alerts are automatically raised whenever specific thresholds are hit
Application logging: logs are collated, classified, indexed and made available for search
Every single log is available: across data-centres, server nodes and application services
Application instrumentation: real-time deep understanding of application internals
Access to run-time environment internals (e.g. JVM) and in-app instrumentation & events

Data is gathered in a consistent, seamless way across the whole system
Application logs and metrics are collated and available for visualisation in one
single place

Flexibility of data visualisation tools allows for optimised visualisation
depending on the nature for each source of data
Event correlation Resource usage / Throughput
Log search
Real-time in-app
instrumentation
Analytics

Real-time and historic monitoring, including root cause analysis for performance and availability issues

Extensive dashboards, focused on development, operations or business KPIs

API MANAGEMENT IN NUMBERS
90% 60% 50%
Revenue
through
API
Expand
to new
Channels
through API
Cost
Savings
through API
3/4thof traffic come from third-party apps for
$1B cost savings through standardization of API for

API BUSINESS MODELS & EXAMPLES
Free Developer Pays Developer Gets Paid Indirect

WHAT DOES API MANAGEMENT IMPLY?
A cultural and organizational
change to maximize the
expected benefits
A technology platform (API
Management) that facilitates
the change
A working philosophy
combining Agile, DevOps and
waterfall methodologies
Enable new collaboration
models with all types of
partners (companies and app
developers)
Increase customer loyalty
and satisfaction
Increase sales capacities
Increase efficiency
Channel
Methodology
Platform
Organization
CHANGES BENEFITS

API MANAGEMENT VS. B2B MODEL
B2B
Ecosystem
with API
Custom (VPN, dedicated line…)
Internet with REST
Communications
Custom according to type of
communication
Standard
Security
Different for each partner
Equal interfaces for all
Interfaces
Manual
Automatic
Technical
On-boarding
B2B
Ecosystem
with API
Custom development
Out-of-the-box
Documentation
and Examples
Limited
No limits
Number of
Partners
Custom development
Out-of-the-box
Technical
Monitoring
Not usually
Out-of-the-box
Business
Monitoring
These are key differences when adopting API management vs. the B2B model

USE CASES BY COLLABORATION MODEL
Use cases are classified depending on the collaboration model (*)
Mobile Point of sale Partners Web
Private API
(Integration)
Partners API
(collaboration)
Open API
(innovation)
Degree of
transparency
Back-ends
ESB, SOA, App. Servers, Databases
Own Apps
Communication between
Internal Business Areas
Logistics
Banks / Money Orders
Letters Sending Service /
Business Messaging
Tracking Service
Shipping Services
Photo Sending Services
Direction Validation Services
API
(*) Not exhaustive list of use cases

API MANAGEMENT COMPONENTS
Gateway
Developer
Portal
Monitoring
APIs Development
Tools
Apps
Back-ends
Develop Apps by
consuming
published APIs
Develop APIs
Deploy APIs on
Gateway
Grant access to
third-parties
Monitoring
Publish products for consumption
APIs are consumed
from the Apps
The process
continues iteratively
1
2
3
4
5
6
78
API developer
App developer
Third-party
business
Business Operations
Business
New requirements
Third -party
business
Business

Accenture Liquid Architectures (for Master EMSE UPM-FI - April 2017)

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Accenture Liquid Architectures (for Master EMSE UPM-FI - April 2017)

Similar to Accenture Liquid Architectures (for Master EMSE UPM-FI - April 2017) (20)

More from Jorge Hidalgo

More from Jorge Hidalgo (20)

Recently uploaded

Recently uploaded (20)

Accenture Liquid Architectures (for Master EMSE UPM-FI - April 2017)