Download - Strata 2015 - Architecting For The Cloud
ARCHITECTING FOR THE CLOUD
Chris Neumann
CEO and Cofounder, DataHero
Traditional Enterprise Data
@DataHero
Enterprise Data Circa 2010
@DataHero
Enterprise Data Circa 2010
@DataHero
Enterprise Data Circa 2010
@DataHero
Enterprise Data Circa 2010
@DataHero
Enterprise Data Circa 2015
@DataHero
Cloud Data is Different
TRADITIONAL ENTERPRISE DATA
Centralized, on-premises data sources
Small number of data sources used by a large number
of people
Standardized interfaces
Databases can do math
Security is secondary, because the data team sits
between the data sources and the end user
CLOUD DATA
Geographically distributed data sources
Large number of data sources each used by a small number
of people
Unique, proprietary interfaces
Cloud services can’t do math
Security models are essential, because self-service means
end users have direct access to the data sources
@DataHero
Why is self-service important?
Bring your own device data
Empower business users to work with the data that matters to
them
Free up analysts and data scientists to work on higher-value
problems
@DataHero
Value-Added Cloud Services
@DataHero
It’s Not Just Analytics
@DataHero
But Analytics Will Be a “Killer App”
#DataHero
Cloud Data in the Real World
@DataHero
How do we architect for the cloud?
@DataHero
We Know What We Don’t Want
@DataHero
Automated ETL
@DataHero
Automated ETL
@DataHero
Automated ETL
@DataHero
User-Level Security
@DataHero
The Coming Storm
Self-service analytics will empower business users, but it will also
bring to the forefront issues that have been “hidden” by data groups
- Security and access policies
- Data cleansing
- De-duplication
@DataHero
What’s Next?
Value-added cloud services will become more pervasive,
particularly as developer tools improve
BI/Analytics tools built for traditional enterprise architectures will
need to figure out how to integrate more effectively with Cloud
Data
Self-service tools will need to be actually self-service
@DataHero
