(ISM310) Scholastic's Strategy to Integration as a Service
•
4 likes•1,615 views
As a global publishing house, Scholastic Corporation has brought to market titles such as Clifford the Big Red Dog and series like Harry Potter and The Hunger Games. Scholastic is in the midst of a multi-year technology transformation, which will move it out of the data center business and all-in on AWS. This session will discuss Scholastic’s DevOps model, which has allowed it to quickly deploy traditional software systems to AWS. It will also discuss how Scholastic addressed enterprise integration challenges by developing “Integration as a Service” and building parallel feeds into Amazon Redshift and other AWS data warehouse and analytics platforms.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to (ISM310) Scholastic's Strategy to Integration as a Service
Similar to (ISM310) Scholastic's Strategy to Integration as a Service (20)
More from Amazon Web Services
More from Amazon Web Services (20)
Recently uploaded
Recently uploaded (20)
(ISM310) Scholastic's Strategy to Integration as a Service
- 1. © 2015, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Jeff Gelb, Scholastic Inc. jgelb@scholastic.com October 2015 ISM310 Enterprise Integration Strategy Scholastic in the Cloud
- 2. 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
- 4. 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
- 5. 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
- 6. 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
- 7. Scholastic’s Transformation Themes • Self-service • Support product development lifecycle • Encourage Reuse • Visibility and Transparency
- 8. Scholastic’s Enterprise Integration as a Service http://quest.nasa.gov/smore/photos/images/docking.jpg
- 9. What was Scholastic’s Enterprise Integration? • Route • Transform • Transport • Orchestrate
- 10. Why change at all? Everything around us is changing: • Endpoints • Data • Vendors, Partners, Platforms • Integration Patterns and Expectations • Rate of change
- 11. What would it have looked like? • Route • Transform • Transport • Orchestrate
- 12. Why should integration be the constraint?
- 13. 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
- 14. API Gateway Transform Analytics & Metrics It’s the same … but different Platform Interfaces Platform Services
- 17. 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
- 18. 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
- 19. 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
- 20. V4: Integration Forensics Refactor 15 years of integrations • Grab parallel feed from current bus • Monitoring and Instrumentation • ELK, SumoLogic, RedShift • Cut-over at will
- 21. Implementation and Technology https://upload.wikimedia.org/wikipedia/commons/5/59/Huge_circuit.JPG
- 22. 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)
- 23. 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
- 24. WSO2 API Manager Analytics Where we are: Broad Pieces Platform Interfaces Platform Services Transform WSO2 ESB Orchestrate
- 25. Where we are: Developer Flow WSO2 API Manager Analytics Platform Interfaces Platform Services Transform WSO2 ESB Orchestrate Jenkins CI Swagger API
- 26. WSO2 API Manager Analytics Where we are: Data/App Flow Platform Services WSO2 ESB Scala/Akka Transform Orchestrate Transform Orchestrate
- 27. WSO2 API Manager Analytics Where we are: Operational Flow Platform Services Transform WSO2 ESB Orchestrate Transform Scala/Akka Orchestrate Platform Interfaces
- 28. Where we are: Complete Picture
- 29. Lessons Learned and Next Steps
- 30. 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
- 31. Lessons Learned • Work-around vs fix vs stop • Self-service isn’t enough • SDKs, on-boarding, demos • Developer workflow, testing workflow
- 32. Next Steps • Get rid of the ESB Transform WSO2 ESB Orchestrate Transform Scala/Akka + Camel Orchestrate
- 33. Credit and Thanks • Scholastic Technology Services management • Mark Bonano and the Integration Services Team • Adam Japhet and the Cloud Transformation Engineers
- 34. Thank you! Questions? Comments? Jeff Gelb jgelb@scholastic.com We’re Hiring!
- 35. Remember to complete your evaluations!