DevOps and APIs: Great Alone, Better Together
Download as PPTX, PDF0 likes939 views
The document discusses the 'Center for Enablement' (C4E) model and its role in improving IT delivery through API-led connectivity and DevOps practices. It emphasizes the importance of reusability across the enterprise to minimize the IT delivery gap and speed up innovation. Additionally, it covers the implementation of modern APIs, the integration of various technologies, and the collaborative environment needed for effective DevOps practices.
![All contents © MuleSoft Inc.
Additional Resources
Webinars
• Unsung heroes of digital transformation: An Architect’s role in the new IT operating
model, with Siemens
• DevOps and the API Lifecycle on Anypoint Platform [Part 1 and Part 2]
Whitepaper
• APIs and DevOps: Great alone, better together
Coming Soon
• Blogs, How-Tos, Additional Demos
• Static Analysis, Orchestration Templates](https://image.slidesharecdn.com/connect2017devopsapis-170421064406/85/DevOps-and-APIs-Great-Alone-Better-Together-28-320.jpg)
DevOps and APIs: Great Alone, Better Together
- 1. Great Alone, Better Together Jake Morgan – Solutions Consulting - MuleSoft DevOps and APIs
- 2. All contents © MuleSoft Inc. Agenda 2 • Digital Pressures • New Approach • Center 4 Enablement (C4E) • C4E + DevOps • DevOps
- 3. All contents © MuleSoft Inc. IoT Mobile Big Data & Analytics Growth in digital technologies widen the IT delivery gap 3 Demands on IT Time Cloud and SaaS IT delivery capacityToday Delivery gap Deliverygap
- 4. All contents © MuleSoft Inc. A common project-based approach Web app API Aggregated customer data Order status Order history On time and within budget Limited opportunity for reuse Tight coupling = brittleness Difficult to govern Meets business requirements? 10 Weeks by Central IT
- 5. All contents © MuleSoft Inc. Integration project 6 months later… Aggregated customer data Order status Order history mobile APIMobile API Aggregated customer data Order historyOrder status road to hell Web app APIWeb app API 10 Weeks by Central IT 16 weeks by Outside Resources
- 6. All contents © MuleSoft Inc. Modern API: the core enabler of a new operating model 6 • Discoverable and accessible through self-service • Productized and designed for ease of consumption • Easily managed for security, scalability, and performance
- 7. All contents © MuleSoft Inc. Modern APIs Have 7 3 Parts – Design • Well defined • Easy to Understand and Use • Consistent and well documented – Implementation • Technology stack that meets business requirements AND company skills • Security – Management • Policies – Rate, Throttling, OAuth, SAML, etc • Metrics – Who, What, Where, and How Often • Security
- 8. All contents © MuleSoft Inc. APIs Are Found To Be 8 • Everywhere – Legacy Modernization to Microservices to IoT • Reusable Artifacts – HTTP(S) + JSON, XML, Binary • Addressing IT Delivery Gap – Increases % of resources to Innovation
- 9. All contents © MuleSoft Inc. The API-led connectivity approach System APIs Process APIs Experience APIs Customers Web app APIMobile API Orders Salesforce customers SAP customers Shipment status Toll shipments UPS shipments Order status Order history 10 weeks by Central IT3 weeks by Outside Resources
- 10. All contents © MuleSoft Inc. Reusable assets and Enablement A new way of working to close the delivery gap 10 Demands on IT Time Self-service and innovation New IT operating model IT delivery capacity Today
- 11. All contents © MuleSoft Inc. C4E operating model emphasizes consumption Production Reusable assets Central IT / LoB IT Consumption Feedback and usage metrics LoB IT, developers Discoverable Self-service
- 12. Center 4 Enablement Why and What
- 13. All contents © MuleSoft Inc. Why - Center for Enablement (C4E) 13 • Drive Reusability Throughout the Enterprise – APIs via API-led connectivity – Patterns – Artifacts • Minimize the IT Delivery Gap via – People – Process – Technology
- 14. All contents © MuleSoft Inc. C4E: Enabling Standard, Reusable Integration Assets • 14 Center for enablement (C4E) • C4E measured on asset consumption and organizational capability • C4E ensures that assets are – Consumable – Consumed broadly – Fully leveraged Central IT LoBInnovation teams
- 15. Center 4 Enablement Roles and Responsibilities
- 16. All contents © MuleSoft Inc. C4E - People 16
- 17. All contents © MuleSoft Inc. Roles – Core Team 17 • API Architect • Enterprise Architect • Solution Architect • SMEs/ICs/Developers/QA/Performance • DevOps Engineer • Operations Engineer • Security Analyst • Training Coordinator Sponsor(s)/Lead
- 18. Operating Model C4E + DevOps
- 19. All contents © MuleSoft Inc. Why - Center for Enablement (C4E) 19 • Drive Reusability Throughout the Enterprise – APIs via API-led connectivity – Patterns – Artifacts • Minimize the IT Delivery Gap via – People – Process – Technology
- 20. All contents © MuleSoft Inc. Why - DevOps 20 • Faster time to market • Lower failure rate of new releases • Shortened lead time between fixes • Faster mean time to recovery
- 21. All contents © MuleSoft Inc. Bigger Picture 21 • API Architect • Enterprise Architect • Solution Architect • SME/IC • DevOps Engineer • Ops Engineer • Security Analyst Sponsor CoreTeam Center 4 Enablement Think Tanks Community 4 Enablement • Knowledge Base • Blogs, Videos • What, Why, How Think Tanks
- 22. All contents © MuleSoft Inc. Think Tanks • Meetups (meetings, forums, roundtables) within the company to focus on strategic topics relevant to a wide audience within the organization. • Opportunity for different groups within the company to talk about their experiences and get feedback from others. It’s a forum intended to be highly collaborative and open to new ideas and approaches. • MuleSoft participates, but ideally doesn’t lead. We are there to facilitate the conversation, bring MuleSoft’s PPOV to the conversation, and if needed educate about the Anypoint Platform.
- 23. All contents © MuleSoft Inc. DevOps is a practice: People. Process. Technology 23 • You need technology that: – helps remove waste and inefficiency – integrates into your existing CI setup – generates meaningful reports • Technology supports a process the automation pipeline – E.g. Jenkins, TeamCity, Bamboo, Cloudbees • Your team needs the right culture – E.g. embracing Agile, TDD, etc. – E.g. robust safety net to enable incremental release – E.g. Security + DevOps = SecDevOps Increases speed to market (& upgrades/ internal usage, etc.) Enables the production of high quality products Serves as a competitive advantage for your company Reduces cost of development
- 25. All contents © MuleSoft Inc. 25
- 26. All contents © MuleSoft Inc. Why Not Add 26 • Issue and Project Tracking – JIRA, Bugzilla, TFS, FogBugz, etc • ITSM (Incident, Problem, Change) – Remedy, ServiceNow, Zendesk, etc • Performance Testing – JMeter, Loadrunner, etc
- 27. All contents © MuleSoft Inc. DevOps and Anypoint Platform (A common scenario) JUnit / MUnit Build Automation Describe how a Mule application is assembled - Connector configs - DB configurations - Test configurations Automate that build process every time a change is made to the app Test Automation Visually compose tests while or BEFORE you code (Test Driven Development; TDD) Test with mocked data, not active connections Validate unit or application functionality Version Control Reliably download(pull), change & commit code Get instant visibility into incompatible changes Enables parallel team development Deployment Automation Describe how a Mule application is deployed - Scheduling - Environments config - Test/success criteria Automate that deployment across teams, projects and environments
- 28. All contents © MuleSoft Inc. Additional Resources Webinars • Unsung heroes of digital transformation: An Architect’s role in the new IT operating model, with Siemens • DevOps and the API Lifecycle on Anypoint Platform [Part 1 and Part 2] Whitepaper • APIs and DevOps: Great alone, better together Coming Soon • Blogs, How-Tos, Additional Demos • Static Analysis, Orchestration Templates
- 29. All contents © MuleSoft Inc. Don’t forget the survey 29 • Why take the survey? – Takes less than 2 minutes – We value your feedback and apply it when deciding next year’s content and speakers – Surveys = Prizes!! Earn 55 points for a chance to win $250 in cash prizes • See “Play To Win” in the Mobile App for details • Where’s my survey? – Log into the mobile app – Click “Surveys” on the Tool Bar – Find the relevant survey for this session slot
- 30. Thank you!