The document discusses the evolution of web applications from static content in the prehistoric era to modern dynamic applications. It proposes an architecture where the client focuses on the user interface and holds all state, while the server is stateless and provides scalable endpoints. This approach aims to achieve scalability, security, testability, and optimization through principles like encapsulation, limiting interaction to essential data, caching, and incremental updates.

1. PainSoftware
Web-application
I’ve always dreamt of
@JavaDay Kharkiv
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

10. Overview
PainSoftware
http://zeroturnaround.com/rebellabs/top-4-java-web-frameworks-revealed-real-life-usage-data-of-spring-mvc-vaadin-gwt-and-jsf/

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

13. Idea
PainSoftware

14. Client
PainSoftware

15. Client
PainSoftware

16. Server
PainSoftware

17. Server
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

21. …We Design
PainSoftware

22. …We Imagine
PainSoftware

23. …We Build
PainSoftware

24. Security
• Do you need it on each request?
• Do you know how it works?
• Do you think it is secure?
PainSoftware

25. …Of Course
PainSoftware

26. …Safe JSF
PainSoftware

27. …Safe Cookies
PainSoftware

28. …Strong Password
PainSoftware

29. …$5000 bug
PainSoftware

30. PainSoftware

31. Testability
• Server side:
Unit
Integration
Contract
[optional] Load & Performance
• Client side:
Unit
Integration
Contract
[optional] Browser & Sanity
PainSoftware

32. …Client
PainSoftware

33. Responsibility
• Client:
Responsive
User-friendly
Pretty
• Server:
Scalable
Fail-proof
Redundant
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

39. Questions
PainSoftware