[jira] [Commented] (SYNCOPE-1006) Performance and NoSql database support

["Francesco Chicchiriccò (JIRA)" <ji...@apache.org>]

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

Francesco Chicchiriccò commented on SYNCOPE-1006:
-------------------------------------------------

Hi Lazlo,
thanks for your interest in Apache Syncope.

While I agree that JPA in general might not be the most trendy hype at the moment, I can count several deployments of the indicated size (or bigger), with no relevant performance issues.

I invite you to try a modern Syncope version (1.2.10 or 2.0.2, which both feature some search improvements) on a decent and properly configured DBMS as recent PostgreSQL (hence no MySQL / MariaDB), with adequate connection pooling.

Besides such considerations, please also take into account that Syncope 2.0 now defines an [abstract persistence layer|https://github.com/apache/syncope/tree/2_0_X/core/persistence-api], currently with a [single JPA-based implementation|https://github.com/apache/syncope/tree/2_0_X/core/persistence-jpa] available.
Nothing prevents someone (maybe you ;-)) to provide {{persistence-mongodb}} or other.

Finally, I would say that such discussion could have had better home at our dev@ mailing list; for the prosecution, you might want to [subscribe|http://syncope.apache.org/mailing-lists.html].
Regards.

> Performance and NoSql database support
> --------------------------------------
>
>                 Key: SYNCOPE-1006
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1006
>             Project: Syncope
>          Issue Type: Improvement
>            Reporter: Laszlo Miklosik
>              Labels: Improvement
>
> CRUD via the API and especially the search are very slow when you have e.g. 400.000 users with 30-40 normal attributes in place.
> JPA and relational databases are not the optimal solution for the performance sensitive problem of provisioning and Syncope's search query builder is a very complex/fragile piece of code.
> I am using Syncope 1.1.5 at the moment but I expect no miracles from 1.2.10 or 2.x with this amount of users and the same persistence solution.
> I am raising this ticket because I did not find performance related items planned in the Syncope roadmap.
> - Do you consider switching the persistence layer to a document store (e.g. MongoDB)? I think its schema-less nature would be ideal for storing flexible attributes and this way the row/document count explosion problem would be avoided by design. 
> - Another possible performance improvement would be an async layer for the persistence and/or the REST API as well. Maybe using e.g. Redis or other publish-subscribe solution for this part?
> Thanks!



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)