Top Secret: Large-Scale SPA
Why should you use it? How to apply it in large scale?
Open source
projects on
github
Computer Scientist
Post graduated
on Software
Engineering (SOA)
More than a
decade on Java
Development
what
do you Mean
scale
about
Significant development effort
Non-trivial
of data manipulation and display
I like
apps
i prefer a
Application
what about a
SPA GIVES ME
Of both worlds
Architecture
which conceptual parts does
our solution consist of?
Design
How is our solution
structured?
Implementation
A proposal to make it
works
architecture
architecture
OK, I understood, so
top secret
The secret to building large apps
is never build large apps.
Break your applications into
small pieces.
DOM
Presenter
Model
ViewEvent Bus Template
Storage
presenter
Asset packaging
Provide all the files
necessary to make modules
work
modularity
Expose interfaces and
abstractions to another
modules
History and seo
Users are expecting to use
history button and if it is a
public solution, remember
about seo
interoperability
Think about all devices you
need to support in your
solution
? ?
Google web toolkit
Google web toolkit
All-in-one jar file
modular design
Event driven programming
Dependency injection
Browser Split code
Compiled Java to javascript
Google web toolkit
IDE and debugging
High performant
good ajax support
Junit support
Good community support
Goodbye
Google web toolkit
Java coding
Compile time
not enough good quality
widgets
extensions
Spa framework
Integrated bootstrap css,
custom widgets, powerfull
rest client and fluent api
@brazoft
The Future of GWT Report
2012
The Future of GWT Report
2013
@brazoft
nitryx.com

Top Secret: Large-Scale SPA