Hi Rainer,
it is always difficult to explain why one is convinced of something... :-)
For me it is always important to improve way of doing things and so I went
a long way
in the last 25 years of webdevelopment...
from cgi-bin/perl to java with servlets and system.out.println HTML over
all java web frameworks to
a long period of using Apache Webserver and Apache Wicket and Apache Tomcat
with WAR deployment.
There was a time when Spring MVC still was working with JSPs, what I
refused to use since I has experienced Struts monster components
and the cleaner way of Apache Wicket.
When Spring MVC switched over to Thymeleaf (developed of a former Wicket
fan) I gave it a try a never looked back,
because Spring MVC made it easier to not only develop webapps (what wicket
focussed on), but also on the same level supporting REST-API-Endpoints.
I still packaged it into WAR files and using Tomcat.
Tomcat was mature stuff, but
- a webapp needed first installation (and maintenance) of a tomcat server
- tomcat sometime hung up ("zombied"), so we always added a cronjob
restarting tomcat every night (these was more than 6 years ago)
- deployment to that time was mostly manual copying and restarting
So we gave Spring Boot a try, that provides an embedded tomcat.
Long story short: we never looked back, now running more than 50 webapps,
services and workflow jobs since years based on spring boot.
One of the big advantages is: Spring is developed by people that know what
is needed in practical day to day work (seems so).
It always introduces things making your job easier and remove boring
boilerplate coding work.
To make a decision depends on:
- If you think that in a project a lot of development effort and time
should go into ramping up a skeleton or environment before starting to code
the functionality asked for,
then Spring Boot is not a good choice
- If you do not like to spend time in every project to develop a
configuration file reading "framework" or logging logic or environment
detection (local/dev/staging/prod) or unit testing environments or
monitoring endpoints
for dashboards, then spring boot is the right stuff. you get a lot (only if
you want and add maven dependencies, you are still free in choosing how far
you will go)
out of the box
if you want have an easy introduction: I wrote some blueprint documentation
here
https://github.com/dbmdz/blueprints
especially spring boot
https://github.com/dbmdz/blueprints/tree/main/webapp-springboot-thymeleaf
So, how does it fit with empire-db?
As Spring Boot is totally open to any persistence framework, it is no
problem to go ahead with empire-db
(some documentation on jdbc stuff:
https://docs.spring.io/spring-framework/docs/current/reference/html/data-access.html#jdbc
)
The only benefits I used from Spring Boot is the automatically creation of
a JDBC Datasource provided by using application.yml config with spring
defined config
properties: spring.datasource.utl and password and username
see documentation
https://docs.spring.io/spring-boot/docs/current/reference/html/application-properties.html#application-properties.data.spring.datasource.url
So the example code of spring boot empire-db is a shorter and focusses on
the test itself.
and spring boot stepped never in my way of using empire-db.
Am Fr., 4. März 2022 um 21:14 Uhr schrieb Rainer Döbele <[email protected]>:
> Hello Ralf,
>
>
>
> first I want to thank you for your code donation.
>
> As an Open Source project we depend on people who are willing to
> contribute and give something back.
>
>
>
> Since I had some access problems with Github, Jan was so kind to get the
> pull request and merge it.
>
> Then I just made a view adjustments and I also had a quick look at it.
>
>
>
> To be frank, I have no clue, what Spring-Boot is all about.
>
>
>
> So I asked Mr. Google and quickly this is what I found:
>
> Spring-Boot AutoConfiguration - Too much magic? : java (reddit.com)
> <https://www.reddit.com/r/java/comments/6byre7/springboot_autoconfiguration_too_much_magic/>
>
>
>
> Plus this video:
>
> https://www.youtube.com/watch?v=Sw7I70vjN0E
>
>
>
> Now I am just curious why you are using Spring-Boot, and why you think it
> would be a good fit for Empire-db.
>
> As I am quite willing to understand and learn 😉
>
>
>
> Best regards,
>
> Rainer
>
>
>
--
Ralf Eichinger
Georg-Lindau-Str. 5
80634 München
tel: 089 / 2375 6862
mobil: 0152 / 5368 5735
email: [email protected]
