4 ms·

Could someone please explain me where the benefit is over using some embedded tomcat/jetty, weld, jersey, hibernate/jdbc? Setting up such a project cost me 30 m

by gd78 11y ago

Could someone please explain me where the benefit is over using some embedded tomcat/jetty, weld, jersey, hibernate/jdbc? Setting up such a project cost me 30 min and gives me full flexibility choosing the stack I need for my project.

debarshri 11y ago
none actually. I think these kind of frameworks essentially reduces lot of boiler plate code. Your code might look a bit cleaner.
atomashpolskiy 11y ago
Speaking from my experience, benefit accumulates with the increasing number of applications under your authority, esp. in case each of these applications is some variation of CRUD Web Forms / Report Generation / Data Processing & Migration (read: typical enterprise environment) and shares most of its' dependencies with other applications, while still having a unique configuration. In such environment, having the means to create a vanilla project configuration and then extend/customize it a tiny bit for each app is immensely helpful. Now, of course, this can be achieved without bootstrapping frameworks, but the real game-changing feature is that you get a single "executable jar" artifact for deployment: - VERY convenient and straightforward to use with containers such as Docker - if you don't use Docker, 100 jars are still easier to maintain than, say, a cluster of 100 Jetty instances - possible to use CLI commands to run short-living daemon jobs; no need for a separate job infrastructure (schedulers, triggers, executors and such), just use shell & cron Besides that you usually get: - pre-packaged health-check and monitoring tools - if bootstrapping framework is popular enough: community support for plug-and-play modules/plugins that leverage some particular framework/technology (e.g. Bootique framework is an excellent example of modular approach: https://github.com/nhl/bootique https://github.com/nhl/bootique)
- eip 11y ago
  >but the real game-changing feature is that you get a single "executable jar" artifact for deployment Like a war file?

by gd78 11y ago

debarshri 11y ago

none actually. I think these kind of frameworks essentially reduces lot of boiler plate code. Your code might look a bit cleaner.

atomashpolskiy 11y ago

Speaking from my experience, benefit accumulates with the increasing number of applications under your authority, esp. in case each of these applications is some variation of CRUD Web Forms / Report Generation / Data Processing & Migration (read: typical enterprise environment) and shares most of its' dependencies with other applications, while still having a unique configuration. In such environment, having the means to create a vanilla project configuration and then extend/customize it a tiny bit for each app is immensely helpful. Now, of course, this can be achieved without bootstrapping frameworks, but the real game-changing feature is that you get a single "executable jar" artifact for deployment: - VERY convenient and straightforward to use with containers such as Docker - if you don't use Docker, 100 jars are still easier to maintain than, say, a cluster of 100 Jetty instances - possible to use CLI commands to run short-living daemon jobs; no need for a separate job infrastructure (schedulers, triggers, executors and such), just use shell & cron Besides that you usually get: - pre-packaged health-check and monitoring tools - if bootstrapping framework is popular enough: community support for plug-and-play modules/plugins that leverage some particular framework/technology (e.g. Bootique framework is an excellent example of modular approach: https://github.com/nhl/bootique https://github.com/nhl/bootique)

eip 11y ago
>but the real game-changing feature is that you get a single "executable jar" artifact for deployment Like a war file?