Back in v3b5, I used James with Spring and with JDBC/mySQL. I realize
that several new implementation combinations have been added. I've read
articles about Guice, Cassandra, Spring, JPA, Docker. I understand
basically where each one fits into the world of James. And looking at
the JAMES package download options, I see that I've got a lot of choices
with various combinations of these. What I am having trouble finding
are details about why I would want one over the other and what the
advantages/disadvantages are of one over the other.
It appears that there is an choice of Cassandra vs JPA vs JDBC/(MySQL).
Then there is a choice of Spring vs. Guice. And also there is a choice
of Docker vs. non-Docker. I'm setting up my new configuration on AWS.
My goal is to make it the most 'strategic' implementation for James.
But I don't know which choices are the right 'strategic' answers, and if
the 'right' answer depends on certain criteria, I would like to
understand the criteria.
If someone could take a few minutes to provide some decision criteria
for a) Cassandra/JPA/JDBC; b) Spring/Guice; c) Docker/non-Docker
-- What are architectural advantages of one choice over the others
-- Are any of the options going to be deprecated soon?
-- When would I want to choose one over the other (or NOT
choose one over the other)?
-- If I have an 'old' Spring/JDBC implmentation with a huge
existing database, does that affect choices? (possibly requiring a
massive db migration)
-- If I have custom matchers/mailets (some of which use JDBC),
will I have to rewrite those if I choose certain implmentations?
-- Are there required fixed combinations (e.g. if you select
Cassandra, you have to use Docker, etc)?
Not a showstopper for me. My first goal is to just get my old
Spring/JDBC version running on 3.3. But after that, I'd really like to
look into moving to the strategic implementation.
Thanks.
Jerry
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
