Andrey Glashenko (Haulmont) How and why to build your own framework in the case of CUBA Platform. CUBA Platform - A high level open source Java framework for enterprise applications https://www.cuba-platform.com/.

1. @CubaPlatform#CubaPlatform
The Dark arts of building your own framework
Andrey Glaschenko
Konstantin Krivopustov
@CubaPlatform
www.cuba-platform.com

2. @CubaPlatform#CubaPlatform
Konstantin Krivopustov
CTO at Haulmont
• CUBA Platform Team leader
• Coding architect
About authors
Andrey Glaschenko
BDD at Haulmont
• Java developer background,
logistics optimization algorithms
specialist

3. @CubaPlatform#CubaPlatform
About Haulmont
• Based in Samara (Russia) and
London
• Specializing in Java enterprise
software
• Products in ECM and taxi fleet
management areas
• Bespoke solutions

4. @CubaPlatform#CubaPlatform
High level full stack Java framework for enterprise applications
development
•2008 – development start
•2009 – base of all new Haulmont’s projects
•2012 – first delivered projects by other IT companies
•2014 – released in Russian as a trial
•2015 – released in English

5. @CubaPlatform#CubaPlatform
Yet another framework?
• Existing frameworks: either low level or too “heavy”
Requirements
• Full stack
• Web UI
• Feature rich
• Uniform
• Open

6. @YourTwitterHandle#DVXFR14{session hashtag} @CubaPlatform#CubaPlatform
U
I

8. @CubaPlatform#CubaPlatform
Requirements
•Web
•Fast to develop hundreds of screens with standard UI
•Same language for the whole application
•Ability to assign a whole feature to a developer
•Code transparency and easier refactoring

9. @CubaPlatform#CubaPlatform
Vaadin – a perfect match
•Pure server-side Java for application development
•Java (via GWT) for browser side components
•Rich set of components
•Server-side UI code suitable for desktop client
•Vibrant community
•Apache license

10. @CubaPlatform#CubaPlatform
Vaadin – issues
•Resolved: performance in old browsers
•Creating own components is complex
•Resolved: excessive code to create layouts
•Extending components: private fields/methods
•Server-side memory consumption

11. @YourTwitterHandle#DVXFR14{session hashtag} @CubaPlatform#CubaPlatform
O
R
M

12. @CubaPlatform#CubaPlatform

13. @CubaPlatform#CubaPlatform
Attributes
All
Job - 88
Account – 29
Individual – 24
Service – 32
Payment_type – 16
Driver - 61
Vehicle – 23
Total: 273
Required
Job - 17
Account – 1
Individual – 1
Service – 1
Payment_type – 1
Driver - 1
Vehicle – 1
Total: 23

14. @CubaPlatform#CubaPlatform
OpenJPA FetchPlan
FetchPlan allows OpenJPA to load partial entities (23..29).
Hibernate always loads all attributes (273).
Result: 10 times more data then we need!
• Extra DB server load
• Extra MW CPU load and
memory consumption

15. @CubaPlatform#CubaPlatform
OpenJPA issues
•Abandoned by IBM -> development almost stopped
•JPA 2.1 not supported (join on, stored procs, etc)
Solution: migrate to EclipseLink (Q3 2015)

16. @YourTwitterHandle#DVXFR14{session hashtag} @CubaPlatform#CubaPlatform
O
ther
technologies

17. @CubaPlatform#CubaPlatform
Container
Switched from JBoss EJB to Spring Framework.
CUBA application can be deployed to any lightweight Java web
server.
How we use Spring Framework:
• Dependency injection container for both middleware and clients
• Remoting via HTTP invoker for communication between clients and
middleware
•Low-level tasks schedulers
•RESTful web services

18. @CubaPlatform#CubaPlatform
Build System
Switched from Ant to Gradle.
Encapsulated platform build logic in plugins
More benefits:
• Very fast incremental builds
•Automatic transitive dependency management
•Storing dependencies in a hierarchy of Maven repositories
Gradle DSL complexity isolated by Studio.

19. @YourTwitterHandle#DVXFR14{session hashtag} @CubaPlatform#CubaPlatform
Extensions

20. @CubaPlatform#CubaPlatform
One size does NOT fit all
Off-the-shelf products are great until
customer wants something in his way.
Typical vendor options:
•Say NO. The luckiest get away with it!
•Branch. Easy start of the road to hell..
•Integration points: plugins

21. @CubaPlatform#CubaPlatform
Extension
A project extending the base product, which can modify base product:
•Add new entities, screens,
beans
•Override entity attributes
•Modify screens
•Modify business logic
•Modify style via SCSS

22. @CubaPlatform#CubaPlatform
All CUBA projects are extensions

23. @CubaPlatform#CubaPlatform
Adding an attribute

24. @YourTwitterHandle#DVXFR14{session hashtag} @CubaPlatform#CubaPlatform
D
eveloping
C
U
B
A
applications

25. @CubaPlatform#CubaPlatform
Tools and Languages
Tools
•IDE
•+ IDE Plugin
•+ Studio
Languages
•Java
•XML
•JPQL

26. @CubaPlatform#CubaPlatform
Shortcutting the development
cycle
See result
Make change Compile
DeployRestart
Hot deploy

27. @CubaPlatform#CubaPlatform
Typical developer workflow
Studio IDE Type
Project files and build
scripts
Auto
Data model and DB scripts Auto
Standard CRUD screens Auto
MW services and entity
listeners stubs
Auto
Middleware logic Java, JPQL
Complex screens – Studio visual designer, IDE or both XML
Screens logic Java, JPQL
Customize UI Theme SCSS

28. @CubaPlatform#CubaPlatform
Next step: PaaS
StudioStudio

29. @YourTwitterHandle#DVXFR14{session hashtag} @CubaPlatform#CubaPlatform
Sum
m
ary

30. @CubaPlatform#CubaPlatform
Our place in the ecosystem

31. @CubaPlatform#CubaPlatform
CUBA can help
..to deliver your application, if
•it has many screens and some non-trivial business logic
•it has standard UI requirements (no kittens!)
•pre-built business features do not fit
•you want to stay in control
•you have limited time and budget
•it is supposed to be used by multiple customers

32. @CubaPlatform#CubaPlatform
Interested?
Welcome to our stand S5!
•Live development process demo
•Examples of CUBA applications
<Stand photo>

33. @YourTwitterHandle#DVXFR14{session hashtag} @CubaPlatform#CubaPlatform
Q
&
A