You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Ioan Eugen Stan (Jira)" <se...@james.apache.org> on 2020/06/17 14:17:00 UTC

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

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

Ioan Eugen Stan commented on JAMES-2586:
----------------------------------------

Hi [~matthieu], 

I fully believe and support what you mentioned. 
Are you planning to work on this?

Having that implementation is going to also require maintenance.
If you or nobody else is going to work on this, let's please close the issue. 


> 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
>
> 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.3.4#803005)

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