The document discusses strategies for implementing DevOps in an API and microservices environment. It outlines some of the challenges companies face when transitioning to microservices, including lack of agility and dependencies between services. It then provides several strategies for DevOps success, such as starting with a smaller initial project to learn microservices, focusing on reducing the size and dependencies of deliverables to enable faster deployment, and considering replacing rather than upgrading services. The conclusion emphasizes learning to build and deploy small, with attention to dependencies, in order to balance speed, safety and time to market.

1. World®
’16
Strategies for DevOps in the API
and Microservices World
Jay Thorne - Consulting Software Engineer, APIM - CA Technologies
DO3X82V
DEVOPS

2. 2 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
© 2016 CA. All rights reserved. All trademarks referenced herein belong to their respective companies.
The content provided in this CA World 2016 presentation is intended for informational purposes only and does not form any type of
warranty. The information provided by a CA partner and/or CA customer has not been reviewed for accuracy by CA.
For Informational Purposes Only
Terms of this Presentation

3. 3 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Abstract
As companies invest in developer-operations-style deployment (DevOps), the interfaces and
tooling necessary to be successful in DevOps beg for simplification as a major focus of projects.
Learn how the CA API Management unit is approaching DevOps enablement and providing a safe
and scalable way to utilize APIs and microservices to help customers realize ROI on their DevOps
investments. In this session, we’ll explore how to enable DevOps in the world of microservices
using API management tooling, and discuss how many of our customers’ traditional, operations-
focused installations are evolving or could be evolved into DevOps-focused deployments.
Properly executed, the world of microservices practically defines simplicity; API management
and DevOps are a crucial part of that path to success.
Jay
Thorne
CA Technologies
Consulting Software
Engineer

4. 4 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Agenda
REALITIES OF MICROSERVICES
STRATEGIES
CONCLUSION
1
2
3

5. 5 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
The Realities
§ Corporate straitjacket
– Governance is called Change Control and mostly means
Change Prevention
– “That’s the way we’ve always done it”:
§ Can’t innovate so time to market is long
The Big Ops / Big Dev Extreme
CHANGES

6. 6 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
The Realities
§ Lunatics running the asylum
– It’s microservices all the way down
– 8 versions of same capability
– Devs write everything, so we don’t need ops
– We didn’t know but it went to production
The Lean and Mean Extreme
CONTROLS

7. 7 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Strategy: Smaller Initial Project
§ Learning the ropes of microservices /
DevOps on core business is a bad idea
§ Microservices design is different
– Intentionally reduced scope
– Lowering dependencies is difficult at first
Learn How This Stuff Works First
BET
YOUR
BUSINESS
NEW
PROJECT

8. 8 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Strategy: Focus on Size of Deliverables
§ Big dependencies = stricter sequences =
longer install/upgrade windows
§ Larger artifacts = longer
builds/installs/startup
§ Manual install = more opportunities for
fat fingering
Reduce Dependencies
HUGE

9. 9 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Strategy: Focus on Smaller Deliverables
§ Lower dependences = opportunities
for asynchronous deployment
§ Smaller artifacts = quick deploy,
quick revert
§ Automation = no missed steps,
smaller runbooks
Reduce Dependencies
SMALL IS
BEAUTIFUL

10. 10 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
NUKE
and
PAVE
Strategy: Don’t Upgrade - Replace
§ Build for “configure from scratch”
where possible
– Upgrade becomes “Run new code with
previous configuration”
– Rollback becomes trivial
§ Microservices can separate data store
from business logic – use this if you can
Upgrades Are a Lot of Work

11. 11 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Strategy: Don’t Make Reuse a Strict Design Goal
§ Similar (but not equal) might require separate tool
§ Focus on not duplicating Identical tools
§ Don’t nitpick on similarity
§ However: Subsets/supersets don’t imply separate tools
Reuse Is Another Way of Saying Dependency

12. 12 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Conclusion: Learn to Build, Deploy Small
§ Bias for size and dependency reduction
§ Learn how to work bias for size in your organization
§ Dependencies need explicit attention
§ Apply learning
Have Your Cake and Eat It Too
Slow Fast
Large Small
Safe Short Time To Market

13. 13 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Questions?

14. 14 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Thank you.
Stay connected at communities.ca.com

15. 15 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
DevOps – API Management and
Application Development
For more information on DevOps – API Management and
Application Development, please visit: http://cainc.to/DL8ozQ