![Prehistoric Era [...-1995]
• Static content only
• Interaction without server:
Impossible
Unthinkable
• Server-side HTML adjustments
PainSoftware](https://image.slidesharecdn.com/web-javadaylviv-2015-final-150615064354-lva1-app6892/85/Web-application-I-have-always-dreamt-of-Lviv-3-320.jpg)
![Medieval Era [1995-2005]
• Static content mostly
• Interaction without server: cached resources
• Server-side HTML+CSS+JS adjustments
• Frames as asynchronous data loading
• Birth of:
Servlet API
JavaScript
DHTML concept
Flash
Browser-compatibility hell
RFC1925
PainSoftware](https://image.slidesharecdn.com/web-javadaylviv-2015-final-150615064354-lva1-app6892/85/Web-application-I-have-always-dreamt-of-Lviv-5-320.jpg)
![Renaissance Era [2005-2010]
• Static content with dynamic “whistles”
• Interaction without server: simple functions
• Server-side HTML+CSS+JS adjustments
• Rising popularity of Rich Internet Applications
• Birth of:
jQuery
DOJO
AJAX and Comet
PainSoftware](https://image.slidesharecdn.com/web-javadaylviv-2015-final-150615064354-lva1-app6892/85/Web-application-I-have-always-dreamt-of-Lviv-7-320.jpg)
![Modern Era [2010-...]
• Internet of Things
• Big Data
• Cloud Computing
• ???
PainSoftware](https://image.slidesharecdn.com/web-javadaylviv-2015-final-150615064354-lva1-app6892/85/Web-application-I-have-always-dreamt-of-Lviv-9-320.jpg)
![Testability
• Server side:
Unit
Integration
Contract
[optional] Load & Performance
• Client side:
Unit
Integration
Contract
[optional] Browser & Sanity
PainSoftware](https://image.slidesharecdn.com/web-javadaylviv-2015-final-150615064354-lva1-app6892/85/Web-application-I-have-always-dreamt-of-Lviv-31-320.jpg)
Web application I have always dreamt of (Lviv)
- 1. PainSoftware Web-application I’ve always dreamt of @JavaDay Lviv 2015
- 2. Victor Polischuk PainSoftware Programming 26 Overall 32 Java 11 Web 11 Legacy 11 Professional 13 Has something to share @alkovictor
- 3. Prehistoric Era [...-1995] • Static content only • Interaction without server: Impossible Unthinkable • Server-side HTML adjustments PainSoftware
- 4. PainSoftware
- 5. Medieval Era [1995-2005] • Static content mostly • Interaction without server: cached resources • Server-side HTML+CSS+JS adjustments • Frames as asynchronous data loading • Birth of: Servlet API JavaScript DHTML concept Flash Browser-compatibility hell RFC1925 PainSoftware
- 6. PainSoftware
- 7. Renaissance Era [2005-2010] • Static content with dynamic “whistles” • Interaction without server: simple functions • Server-side HTML+CSS+JS adjustments • Rising popularity of Rich Internet Applications • Birth of: jQuery DOJO AJAX and Comet PainSoftware
- 8. PainSoftware
- 9. Modern Era [2010-...] • Internet of Things • Big Data • Cloud Computing • ??? PainSoftware
- 11. Business Needs • Integration with anything: Mobile Mainframe Coffee machine • High availability: Hard to predict clients behavior • Data is the TOP priority: We make money out of it • Client’s satisfaction: Should be happier than those of our competitors PainSoftware
- 12. Idea • “All problems in computer science can be solved by another level of indirection” © David Wheeler • “Do One Thing and Do It Well” © Unix community PainSoftware
- 18. Business Needs • Integration with anything • High availability • Data is the TOP priority • Client’s satisfaction PainSoftware
- 19. Technical Needs • Scalability • Security • Testability • “Otherity” PainSoftware
- 20. Scalability • Server is just a bunch of endpoints • Independent client • State Client needs it Server doesn’t • SLA Way to Nine-Nines You do not want to lose clients, right? PainSoftware
- 24. Security • Do you need it on each request? • Do you know how it works? • Do you think it is secure? PainSoftware
- 30. PainSoftware
- 31. Testability • Server side: Unit Integration Contract [optional] Load & Performance • Client side: Unit Integration Contract [optional] Browser & Sanity PainSoftware
- 34. Traffic • Reduce useless to none • De-increase useful: Increase volume Decrease size PainSoftware
- 35. Optimization • Client Caching Pre-fetching Incremental updates • Server: Caching Pre-fetching Incremental updates PainSoftware
- 36. Encapsulation • Both parties can have their own secrets PainSoftware
- 37. Polygamy • Is it moral if a client has many servers and vice versa? PainSoftware
- 38. Summary • Effectiveness: you have one job • Security: you are limiting interaction to minimum • Testability: test JSF page, I dare you! • State: -less server, -ful client • Elasticity/scalability: your data volume is growing • Network optimizations: you know what you send • Local optimizations: you know what you do • Many-to-many connections • SLA PainSoftware