Java Architectures A New Hope. Eberhard Wolff

Transcription

1 Java Architectures A New Hope Eberhard Wolff

2 What happens with a talk titled like this?

3 Architecture of Enterprise Java Apps

4

5

6 How can I implement a new feature???

7 !

8 ECommerce System New Stuff Spring & OSGi

9 ECommerce System New Stuff New Spring Stuff & OSGi

10 HTTP Links No legacy code Any technology Small code base " New Stuff

11 Micro Services Component Model Component Separate process Individual deployment unit GUI+Logic Small services+gui unlike SOA

12 Online Shop Order Billing Catalog Search

13 Online Shop Order Billing Catalog Spring Batch Search Spring MVC Oracle elasticsearch MongoDB

14 Service might be even smaller

15 Continuous Delivery

16 Continuous Delivery: Build Pipeline Automated Acceptance Testing Manual Explorative Testing Commit Stage Automated Capacity Testing Release

17 Without Micro Services Modify order process slightly Billing, Search & Catalog unchanged Order Billing Catalog Search

18 Order Billing Catalog Search

19 Continuous Delivery: Everything Tested etc Automated Acceptance Testing Manual Explorative Testing Commit Order Billing Stage Search Catalog Automated Capacity Testing Release

20 Build Pipeline Just one component changed! Lots of unneeded work Takes much too long

21 With Micro Services Automated Acceptance Testing Manual Explorative Testing Commit Order Stage Automated Capacity Testing Release

22 Release Just a single component Faster feedback Easier deployment Rollback of single service also easier

23 How to scale agile? Implement more feature

24 Conways Law Architecture copies communication structures of the organization

25 Online Shop Order Billing Catalog Search Component = Team

26 Micro Service Team independent from each other No code dependencies Can use individual technology stack Can even deploy independently Speed up development

27 Architecture Challenges Code Reuse? Handling interfaces? Managing dependencies between (>100) Services? Global architecture? Global refactorings?

28 Install and configure App Server for each Microservice??

29 Simple Java Application? What about Operations?

30 Spring Boot Demo

31 Why Spring Boot? Easier deployment i.e. just a JAR Built in operations support

32 Other Technologies Dropwizard by Yammer vert.x Play Framework

33 Micro Services as a Component System

34 Components Collaborate Link Micro Service REST Messaging Micro Service Data Replication

35 Micro Service can easily integrate with Legacy

36 Deploy & Operate?

37 Component Model No restriction on language etc Individual processes + infrastructure (database etc) JARs, WARs, EARs: No good fit Virtual machines as components? Overhead??

38 Docker No true virtualization Linux Containers (lxc) i.e. shared kernel i.e. separate file systems

39 Docker File Systems Read only base images +read/write image Read / Write Can be stacked Application Java Ubuntu

40 Docker Linux only So: Run it in VM Controlled by Vagrant

41 Docker Demo

42 Vagrant VM Docker Container Redis Port 6379

43 Communication Between Docker Container Via ports Via data volumes

44 Docker is a Component System

45 Example Log file analysis ELK Stack Elasticsearch: Store Logstash: Parse Kibana: Web based GUI Install three servers Automate installation...!

46 Dockerized ELK Stack 1 Vagrantfile (25 lines) 6 Dockerfiles (total 28 lines) 1 HTML file (11 lines) 1 Config (Logstash) (29 lines) Total: 93 lines, 9 files Including one RegExp!

47 Vagrant VM Container user-registration 8080 Container logstash 9200 Container elasticsearch 9200 Container kibana Volume /log link Port 8081 Port 9200 Port 8080 Browser

48 Demo ELK Stack

49 Links artikel/episode-44-modularisierte- Architektur-fuer-grosse- Systeme html

50

51 Micro Services A new hope against Java Monoliths Also great for legacy Spring Boot for implementation Docker as component model & runtime

52 Thank