Matteo Vaccari - Going Frameworkless in the Backend - Codemotion Milan 2018
0 likes133 views
The document discusses the concept of a frameworkless backend approach, comparing its advantages and disadvantages related to functionality, performance, and developer experience. It highlights data on server startup times, test running durations, and source lines of code for various setups. Additionally, it provides references to external resources and emphasizes the potential risks associated with using frameworks.
Matteo Vaccari - Going Frameworkless in the Backend - Codemotion Milan 2018
- 1. THE ART OF #FRAMEWORKLESS IN THE BACKEND Matteo Vaccari @xpmatteo
- 9. Frameworks? Risk Functionality Performance Obsolescence Incompatibilities Developer Experience App startup time Test running timeThe bad The good Learning Standardisation Bad habits DB-Centric Quick project startup Extra work Upgrades Searching on Stackoverflow for answers Addiction
- 11. Creating a new game
- 12. First guess: the letter “e”
- 13. Second guess: the letter “t”
- 14. Etc, etc…
- 16. Spring/JPA (Spring MVC) Controller Embedded Tomcat Spring MVC Servlet (Spring) Application Service (JPA) Repository Emtity Manager DB Our router Embedded Jetty Our Servlet Our Application Service Our Repository JDBC DB Domain Objects Domain Objects Domain Objects Domain Objects Domain Objects Domain Objects Domain Objects Domain Objects
- 22. Spring/JPA No Spring/No JPA (Spring MVC) Controller Embedded Tomcat Spring MVC Servlet (Spring) Application Service (JPA) Repository Emtity Manager DB Our router Embedded Jetty Our Servlet Our Application Service Our Repository JDBC DB Domain Objects Domain Objects Domain Objects Domain Objects Domain Objects Domain Objects Domain Objects Domain Objects
- 25. HttpServletRequest HttpServletResponse WebRequest WebResponse GameResponse x HttpStatus GuessRequest
- 26. Main
- 28. The Router
- 29. The Router, part II
- 34. The Web Request
- 36. Spring/JPA Spring/— —/— Server startup time ~6s ~3s 0.4s Time to run all tests 10s 5.5s 3.5s Time to run slowest test 7s 4-5s 1s # of tests 25 24 48 SLOC prod 360 424 643 SLOC test 358 357 745 jar size 30MB 17MB 6.3MB
- 37. Frameworks? Risk Functionality Performance Obsolescence Incompatibilities Developer Experience App startup time Test running timeThe bad The good Learning Standardisation Bad habits DB-Centric Quick project startup Extra work Upgrades Searching on Stackoverflow for answers Addiction
- 39. twitter.com/xpmatteo thoughtworks.com THANK YOU WE ARE HIRING! YES, IN ITALY!
- 40. How do we save a “guess”?
- 41. The Web Response