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/09/30 01:47:00 UTC
[jira] [Created] (POLYGENE-311) Blockchain Entitystore
Niclas Hedhman created POLYGENE-311:
---------------------------------------
Summary: Blockchain Entitystore
Key: POLYGENE-311
URL: https://issues.apache.org/jira/browse/POLYGENE-311
Project: Polygene
Issue Type: New Feature
Reporter: Niclas Hedhman
Assignee: Niclas Hedhman
Attachments: blockchain-architecture.png
With blockchain technology becoming more and more prevalent in our industry, we should add support for blockchain operations and storage.
The first and easiest way to get enough experience with blockchain is to implement an EntityStore being backed by a blockchain.
Since there are some many different ways one can go about it, we need a great deal of flexibility for the users. A proposed architecture is attached to this issue, but also present in Git https://github.com/apache/polygene-java/blob/develop/artwork/blockchain-architecture.png
The major recurring flexibility concern will revolve around "signing". It needs to be possible for Polygene applications to delegate to the actual user of such application, as apps shouldn't hold private keys of its users.
The storage of the data needs to be split in two, as storage on blockchain is relatively expensive, so the blockchain is primarily for storing Identities back a the secondary store which should be immutable, fully distributed and preferably decentralized. One such store exists, namely IPFS. However, if decentralization is not a requirement, then HDFS, Cassandra, SQL and almost any type of store could be used.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)