Web-application I’ve always dreamt of (Kharkiv)

PainSoftware
Web-application
I’ve always dreamt of
@JavaDay Kharkiv
2015

Victor Polischuk
PainSoftware
Programming 26
Overall 32
Java 11
Web 11
Legacy 11
Professional 13
Has something to share
@alkovictor

Prehistoric Era [...-1995]
• Static content only
• Interaction without server:
Impossible
Unthinkable
• Server-side HTML adjustments
PainSoftware

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

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

Modern Era [2010-...]
• Internet of Things
• Big Data
• Cloud Computing
• ???
PainSoftware

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

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

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

Business Needs
• Integration with anything
• High availability
• Data is the TOP priority
• Client’s satisfaction
PainSoftware

Technical Needs
• Scalability
• Security
• Testability
• “Otherity”
PainSoftware

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

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

…Strong Password
PainSoftware

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

Responsibility
• Client:
Responsive
User-friendly
Pretty
• Server:
Scalable
Fail-proof
Redundant
PainSoftware

Traffic
• Reduce useless to none
• De-increase useful:
Increase volume
Decrease size
PainSoftware

Optimization
• Client
Caching
Pre-fetching
Incremental updates
• Server:
Caching
Pre-fetching
Incremental updates
PainSoftware

Encapsulation
• Both parties can have their own secrets
PainSoftware

Polygamy
• Is it moral if a client has many servers and vice versa?
PainSoftware

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

Web-application I’ve always dreamt of (Kharkiv)

More Related Content

What's hot (20)

Viewers also liked (13)

Similar to Web-application I’ve always dreamt of (Kharkiv) (20)

More from Victor_Cr (14)

Recently uploaded (20)

Web-application I’ve always dreamt of (Kharkiv)