[jira] [Commented] (JAMES-2586) Implement a Postgres-specific backend

["Benoit Tellier (Jira)" <se...@james.apache.org>]

    [ https://issues.apache.org/jira/browse/JAMES-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875871#comment-17875871 ] 

Benoit Tellier commented on JAMES-2586:
---------------------------------------

Following recent upgrade of Lucene, it *should* make Lucene dependency compatible with the one of OpenSearch.

This likely can allow choosing to use either OpenSearch or Lucene as a search back-end. The option can likely be exposed in the existing search module chooser.

This would allow small deployments to simplify their deployment topology by relying on Lucene on top of the local filesystem and not depend on OpenSearch dependency, which is a standalone, expensive to operate service.

This shall make James easier and cheaper to install for individuals thus expending its use cases.

Dependency being pulled by OpenSearch the only downside is that we would need to align Lucene dependency with the one brought by OpenSearch, which is the case today and would be easy regarding OpenSearch reliance on latest Lucene

CF https://github.com/opensearch-project/OpenSearch/releases + https://github.com/apache/james-project/blob/b562ce50b93c520f1bd0b418cdb16b426c469fcf/pom.xml#L649

Thoughs?

> Implement a Postgres-specific backend
> -------------------------------------
>
>                 Key: JAMES-2586
>                 URL: https://issues.apache.org/jira/browse/JAMES-2586
>             Project: James Server
>          Issue Type: New Feature
>            Reporter: Matthieu Baechler
>            Priority: Major
>          Time Spent: 235.5h
>  Remaining Estimate: 0h
>
> James has a JPA implementation of most interfaces that allows to deploy it on top of some popular RDBMS.
> However, while useful for some kind of applications, ORM are usually a bad fit for applications requiring high performance like a mail server.
> As an abstraction, it also prevents from using advanced features of a given RDBMS.
> For most usages, James would probably run great on top of Postgres, given that we use advanced features to implement search, for example.
> A good strategy would be to implement all interfaces implemented by JPA with a modern Postgres driver.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org