Architecture 201x @ W-JAX

Lessons learned from modern web-based systems for Enterprise IT

Transcript

1. #Architecture201x Stefan Tilkov | innoQ stefan.tilkov@innoq.com @stilkov
2. Let’s start with the enterprise
3. The J2EE(TM) 1.4 Tutorial, http://docs.oracle.com/cd/E17802_01/j2ee/j2ee/1.4/docs/tutorial-update2/doc/Overview7.html
4. GỬI PHẢN HỒI, http://ejbvn.wordpress.com
5. DB Application Browser
6. DB Backend Frontend Browser
7. Assumptions to be challenged One single system One single environment Predictable load Clear & distinct roles Planned releases Built because they have to be
8. Somewhat Limited Agility
9. Increased Desaster Potential
10. Cut Things into Pieces 3 2 1
11. Small, lightweight, focused apps
12. My favorite programmer’s story
13. Task: Read a file of text, determine the n most frequently used words, and print out a sorted list of those words along with their frequencies.
14. Donald Knuth Doug McIlroy Dr. Drang, http://www.leancrew.com/all-this/2011/12/more-shell-less-egg/ 10-page literal Pascal program, including innovative new data structure tr  -­‐cs  A-­‐Za-­‐z  '\n'  |   tr  A-­‐Z  a-­‐z  |   sort  |   uniq  -­‐c  |   sort  -­‐rn  |   sed  ${1}q  
15. Small, lightweight, focused apps
16. Persistence Logic UI Module A Module B Module C
17. System A Persistence Logic UI System B Persistence Logic UI System C Persistence Logic UI
18. Assumptions to be challenged Large systems with a single environment Separation internal/external Predictable non-functional requirements Clear & distinct roles Planned releases Built because they have to be
19. http://12factor.net
20. Separate, runnable process Accessible via standard ports & protocols Shared-nothing model Horizontal scaling Fast startup & recovery App characteristics
22. Microservice Characteristics small each running in its own process lightweight communicating mechanisms (often HTTP) built around business capabilities independently deployable mininum of centralized management may be written in different programming languages may use different data storage technologies http://martinfowler.com/articles/microservices.html
23. System Characteristics Separate (redundant) persistence Internal, separate logic Domain models & implementation strategies Separate UI Separate development & evolution Limited interaction with other systems Autonomous deployment and operations
24. In search for a name … Not-so-micro-service Autonomous system Full-stack service Self-sufficient component Small system Sovereign system Independent system Cohesive system Large enough system Small enough system Logical node Domain unit Bounded system Executable component System Self-contained system
25. Self-Contained System (SCS)
26. SCS Characteristics Autonomous web application Owned by one team No sync remote calls Service API optional Includes data and logic No shared UI No or pull-based code sharing only
27. SCS App Microservice Size (kLoC) 1-50 0.5-10 0.1-? State Self-contained External Self-contained # per Logical System 5-25 >50 >100 Communication between units No (if possible) ? Yes UI Included Included External (?) UI Integration Yes (web-based) ? ?
28. Simple process run model
29. Back to building servers
30. Closer to the metal
31. Isolation and independence
32. Polyglotism
33. Built for replacement,
    not for re-use
34. FAQ Press Release Customer Experience User Manual Werner Vogels, http://www.allthingsdistributed.com/2006/11/working_backwards.html
35. Dismantled monolith Backend & front-end services (Re-Implementation in Node.js) https://engineering.groupon.com/2013/misc/i-tier-dismantling-the-monoliths/
36. DB Service Frontend Browser Service Service
37. DB Service Frontend Browser Service Service DB DB
38. DB Service FE Browser Service Service DB DB FE FE
39. Organization ⟷ Architecture
40. Kraus, Steinacker, Wegner: Teile und Herrsche – Kleine Systeme für große Architekturen, http://bit.ly/152cXbx Independent “Verticals” REST-based macro architecture Individual micro architecture
41. App DB Browser App App DB DB
42. Services as DNA “Dogfooding” Two-pizza rule Steve Yegge, https://plus.google.com/110981030061712822816/posts/AaygmbzVeRq
43. Tools Play Node.js Modern Java EE containers Akka Embedded Jetty vert.x DropWizard Netty
44. Example Micro Architecture Stacks Typesafe (Play, Akka), Java 7 Typesafe (Play, Akka), Scala JRuby/Rails, Ruby/Sinatra, Passenger Play 2, Java 8, Spring 4, Spring Data, QueryDSL, Hystrix, Logback Java 7, JAX-RS/Jersey, Jackson, Tomcat Java 8, Jetty, Jersey 2.x, HalBuilder, Archaius, Ribbon, Eureka, Google OAuth2 Client Library
46. Integrate pieces to form a whole 3 2 1
47. Robust systems
    Unreliable networks
48. S1 S2 S3
49. Tools Hystrix Akka Finagle
50. Smart aggregation
51. REST APIs Client-specific orchestration Streaming architecture
52. Browser DB Service Frontend Service Service DB DB Mobile App
53. Browser DB Service Frontend Service Service DB DB Mobile App Orch 1 Orch 2
54. S1 S2 S3 S4 S5 S6
55. Tools ql.io Storm Rx Play spray
56. Web-native front-end integration
57. Service Interface Service Interface Client Logic
58. Service Interface Service Interface Client Logic
59. Service Interface Service Interface Client Logic
60. Service Interface Service Interface Presentation Logic Orchestration Logic
61. Business Logic Business Logic Presentation Logic
62. Business Logic Business Logic Presentation Logic Presentation Logic
63. Simple semantic HTML Open Data Single domain – no portal “Google as the homepage” Polyglot environment https://gds.blog.gov.uk/govuk-launch-colophon/
64. Tools & Approaches RESTful HTTP ROCA MVC Web Frameworks
65. Change & run efficiently 3 2 1
66. Horizontal scaling
67. Virtualized operating system as container
68. Fully automated, repeatable deployment
69. Transparent monitoring
    
70. Small changesets Everyone deploys Fast deploys Change flags Graphs/metrics Fix fast/roll forward Ross Snyder, http://www.slideshare.net/beamrider9/continuous-deployment-at-etsy-a-tale-of-two-approaches
71. Fully cloud-based Self-made PaaS Simian Army Adrian Cockcroft, http://www.infoq.com/presentations/Netflix-Architecture
72. Netflix Stack Zuul Edge Router Eureka Service Registry Hystrix Stability patterns Ribbon HTTP client on steroids Karyon Application blueprint Archaius Configuration Asgard Console Servo Annotation-based metrics … … Many, many more at http://netflix.github.io
73. Simian Army Chaos Monkey Security Monkey Latency Monkey Conformity Monkey Doctor Monkey Janitor Monkey 10-18 Monkey Chaos Gorilla
74. Tools Puppet Metrics docker Vagrant Chef logstash Zipkin Packer
76. Summary
77. Build smaller
78. Aggregate smartly
79. Merge run & change
80. Thank you! Questions?
    Comments? Stefan Tilkov, @stilkov stefan.tilkov@innoq.com http://www.innoq.com/blog/st/ Phone: +49 170 471 2625 innoQ Deutschland GmbH Krischerstr. 100 40789 Monheim am Rhein Germany Phone: +49 2173 3366-0 innoQ Schweiz GmbH Gewerbestr. 11 CH-6330 Cham Switzerland Phone: +41 41 743 0116 www.innoq.com Ohlauer Straße 43 10999 Berlin Germany Phone: +49 2173 3366-0 Robert-Bosch-Straße 7 64293 Darmstadt Germany Phone: +49 2173 3366-0 Radlkoferstraße 2 D-81373 München Germany Telefon +49 (0) 89 741185-270
81. Backup
82. Browser HTML Page Backend 1 UI 1 UI 2 Server-side integration Backend 2 Frontend
 Server Examples: ESI-Caches SSI Portal Server
83. Browser HTML Page Backend 1 UI 1 UI 2 Client-side integration Backend 2 Examples: AJAX Proprietary Frameworks
84. Browser HTML Page 1 Links Backend 1 Backend 2 Asset Server HTML Page 2 CSS <<creates>> <<creates>>