Follow along the devops journey of Foundational Services as they move from monolith to micro services and from hoster to cloud.

1. ATLANTIC DEVOPS JOURNEY

2. WHAT WILL WE TALK ABOUT
• WHAT ARE FOUNDATIONAL SERVICES
• THE START
• THE PLAN
• THE JOURNEY
• WHERE ARE WE NOW
• WHERE ARE WE HEADED
WHAT WE WILL NOT TALK ABOUT: STAKEHOLDER TRANSPARENCY, DATA DRIVEN,
API EVOLUTION, LOWERING TICKET COUNT, LESS EXTERNALLY DRIVEN,
BACKLOG AND SCRUM, FUNCTIONALLY WE DELIVERED, ETC

3. WHAT ARE FOUNDATIONAL SERVICES
• WHAT DO WE OFFER
• SINGLE SIGN ON
• USER MANAGEMENT
• LICENSES
• ORDER MANAGEMENT
• PARTNER SERVICES
• … AND OTHER THINGS
• MOSTLY APIS AND VERY LITTLE UI
• >2 MILLION REQUESTS PER DAY

4. WHAT ARE FOUNDATIONAL SERVICES
• THE STACK – BIG MONOLITH
• J2EE
• SOLR
• ACTIVEMQ
• OPENAM
• POSTGRESQL
• WE ADDED MORE LATER…

5. INFRASTRUCTURE

6. THE START
• INNOVATION SPEED CHALLENGES
• HIGH RISK AND COST OF CHANGE
• HIGH COST OF MAINTENANCE
• USERS UNHAPPY
• SPLIT TEAM (3 PROJECTS)
• DOCKER/PIPELINES POC

7. THE PLAN
• TURN FS INTO A PRODUCT
• API/SERVICES AS PRODUCT
• OWN TEAM AND BUDGET
• INITIAL ROADMAP OF FY17
• LOWERING COST OF CHANGE – INBUILT QUALITY/CI-CD/CLOUD
• SOLVING LONG LASTING PAIN POINTS
• NEW TAKE ON LICENSE MANAGEMENT
• TEAM
• DEDICATED
• DEVOPS
• INNERSOURCE

8. THE PLAN - OUR OUTCOMES FOR 17
• DELIVER FASTER THAN “TODAY”
• DEPLOY MORE OFTEN:
• DURATION OF THE DEPLOYMENT - ~30 MINUTES
• (MANUAL) EFFORT IN DEPLOYMENT – CLOSE TO 0
• DEPLOYMENT ON LIVE AFTER EVERY SPRINT
• NO EXTERNAL PARTY NEEDS TO BE INVOLVED IN THE VALIDATION AND NEEDS TO GIVE THE GREEN LIGHT
• “GO FROM RELEASING IN 10 DAYS (WITH EXTERNAL VALIDATION) TO STEALTH RELEASES IN MINUTES.”
• MEASURE SUCCESS OF THE INNER SOURCE FRAMEWORK BY SEEING HOW MANY EXTERNAL CONTRIBUTORS THERE ARE AT THE END OF THE YEAR.
• KPI - NUMBER OF SUBMISSIONS 15
• LOWER IMPACT OF CHANGES: THE OUTCOME IS THAT FS IS READY FOR BIGGER AND UNEXPECTED CHANGES. IT PROVIDES SOLUTIONS IN “GOOD” TIME AND IS
NOT THE CRITICAL PATH SYSTEM FOR OTHER PROJECTS ANYMORE.
• LESS TIME SPENT ON SOLVING TICKETS MANUALLY.
• IMPROVE THE PERCEPTION OF CUSTOMERS FOR FS
• MEASURE BY SURVEY (QUESTIONS LIKE: IS IT BETTER THAN 1 YEAR AGO). A REALISTIC GOAL IS TO SEE A SMALL IMPROVEMENT NOT TO DECREASE
• ENABLE SELF-SERVICE BY DEVELOPERS INTEGRATING WITH FOUNDATIONAL SERVICES
• DEVELOPERS CAN FIND AND USE THE SUPPORTED APIS WITH SUFFICIENT DOCUMENTATION WITHOUT THE NEED TO INTERACT WITH THE FS TEAM FOR LOGIN/SSO AND
ANY NEW SERVICES DEVELOPED
• CREATE A STRONG TEAM THAT CAN DELIVER ON THE ROADMAP
• VELOCITY: GET TO A STABLE VELOCITY OF THE TEAM
• DELIVER A NEW SERVICE THAT IMPACTS MORE THAN 1 CUSTOMER – EX: LICENSE MANAGEMENT

9. THE JOURNEY – BY OCTOBER
• GLASSFISH TO WILDFLY
• POC TO INTEGRATION (EXCEPT OPENAM)
• HOMEBREW CONTAINER MANAGEMENT
• HA / 0 DOWNTIME DEPLOYS
• NEW TESTING HARNESS
• UNIT TESTING
• API TESTING
• END2END TESTING – INNERSOURCE
• REPORTING AND PIPELINES
• SOME MICROAPPS
• RESTARTED SCRUM
• GO-LIVE WITH DOCKER AND CD

10. THE JOURNEY – CHALLENGES/WHAT WE
LEARNED
• BIG TEAM STORMING PHASE
• PUTTING TEAMS BACK TOGETHER IS HARD
• INTERNAL FRICTION ABOUT DEVOPS
• NEW TECH OLD MINDSET DON’T WORK
• DON’T FORGET ABOUT CUSTOMER REQUESTS
• DON’T DO MULTIPLE THINGS AT THE SAME TIME!
• NEED A WIN - GO-LIVE

11. THE JOURNEY – CHALLENGES/WHAT WE
LEARNED
• SMALL GHOST RELEASES BEFORE THE BIG ANNOUNCEMENT
• NON VISIBLE WORK
• DITCHED STAGING ENVIRONMENT
• CANARY RELEASES
• HOSTERS ARE HARD TO WORK WITH
• WE WERE LUCKY

12. THIS MILESTONE WAS ALL
ABOUT DEMONSTRATING
THAT WE CAN DO IT, TO
OTHERS AND TO US!

13. THE JOURNEY – BY MAY
• END2END LIVE TESTS
• LICENSE MANAGEMENT
• OPENAM IN DOCKER
• DOCKERIZE
• DEPLOY ON INTEGRATION
• HA / 0 DOWNTIME DEPLOYS
• NEW ARCHITECTURE AND VERSION
• DEV AND INTEGRATION ENVIRONMENT IN AZURE GERMANY
• RUNNING FULLY DOCKERIZED IN PRODUCTION

14. THE JOURNEY – OPENAM

15. THE JOURNEY – CHALLENGES/WHAT WE
LEARNED
• DON’T DO MULTIPLE THINGS AT THE SAME TIME!
• EXTERNAL FRICTION
• HAUFE PROCESSES
• STAKEHOLDERS
• TEAM CULTURE PAYOFF
• WEKA IS NOT HAUFE
• CD INVESTMENT PAYED OFF
• WE HAVE A ~6H FROM ISSUE TO DEPLOY

16. THE JOURNEY – CHALLENGES/WHAT WE
LEARNED
• MIGRATION TO CLOUD IN SMALLER STEPS (WE LEARNED!)
• MIGRATING DEV WAS EASY (SMALL ISOLATED ENV)
• INTEGRATION IS DIFFERENT – KEEP I MIND
• LOAD BALANCERS ARE TRICKY (HOSTER AND AZURE)
• AZURE GERMANY IS NOT AZURE
• VPN CHALLENGES
• IP VS FQDN VS EVERYTHING DYNAMIC
• LOOK OUT FOR THE 0.5% CASE YOU NEVER KNOW
• DORMANT IMPORTANT USECASES/USERS

17. IT’S BEEN A LONG JOURNEY
AND WE’RE GLAD WE’RE
HERE!

18. WHERE ARE WE NOW

19. WHERE ARE WE NOW

20. WHERE ARE WE NOW
• V1 CD INFRA - STATIC
• GETTING READY TO GO LIVE WITH CLOUD
• SECURITY, TRB
• LESSONS LEARNED FROM INTEGRATION
• NEW LICENSE MANAGEMENT ON INTEGRATION
• V2 FOR TEST FRAMEWORK
• GO-LIVE PROCESS WITH WEKA
• GREAT TEAM

21. WE’VE GROWN UP!
https://martinfowler.com/bliki/MicroservicePrerequisites.ht

22. WHERE ARE WE HEADED
• SPLITTING IT UP INTO MICROSERVICES
• V2 FOR PIPELINES AND INFRASTRUCTURE (K8S VS SWARM VS EVERYTHING ELSE)
• MOVE EVERYTHING TO THE CLOUD
• GO LIVE WITH LICENSE MANAGEMENT/NOTIFICATIONS
• SUNDOWN-HANDOVER SERVICES
• DEVELOP NEW SERVICES (1 ALREADY IN PIPELINE)
• CULTURE – TRANSITION TO FULL STACK
• WE START WITH TESTERS TO DEV/OPS