Community getriebene Enterprise Cloud Native Architektur bei BMW Robert Lang & Marco Kühling, BMW & Mario-Leander Reimer, QAware

Der Einsatz von Cloud-nativen Technologien und die Evolution von Systemen hin zu Microservices ist aus Sicht der Enterprise Architektur herausfordernd. Wie können Entwickler fit für die Cloud gemacht und „enabled“ werden? Welche Technologien beinhaltet ein einfaches Service Skeleton für „wirklich“ produktive Feature Teams? Diese und andere Fragen wurden früher aus dem Elfenbeinturm heraus beantwortet. Dieser traditionelle Ansatz lässt jedoch kaum Raum für Innovation und Flexibilität. In diesem Vortrag berichten Marco, Robert und Leander wie die Herausforderungen der Cloud-nativen Revolution bei der BMW Group von der Community beantwortet und gemeinsam gemeistert werden.

Transcript

1. COMMUNITY DRIVEN ENTERPRISE CLOUD NATIVE ARCHITECTURE 08.10.2019 M.-L. Reimer, R. Lang, M. Kühling
2. Page 2 BMW COMMUNITY DRIVEN ENTERPRISE CLOUD NATIVE ARCHITECTURE Robert Lang BMW IT Enterprise Architect Marco Kuehling BMW IT Enterprise Architect Mario-Leander Reimer QAware Principal Software Architect Our BMW Challenge. Communities. Enterprise Architecture activities as of today. BizDevOps Team Experience.
3. Page 3 BMW I. OUR BMW CHALLENGE ➢ Enterprise Architects manage Business Capabilities ➢ A Committee of Managers make decisions ➢ Strict Blueprint defines small technical solution space (Master Solutions) Traditional Enterprise Architecture limited in space for innovation and flexibility
4. Page 4 BMW I. 100% AGILE TRANSFORMATION Classical project mindset New product mindset Meaning • „Say, what do we have to build & deliver !“ • „We want to solve problems of our customers.“ Employee • Business Analysts upfront • Outsourcing • empowered Product Managers • Customer-centric developer work Team • Functional working groups (Developer, Designer) • One person assigned to different projects • Cross functional teams • One person in one product Learning • Mistakes are very bad • Fail fast … and learn!
5. Page 5 BMW II. COMMUNITIES CHANGE VALUES AND PROCESSES ➢ MAC Development machines with admin permissions ➢ Organize Community of Practice and Coding Dojos ➢ To be on a first-name basis ➢ Share Source Code between teams ▪ Culture ▪ Tools ▪ Knowledge ➢ Use freedom for more creativity ➢ Speed up development by using new technologies ➢ Experienced lead teams inspire other teams
6. Page 6 BMW II. TECH RADAR FOR EXTENDED SOLUTION SPACE ADOPT, TRIAL, ASSESS, HOLD
7. Page 7 BMW II. COMMUNITY ORGANIZE CODING DOJOS TO LEARN Our Vision To spread the knowledge, the joy and the passion about real good programming. Coming from martial arts, a Dojo is a training space where participants meet in a secure and safe place to practice their skills by repeatedly sharpening their moves using Katas. Coders meet, they are in the Dojo to learn from each other while trying to solve a given Kata of the day.
8. Page 8 BMW
9. Page 9 BMW III. ENTERPRISE ARCHITECTS SCOUT, NETWORK & DIVE DEEP ▪ scope & dive deep ▪ inform & consult ▪ network & multiply ▪ scout ➢Link People - share & distribute Knowledge ➢Propagate Technical Excellence ➢Support in-depth at key Topics (e.g. Security) ➢Code shippable Components (e.g. Build Pipeline) ➢Architecture Support at Customer needs ➢Help to solve responsibility conflicts between Products ➢Scout for IT Technology Trends ➢Find and enable Pilot Candidates
10. Page 10 BMW III. ENTERPRISE ARCHITECTS PROPAGATE BACK2CODE INTO COMMUNITIES Java Starter Package Developer Workplace (Windows) Tech Wiki Recruiting Profiles Software Engineering Qualification Map Learning Online Back2Code Campus focus on developing Product Increments instead of “Project Management”!
11. Page 11 BMW
12. Page 12 BMW III. ENTERPRISE ARCHITECTS: ENABLE COMMUNITIES TO SHARE KNOWLEDGE Communities of Practice IT Architecture & Technical Excellence ▪ Surveys What expertise do I want to strengthen (in my product team) ? ▪ Monthly Focus Workshops Prepare and participate in-depth. ▪ Hands-On Workouts − Community to contribute − experience Tools & Methods − post Topics to tackle or exchange on
13. Page 13 BMW IV. BIZDEVOPS TEAM EXPERIENCE - ISPI ARCHITECTURE COMMUNITY Authentication & Authorization Cloud Architecture API Management Guidelines & Standards UX / UI Test- Automatisierung Microservice Skeleton Build Managment
14. Page 14 BMW IV. ENABLING FEATURES TEAMS WITH SERVICE SKELETONS ▪ Mission & Challenges − How do we get the feature teams up and running quickly? − How do we ensure a consistent tech stack without restricting autonomy too much? − What is the minimal set of functionality a service skeleton must provide? ▪ Current Status − Service skeleton exists and has been tested ▪ Future Work − Provide guidance and examples for additional functionality to teams − Provide a web-based project generator or CLI
15. Page 15 BMW IV. HOLISTIC SECURITY RIGHT FROM THE START ▪ Mission & Challenges − How do we handle multiple incompatible and often proprietary SSO contexts? − How to we enable every service in the call chain to authorize a request? − Which attributes must be present in the product wide security token? ▪ Current Status − Working security layer for one use case ▪ Future Work − Extract and extend the current solution as product wide security layer − Integrate with API management solution
16. Page 16 BMW IV. IMPROVING AND EXTENDING THE ISPI BUILD MANAGEMENT ▪ Mission & Challenges − Should we migrate to the centrally managed build infrastructure? − Which parts of the ISPI build infrastructure need to be modernized? ▪ Future Work − What are the required elements for a secure software delivery chain? ▪ Current Status − Microservices can be built and deployed in all stages (DEV, QA, PROD) automatically − Template for default build pipeline is part of the service skeleton
17. Page 17 BMW SUMMARY
18. Page 18 BMW THANK YOU THANK YOU.