2012-06-06-Platform--Webinale.pdf

Thoughts on the difference between a web application that's created quickly and a sustainable platform that you can base a business on.

Transcript

1. @stilkov #webinale Stefan Tilkov | innoQ From ad hoc Solutions to Sustainable Platforms Monday, June 11, 12
2. @stilkov #webinale innoQ Deutschland GmbH http://www.innoq.com 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 Monday, June 11, 12
3. @stilkov #webinale innoQ Deutschland GmbH http://www.innoq.com 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 (… and yes, we’re hiring) Monday, June 11, 12
4. @stilkov #webinale innoQ Deutschland GmbH http://www.innoq.com 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 (… and yes, we’re hiring) (… speci cally in Berlin) Monday, June 11, 12
5. @stilkov #webinale Initial goals Simplicity Speed Easy development Maximum productivity Monday, June 11, 12
6. @stilkov #webinale Long-term goals Stability Scalability Maintainability Decoupling Monday, June 11, 12
7. @stilkov #webinale 10 Recommendations Monday, June 11, 12
8. @stilkov #webinale Systematic breakdown Monday, June 11, 12
9. @stilkov #webinale Monday, June 11, 12
10. @stilkov #webinale Monday, June 11, 12
11. @stilkov #webinale Persistence Monday, June 11, 12
12. @stilkov #webinale Logic Persistence Monday, June 11, 12
13. @stilkov #webinale UI Logic Persistence Monday, June 11, 12
14. @stilkov #webinale Monday, June 11, 12
15. @stilkov #webinale Product Admin OrderMgmt Catalog Inventory Mgmt Comms Gateway Billing Monday, June 11, 12
16. @stilkov #webinale Modules Components Subsystems Libraries Classes Monday, June 11, 12
17. @stilkov #webinale Modules Components Subsystems Libraries Classes Something vague and inexplicable Monday, June 11, 12
18. @stilkov #webinale A system and its parts Monday, June 11, 12
19. @stilkov #webinale How do we come up with system boundaries? Monday, June 11, 12
20. @stilkov #webinale 1 project ≡ 1 system? Monday, June 11, 12
21. @stilkov #webinale 1 site ≡ 1 system? Monday, June 11, 12
22. @stilkov #webinale Modularization & Size (Ruby/Rails) * LOC = Lines of Code Monday, June 11, 12
23. @stilkov #webinale Modularization & Size (Ruby/Rails) Size Modularization 1-50 LOC* single le 50-500 LOC few les, few functions 500-1000 LOC Library, class hierarchy 1000-2000 LOC Framework + application >2000 LOC multiple applications * LOC = Lines of Code Monday, June 11, 12
24. @stilkov #webinale Modularization & Size (Ruby/Rails) Size Modularization 1-50 LOC* single le 50-500 LOC few les, few functions 500-1000 LOC Library, class hierarchy 1000-2000 LOC Framework + application >2000 LOC multiple applications * LOC = Lines of Code Monday, June 11, 12
25. @stilkov #webinale Modularization & Size (Ruby/Rails) Size Modularization 1-50 LOC* single le 50-500 LOC few les, few functions 500-1000 LOC Library, class hierarchy 1000-2000 LOC Framework + application >2000 LOC multiple applications * LOC = Lines of Code Monday, June 11, 12
26. @stilkov #webinale Modularization & Size (Ruby/Rails) Size Modularization 1-50 LOC* single le 50-500 LOC few les, few functions 500-1000 LOC Library, class hierarchy 1000-2000 LOC Framework + application >2000 LOC multiple applications * LOC = Lines of Code Monday, June 11, 12
27. @stilkov #webinale Modularization & Size (Ruby/Rails) Size Modularization 1-50 LOC* single le 50-500 LOC few les, few functions 500-1000 LOC Library, class hierarchy 1000-2000 LOC Framework + application >2000 LOC multiple applications * LOC = Lines of Code Monday, June 11, 12
28. @stilkov #webinale Modularization & Size (Ruby/Rails) Size Modularization 1-50 LOC* single le 50-500 LOC few les, few functions 500-1000 LOC Library, class hierarchy 1000-2000 LOC Framework + application >2000 LOC multiple applications * LOC = Lines of Code Monday, June 11, 12
29. @stilkov #webinale System characteristics Monday, June 11, 12
30. @stilkov #webinale System characteristics Separate (redundant) persistence Monday, June 11, 12
31. @stilkov #webinale System characteristics Separate (redundant) persistence Internal, separate logic Monday, June 11, 12
32. @stilkov #webinale System characteristics Separate (redundant) persistence Internal, separate logic Domain models & implementation strategies Monday, June 11, 12
33. @stilkov #webinale System characteristics Separate (redundant) persistence Internal, separate logic Domain models & implementation strategies Separate UI Monday, June 11, 12
34. @stilkov #webinale System characteristics Separate (redundant) persistence Internal, separate logic Domain models & implementation strategies Separate UI Separate development & evolution Monday, June 11, 12
35. @stilkov #webinale System characteristics Separate (redundant) persistence Internal, separate logic Domain models & implementation strategies Separate UI Separate development & evolution Autonomous operations Monday, June 11, 12
36. @stilkov #webinale System characteristics Separate (redundant) persistence Internal, separate logic Domain models & implementation strategies Separate UI Separate development & evolution Autonomous operations Limited interaction with other systems Monday, June 11, 12
37. @stilkov #webinale Build the right number of systems. Recommendation #1: Monday, June 11, 12
38. @stilkov #webinale Separate rules, common assets Monday, June 11, 12
39. @stilkov #webinale Monday, June 11, 12
40. @stilkov #webinale Macro (technical) architecture Domain architecture Monday, June 11, 12
41. @stilkov #webinale JRuby PHP Scala Java Clojure Monday, June 11, 12
42. @stilkov #webinale RDBMS NoSQL K/V RDBMS RDBMS/ DWH NoSQL DocDB Monday, June 11, 12
43. @stilkov #webinale RDBMS NoSQL K/V RDBMS RDBMS/ DWH NoSQL DocDB Micro architecture Monday, June 11, 12
44. @stilkov #webinale Rules & Guidelines Monday, June 11, 12
45. @stilkov #webinale Rules & Guidelines Cross-system System-internal Responsibilities Programming languages UI integration Development tools Communication protocols Frameworks Data formats Process/Workflow control Redundant data Persistence BI interfaces Design patterns Logging, Monitoring Coding guidelines Monday, June 11, 12
46. @stilkov #webinale Rules & Guidelines Cross-system System-internal Responsibilities Programming languages UI integration Development tools Communication protocols Frameworks Data formats Process/Workflow control Redundant data Persistence BI interfaces Design patterns Logging, Monitoring Coding guidelines Monday, June 11, 12
47. @stilkov #webinale Rules & Guidelines Cross-system System-internal Responsibilities Programming languages UI integration Development tools Communication protocols Frameworks Data formats Process/Workflow control Redundant data Persistence BI interfaces Design patterns Logging, Monitoring Coding guidelines (Deployment, Operations) Monday, June 11, 12
48. @stilkov #webinale t System-internal Rules 1.0 1.1 2.0 2.1 Monday, June 11, 12
49. @stilkov #webinale t System-internal Rules 1.0 1.1 2.0 2.1 Cross-system Rules 1.0 1.1 1.2 Monday, June 11, 12
50. @stilkov #webinale t Domain Architecture 1.0 1.1 System-internal Rules 1.0 1.1 2.0 2.1 Cross-system Rules 1.0 1.1 1.2 Monday, June 11, 12
51. @stilkov #webinale Common Assets Monday, June 11, 12
52. @stilkov #webinale Browser HTML Page 1 Links Backend 1 Backend 2 Asset Server HTML Page 2 CSS <<creates>> <<creates>> Monday, June 11, 12
53. @stilkov #webinale Asset Example Monday, June 11, 12
54. @stilkov #webinale Avoid both chaos and standardization paralyzation. Recommendation #2: Monday, June 11, 12
55. @stilkov #webinale Services & APIs Monday, June 11, 12
56. @stilkov #webinale The Bezos Mandate* *Steve Yegge, https://plus.google.com/112678702228711889851/posts/eVeouesvaVX Monday, June 11, 12
57. @stilkov #webinale 1. All teams will expose data and functionality through service interfaces. The Bezos Mandate* *Steve Yegge, https://plus.google.com/112678702228711889851/posts/eVeouesvaVX Monday, June 11, 12
58. @stilkov #webinale 1. All teams will expose data and functionality through service interfaces. 2. Teams must communicate with each other through these interfaces. The Bezos Mandate* *Steve Yegge, https://plus.google.com/112678702228711889851/posts/eVeouesvaVX Monday, June 11, 12
59. @stilkov #webinale 1. All teams will expose data and functionality through service interfaces. 2. Teams must communicate with each other through these interfaces. 3. No other form of interprocess communication allowed, only service calls over the net. The Bezos Mandate* *Steve Yegge, https://plus.google.com/112678702228711889851/posts/eVeouesvaVX Monday, June 11, 12
60. @stilkov #webinale 1. All teams will expose data and functionality through service interfaces. 2. Teams must communicate with each other through these interfaces. 3. No other form of interprocess communication allowed, only service calls over the net. 4. The protocols used are unimportant. The Bezos Mandate* *Steve Yegge, https://plus.google.com/112678702228711889851/posts/eVeouesvaVX Monday, June 11, 12
61. @stilkov #webinale 1. All teams will expose data and functionality through service interfaces. 2. Teams must communicate with each other through these interfaces. 3. No other form of interprocess communication allowed, only service calls over the net. 4. The protocols used are unimportant. 5. All service interfaces to be designed from the ground up to be externalizable. No exceptions. The Bezos Mandate* *Steve Yegge, https://plus.google.com/112678702228711889851/posts/eVeouesvaVX Monday, June 11, 12
62. @stilkov #webinale 1. All teams will expose data and functionality through service interfaces. 2. Teams must communicate with each other through these interfaces. 3. No other form of interprocess communication allowed, only service calls over the net. 4. The protocols used are unimportant. 5. All service interfaces to be designed from the ground up to be externalizable. No exceptions. 6. Anyone who doesn't do this will be red. The Bezos Mandate* *Steve Yegge, https://plus.google.com/112678702228711889851/posts/eVeouesvaVX Monday, June 11, 12
63. @stilkov #webinale 1. All teams will expose data and functionality through service interfaces. 2. Teams must communicate with each other through these interfaces. 3. No other form of interprocess communication allowed, only service calls over the net. 4. The protocols used are unimportant. 5. All service interfaces to be designed from the ground up to be externalizable. No exceptions. 6. Anyone who doesn't do this will be red. 7. Thank you; have a nice day! The Bezos Mandate* *Steve Yegge, https://plus.google.com/112678702228711889851/posts/eVeouesvaVX Monday, June 11, 12
64. @stilkov #webinale Service with RESTful API Well-designed Web app Monday, June 11, 12
65. @stilkov #webinale Service with RESTful API Well-designed Web app Monday, June 11, 12
66. @stilkov #webinale Eat your own API dog food. Recommendation #3: Monday, June 11, 12
67. @stilkov #webinale Identity Users Products Monday, June 11, 12
68. @stilkov #webinale Identity Users Products Monday, June 11, 12
69. @stilkov #webinale Single sign-on Backend 1 Backend 2 Auth-Provider Browser Monday, June 11, 12
70. @stilkov #webinale Single sign-on Backend 1 Backend 2 Auth-Provider Browser Login Credentials Monday, June 11, 12
71. @stilkov #webinale Single sign-on Backend 1 Backend 2 Auth-Provider Browser Login Credentials Ticket Monday, June 11, 12
72. @stilkov #webinale Single sign-on Backend 1 Backend 2 Auth-Provider Browser Login Credentials Ticket Request + Ticket Monday, June 11, 12
73. @stilkov #webinale Single sign-on Backend 1 Backend 2 Auth-Provider Browser Login Credentials Ticket Validation Request + Ticket Monday, June 11, 12
74. @stilkov #webinale Single sign-on Backend 1 Backend 2 Auth-Provider Browser Login Credentials Ticket Validation Request + Ticket Request + Ticket Monday, June 11, 12
75. @stilkov #webinale Single sign-on Backend 1 Backend 2 Auth-Provider Browser Login Credentials Ticket Validation Request + Ticket Request + Ticket Algorithmic Validation Monday, June 11, 12
76. @stilkov #webinale Separate user identity, sign-up and self-care from product dependencies. Recommendation #4: Monday, June 11, 12
77. @stilkov #webinale Understand your requests Monday, June 11, 12
78. @stilkov #webinale Monday, June 11, 12
79. @stilkov #webinale Monday, June 11, 12
80. @stilkov #webinale Pick the low-hanging fruit of front-end performance optimizations. Recommendation #5: Monday, June 11, 12
81. @stilkov #webinale Separate Command & Query Paths Monday, June 11, 12
82. CQRS (Command Query Responsibility Segregation) Logic Data Write UI Read UI Monday, June 11, 12
83. CQRS (Command Query Responsibility Segregation) Write UI Logic Data Read UI Data Event Handling Monday, June 11, 12
84. @stilkov #webinale Don’t bother readers with write complexity. Recommendation #6: Monday, June 11, 12
85. @stilkov #webinale Learn how to build Web UIs Monday, June 11, 12
86. @stilkov #webinale From server to client Server Client Silverlight Monday, June 11, 12
87. @stilkov #webinale From server to client Server Client Single Page Apps Silverlight Monday, June 11, 12
88. @stilkov #webinale From server to client Server Client Single Page Apps Flash Silverlight Monday, June 11, 12
89. @stilkov #webinale From server to client Server Client Single Page Apps Flash Silverlight Applets Monday, June 11, 12
90. @stilkov #webinale From server to client Server Client Single Page Apps Flash Silverlight Applets … Monday, June 11, 12
91. @stilkov #webinale From server to client Server Client Server-side Components Single Page Apps Flash Silverlight Applets … Monday, June 11, 12
92. @stilkov #webinale From server to client Server Client Server-side Components Single Page Apps Flash Silverlight Applets … JSF Monday, June 11, 12
93. @stilkov #webinale From server to client Server Client Server-side Components Single Page Apps Flash Silverlight Applets … JSF APS.NET Monday, June 11, 12
94. @stilkov #webinale From server to client Server Client Server-side Components Single Page Apps Flash Silverlight Applets … JSF APS.NET Vaadin Monday, June 11, 12
95. @stilkov #webinale From server to client Server Client Server-side Components Single Page Apps Flash Silverlight Applets … JSF APS.NET Vaadin … Monday, June 11, 12
96. @stilkov #webinale From server to client Server Client Server-side Components ROCA Single Page Apps Flash Silverlight Applets … JSF APS.NET Vaadin … Monday, June 11, 12
97. @stilkov #webinale ROCA http://roca-style.org/ ‣ REST principles Do this: Monday, June 11, 12
98. @stilkov #webinale ROCA http://roca-style.org/ ‣ REST principles ‣ Server-side application logic Do this: Monday, June 11, 12
99. @stilkov #webinale ROCA http://roca-style.org/ ‣ REST principles ‣ Server-side application logic ‣ Server-side, structured HTML generation Do this: Monday, June 11, 12
100. @stilkov #webinale ROCA http://roca-style.org/ ‣ REST principles ‣ Server-side application logic ‣ Server-side, structured HTML generation ‣ Unobtrusive JavaScript Do this: Monday, June 11, 12
101. @stilkov #webinale ROCA http://roca-style.org/ ‣ REST principles ‣ Server-side application logic ‣ Server-side, structured HTML generation ‣ Unobtrusive JavaScript ‣ Progressive enhancement Do this: Monday, June 11, 12
102. @stilkov #webinale ‣ Broken accessibility ROCA http://roca-style.org/ Avoid this: Monday, June 11, 12
103. @stilkov #webinale ‣ Broken accessibility ‣ Broken back/forward/refresh ROCA http://roca-style.org/ Avoid this: Monday, June 11, 12
104. @stilkov #webinale ‣ Broken accessibility ‣ Broken back/forward/refresh ‣ No bookmarks/links ROCA http://roca-style.org/ Avoid this: Monday, June 11, 12
105. @stilkov #webinale ‣ Broken accessibility ‣ Broken back/forward/refresh ‣ No bookmarks/links ‣ JS “engines” in client ROCA http://roca-style.org/ Avoid this: Monday, June 11, 12
106. @stilkov #webinale ‣ Broken accessibility ‣ Broken back/forward/refresh ‣ No bookmarks/links ‣ JS “engines” in client ‣ Hashbangs et al. ROCA http://roca-style.org/ Avoid this: Monday, June 11, 12
107. @stilkov #webinale Follow “pure” Web principles to get performance, scale and longevity. Recommendation #7: Monday, June 11, 12
108. @stilkov #webinale Automate. Seriously. Monday, June 11, 12
109. @stilkov #webinale Testing Monday, June 11, 12
110. @stilkov #webinale Delivery Monday, June 11, 12
111. @stilkov #webinale Operations Monday, June 11, 12
112. @stilkov #webinale Back-o ce tasks Monday, June 11, 12
113. @stilkov #webinale Automate everything or you will be hurt. Recommendation #8: Monday, June 11, 12
114. @stilkov #webinale Design for scale with care Monday, June 11, 12
115. @stilkov #webinale NoSQL Monday, June 11, 12
116. @stilkov #webinale Servers and Caches Monday, June 11, 12
117. @stilkov #webinale Cloud Platforms Monday, June 11, 12
118. @stilkov #webinale Transient Sharded Unshared Monday, June 11, 12
119. @stilkov #webinale Transient Sharded Unshared Horizontally Scalable Monday, June 11, 12
120. @stilkov #webinale Ye Good Ol’ SQL RDBMS Monday, June 11, 12
121. @stilkov #webinale You can use new-fangled stu , but you might not have to. Recommendation #9: Monday, June 11, 12
122. @stilkov #webinale Agility Monday, June 11, 12
123. @stilkov #webinale Monday, June 11, 12
124. @stilkov #webinale Monday, June 11, 12
125. @stilkov #webinale Monday, June 11, 12
126. @stilkov #webinale Don’t become too rigid – retain the right to be chaotic. Recommendation #10: Monday, June 11, 12
127. @stilkov #webinale Thank you! Q&A innoQ Deutschland GmbH http://www.innoq.com Krischerstr. 100 40789 Monheim am Rhein Germany Phone: +49 2173 3366-0 innoQ Schweiz GmbH info@innoq.com Gewerbestr. 11 CH-6330 Cham Switzerland Phone: +41 41 743 0116 Monday, June 11, 12