[
https://issues.apache.org/jira/browse/JAMES-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140474#comment-17140474
]
Ioan Eugen Stan commented on JAMES-2586:
----------------------------------------
We can decide how we use the tools and *document* those decisions.
We can do that as part of a future community effort (via a community call).
That way we as a community decide and we enforce them by pointing things out.
It should be more of a soft enforcement than a hard one: please do that instead
of this, because it's more useful for us to maintain the project.
What I would like to get out of is a clear process for how we encourage
contributions.
This is intended to make our lives simpler when we manage the future of Apache
James: we have a simple process, we expect people to behave and we have some
expectations of how things will unfold.
> 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-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
