enterprise i.t. is dead, long live enterprise i.t.!
TRANSCRIPT
@yveshwang#DevoxxPL
Platinum Sponsors:
ENTERPRISE I.T. IS DEAD,LONG LIVE ENTERPRISE I.T.!
YVES HWANG
Internet & Mobility ArchitectSTATOIL FUEL & RETAIL
By 2020 more than three-quarters of the (Standard & Poor) S&P 500 companies will be comprised of businesses that are yet known to
us.
Professor Richard Foster from Yale University http://www.bbc.com/news/business-16611040
COST REDUCTION
TIME TO MARKETVENDOR LOCK-INS
NEW SALES & OPPORTUNITIES
SUPPORT NEW CHANNELS
INNOVATION
CRAFTSMANSHIP
CONTINUITYAGILITY
I live in Oslo, Norway
I come from Perth, WA
I am passionate about devopsand automation
devops culture
automation
cloud native
enterprise transformation
POOR ENTERPRISE DINOSAURS
EVIL STARTUPS, DISRUPTORS &OPEN SOURCE
“Bank is I.T., I.T. is bank” - ING, H. Kolk (Chief Architect)
what is an enterprise i.t.
lets start with some facts
FACT #1
Lots of meetings, lots of processes, and lots of chefs, not many cooks
FACT #2
You <3 buzzwords, buzzwords ftw!
FACT #3
Your current (and very large) I.T. investment or portfolio is NOT going anywhere soon
FACT #4
You can build cloud native apps, but your enterprise I.T. is NOT cloud native
FACT #5
Your cloud native apps will be highly DEPENDENT on the old monoliths or traditional application architectures
UI Layer
Business Logic Tier
Data Access Tier
IntegrationTier
MainframeRDMS DB(s)
• Monolithic apps
• Dependent on heavy, stagnant tech
• Configuration is embedded and static
• Requires specific infrastructure and configuration
• Inability to decomposed deployability
• Lack of portability
piecemeal all the things!
enterprise transformation
Sinclair Schuller, Apprenda @ KubeCon EU, London 2016 :)
OPTION #1
:(
Decompose all existing enterprise apps into micro services
OPTION #2
:)
Leverage CI/CD tooling and platforms with hybrid architecture capabilities
OPTION #3
:)
Leverage a platform that understands the mechanics of “mixed era” apps
Let’s explore option 2 with CI/CD!
Cloud native APIs and UIs
DB RDS (Dynamo, Elasticsearch, Postgres..)
Other API endpoints
On-premise APIs
Existing enterprise apps and servicesERP, CRM etc etc
• AWS Linux instance running nginx and docker
• Deploy Docker images or Dockerfile
• Elastic load balance
• Highly available platform
• Rolling updates, 0 downtime
• Hackable platform
WHY ELASTIC BEANSTALK
• 10+ years of Google R&D tech
• Not built for single vendor, community driven
• Makes good use of legacy hardware
• Elastic, horizontally scalable within hardware limits
WHY KUBERNETES
+ lack of orchestration =
Build pipeline
• Provides a repeatable, automated and visible platform for shipping applications
• Test automation, static code analysis, bootstrapping infrastructure
• kitchen (test/dev) —> prep —> shop
• Packaging! Because packaging is very important
TESTING YOUR BUILD PIPELINE!
• Use a DSL for describing your jobs, Jenkins Job Builder for example
• Jenkins in Vagrant or Docker to help promote testability
Fledgling ChatOps-foo
Piecemeal cloud native app + build pipeline + ChatOps = win?
ALMOST!
• Fairly complex deployment between cloud native and on premise
• Monitoring and logging can be difficult to consolidate between the “multi-era”
• Potential micro service landscape
• Monolithic dependencies are killing us
• Polyglot tooling
Our Findings
NO
devops is culture
kubernetes/elastic beanstalk does not solve the fact that we have shitty applications
THANK YOU!
@yveshwang#DevoxxPL
Q&A?
http://macyves.wordpress.comhttps://github.com/yveshwang/jenkins-docker-2step