(ism310) scholastic's strategy to integration as a service
TRANSCRIPT
© 2015, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Jeff Gelb, Scholastic Inc.
October 2015
ISM310
Enterprise Integration
StrategyScholastic in the Cloud
What to Expect from the Session
• Introduction to Scholastic
• Enterprise Integrations?
• Four Scenarios - Examples in Use
• Implementation and Technologies
• Lessons Learned and Next Steps
• Q&A
Who is Scholastic?
Who is Scholastic?
• Our mission: To encourage the intellectual and
personal growth of all children, beginning with
literacy.
• Started in 1920 with a single magazine
• The largest publisher and distributor of children’s books
in the world
• 165 countries, 45 languages
• A leading provider of educational materials in K-8
Who is Scholastic?
- Content – text, images, video, metadata
- Commerce – B2B, B2C
- Logistics and Distribution
- Physical – supply chain, printing, pop-up stores, shipping
- Digital – Content, Applications, Marketing, Mobile Games
Scholastic’s Technology Transformation
• Scholastic in transition
• Technology is not just a supporting function
• Three year goal to reform all technology• Externalize commodity services
• More strategic, less routine operational
• Improve speed and quality of service
• Function as a coordinated system
Scholastic’s Transformation Themes
• Self-service
• Support product development lifecycle
• Encourage Reuse
• Visibility and Transparency
Scholastic’s Enterprise
Integration as a Service
http://quest.nasa.gov/smore/photos/images/docking.jpg
What was Scholastic’s Enterprise Integration?
• Route
• Transform
• Transport
• Orchestrate
Why change at all?
Everything around us is changing:
• Endpoints
• Data
• Vendors, Partners, Platforms
• Integration Patterns and Expectations
• Rate of change
What would it have looked like?
• Route
• Transform
• Transport
• Orchestrate
Why should integration be the constraint?
How it is used
• Driven by consumer
• Usable at any time by anyone
• Integrated into SDLC
processes
• Testable, reconfigurable
Self-Service Integration Platform
What it is
• Published features
• Common patterns
• Highly instrumented and monitored
• Easy and fast to scale, in multiple
dimensions
• Capacity, Throughput, Isolation
Unblock the Enterprise
API Gateway
Transform
Analytics & Metrics
It’s the same … but different
Platform Interfaces Platform Services
Examples: Four Variations
https://commons.wikimedia.org/wiki/File%3AOsteichthyes-examples.png
Examples:
Four Variations
https://commons.wikimedia.org/wiki/File:Guylaine2007_-_Bonne_journee_%28by%29.jpg
https://commons.wikimedia.org/wiki/File:Harry_and_stella.jpg
V1: Integration Platform
The core features of integration:
• Input, Output, Transform, Transport
•Unifies API, ESB, messaging
•Non-functionals for free
• Integration catalog
•Self-service
•SDLC support
V2: International ERP Transformation
International Division new ERP PoC
• Move at their own pace
• Participate in the Enterprise
• No scale-out concerns
• Freedom to innovate
V3: Fast Track Data and BI Transformation
Live migrate EDW to AWS data platforms
• Grab parallel feed from current bus
• Reuse transports, mappings
• Transform if needed
• Amazon Data Pipelines and Lambda
V4: Integration Forensics
Refactor 15 years of integrations
• Grab parallel feed from current bus
• Monitoring and Instrumentation
• ELK, SumoLogic, RedShift
• Cut-over at will
Implementation
and Technology
https://upload.wikimedia.org/wikipedia/commons/5/59/Huge_circuit.JPG
The Not As Good
• Mature commercial product
• Poor developer support
• Single Topic
• Single Topology
• Single Data Center
• Single Environment
• Single Team
Where we were
The Good
• Mature commercial product
• Business object dictionary
• Pub/Sub(ish)
How are we doing this?
• AWS IaaS + AWS platforms + 3rd Party SaaS
• Configuration Automation
• AMIs, CloudFront, Chef, (Consul)
• Open Source Integration Framework
• WSO2 API Manager and ESB
• Multiple Transports
• Kafka, RabbitMQ, Existing Bus
• APIs and Services – built and consumed
WSO2 API
Manager
Analytics
Where we are: Broad Pieces
Platform Interfaces Platform Services
Transform
WSO2 ESB
Orchestrate
Where we are: Developer Flow
WSO2 API
Manager
Analytics
Platform Interfaces Platform Services
Transform
WSO2 ESB
Orchestrate
Jenkins CI
Swagger
API
WSO2 API
Manager
Analytics
Where we are: Data/App Flow
Platform Services
WSO2 ESB Scala/Akka
Transform
Orchestrate
Transform
Orchestrate
WSO2 API
Manager
Analytics
Where we are: Operational Flow
Platform Services
Transform
WSO2 ESB
Orchestrate
Transform
Scala/Akka
Orchestrate
Platform Interfaces
Where we are: Complete Picture
Lessons Learned and Next Steps
The Not As Good
• Integration dev experience
• Platform automation
• Complexity
Where we are
The Good
• Good SDLC support
• Instrumentation
• Flexible topology
• Flexible transports
• Multiple environments
• Multiple data centers*
• Multiple instances*
Unblock the Enterprise
Lessons Learned
• Work-around vs fix vs stop
• Self-service isn’t enough• SDKs, on-boarding, demos
• Developer workflow, testing workflow
Next Steps
• Get rid of the ESB
Transform
WSO2 ESB
Orchestrate
Transform
Scala/Akka + Camel
Orchestrate
Credit and Thanks
• Scholastic Technology Services management
• Mark Bonano and the Integration Services Team
• Adam Japhet and the Cloud Transformation Engineers
Remember to complete
your evaluations!