You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@polygene.apache.org by "Niclas Hedhman (JIRA)" <ji...@apache.org> on 2018/04/28 02:10:00 UTC

[jira] [Resolved] (POLYGENE-303) Zookeeper Entity Store

     [ https://issues.apache.org/jira/browse/POLYGENE-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Niclas Hedhman resolved POLYGENE-303.
-------------------------------------
    Resolution: Fixed

> Zookeeper Entity Store
> ----------------------
>
>                 Key: POLYGENE-303
>                 URL: https://issues.apache.org/jira/browse/POLYGENE-303
>             Project: Polygene
>          Issue Type: Improvement
>            Reporter: Niclas Hedhman
>            Assignee: Niclas Hedhman
>            Priority: Major
>
> **Zookeeper is a nifty way (once it is set up and running) to keep configurations in sync. And since Configuration for Polygene is entities, by implementing a generic Zookeeper Entity Store we get both a cool Configuration store, but it can also be used for any arbitrary storage needed (except that Zookeeper is not meant for heavy duty loads, and reasonable caution needed to be taken). But Polygene also (still, I hope) supports multiple entity stores to be used in parallel, so one could place the 'reference data' on Zookeeper while most of the OTP is done elsewhere. All with minimal effort.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)