Microservices Meets Citizen Developers

Transcription

1 OpenMunich December 1, 2017 Microservices Meets Citizen Developers Karsten Gresch & Oliver Horn Senior Solution Architects, Red Hat GmbH

2 RED HAT - OPEN SOURCE NOT OPEN CORE. BUT OPEN STANDARDS. OPEN CORE OPEN SOURCE "Community Edition" Enterprise features fully open sourced like Pay for closed source proprietary features >>>ftp.redhat.com<<< Pay for support only 2 OPEN STANDARDS Helps to make proprietary software interoperable E.g. OCI, Open Document Format, LDAP, IEEE Standards, ISO

3 3

4 MARTIN FOWLER? MICROSERVICES MEET CITIZEN DEVELOPERSHIP 4

5 MICROSERVICES DEFINED... is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API. These services are built around business capabilities and independently deployable by fully automated deployment machinery. There is a bare minimum of centralized management of these services, which may be written in different programming languages and use different data storage technologies. Martin Fowler MICROSERVICES MEET CITIZEN DEVELOPERSHIP 5 5

6 MICROSERVICES CHARACTERISTICS Build an application......as a suite of single-process services that are...using lightweight communication...independently + automatically deployable......polyglot (language + storage independent). Business impact driven Minimum of centralized management. 6

7 MICROSERVICES THE GOOD... Architectural benefits (code). Stressless processes (people). Container fit: automation advantages. SPEED (business)! 7

8 MICROSERVICES THE BAD,... Dogma / CS purity Agility/operational complexity tradeoff Working monoliths/soas Microservices (==unicorn) envy Talent pool limited Data consistency complex (distributed systems) 8

9 MICROSERVICES AND THE UGLY Building large scale distributed systems is really hard Monitoring/APM tools need to catch up Service dependency Management Heterogenity (languages, frameworks, data stores) Event-based, asynchronous, reactive programming is still in it s infancy and skills are rare. Dealing with data will be the biggest challenge Consistency, Availability, Partition Tolerance? 9

10 Short History of Microservices AWS EC2 Java EE6 DropWizard Hystrix May 2011 March 2012 Continuous Agile Integration Manifesto via XP Feb DevOps NETFLIX 2009 to AWS 2010 Eureka July 2012 Ribbon Microservices March 2012 Assess Thoughtworks Radar March 2012 Spring Boot Sept 2013 Docker March 2013 Kubernetes June 2014 Microservices Defined Thoughtworks Fowler, Lewis March 2014

11 SERVICE ORCHESTRATION MISSION ACCOMPLISHED? 11

12 CITIZENS? CITIZEN VERSUS WHAT? 12

13 CITIZENS? CITIZEN VERSUS SOLDIER? 13

14 MILITARY SLANG SO MUCH TO OPEN CULTURE... Chief XYZ Officer Deadline Milestone "From the field" 14 War Room Resources (== People!)

15 CITIZENS? CITIZEN VERSUS SCIENTIST? By Park Ranger - Cascades Butterfly Project Team, CC BY 2.0, 15

16 CITIZEN DEVELOPERS OUR DEFINITION PROFILE 16 No IT focus Lacks developer skills Results normally derived from software development MAIN AREAS Application Development (Surrogates) Data Analytics/Data Science Business Processes

17 CITIZEN DEVELOPERS IFTTT? 17

18 ORCHESTRATING MICROSERVICES WHAT WAS MISSING? FUNCTIONAL ORCHESTRATION 18

19 MICROSERVICE ORCHESTRATION PARADOXON FUNCTIONAL: STATEFUL TECHNICAL: STATELESS 19

20 EVENT DRIVEN CHOREOGRAPHY (Sam Newman) 20

21 EVENT DRIVEN CHOREOGRAPHY ORCHESTRATION OBSOLETE? NO PROBLEM? Orchestration Choreography Source and : Sam Newman, Building Microservices, Sebastopol,

22 CHOREOGRAPHY CRITICISM ORCHESTRATION OBSOLETE? Service orchestration becomes event orchestration. Event handling (management) becomes central. Standards? Tooling? 22

23 COMPOSITE MICROSERVICES (AGGREGATOR/PROXY/CHAINED MICROSERVICE PATTERNS) => ORCHESTRATION 23

24 COMPOSITE MICROSERVICES APACHE CAMEL INTEGRATION SERVICES + OPEN SOURCE TOOLING: SYNDESIS 24

25 COMPOSITE MICROSERVICES CITIZEN SERVICE DEVELOPERS HAPPY CITIZEN DEVELOPERS 25

26 COMPOSITE MICROSERVICES FUNCTIONAL ORCHESTRATION MEANS MORE THAN LEGO STYLE 26 Functional tracing and monitoring (aka BAM) Granularity, state, coupling User interaction?

27 UI BASED ORCHESTRATION FANCY ORCHESTRATION Source and : Sam Newman, Building Microservices, Sebastopol,

28 API MANAGEMENT ORCHESTRATE THROUGH APIS Source and : Sam Newman, Building Microservices, Sebastopol,

29 STATEFUL FOR STATELESS: BPM BUSINESS PROCESS MANAGEMENT FOR MICROSERVICES. REALLY? 29 Standard: BPMN 2.0 Event support BPMN level 1-2 citizen developer friendly

30 BPMN + MESSAGING TO THE RESCUE MIXING IN THE EVENT DRIVEN PART Source and : 30

31 BPMS-MICROSERVICES ARCHITECTURE BASE BUILDING BLOCKS BPM LAYER CITIZEN DEVELOPER AREA SERVICES MESSAGING SUBSYSTEM SERVICE MESH CONTAINER PLATFORM 31

32 CONCLUSION With BPMN 2.0 support, stateless microservices can be functionally orchestrated. Citizen developers have open source support for creating microservices and their functional orchestration. 32

33 THANK YOU plus.google.com/+redhat facebook.com/redhatinc linkedin.com/company/red-hat twitter.com/redhatnews youtube.com/user/redhatvideos