In order to demonstrate the idea we plan implement a proof of concept of union-db and demonstrate it’s abilities publicly. The PoC will be composed from two parts: the database library and the demo project.
As suggested by other people, distributed transactions performance is the main concern of union-db. If they can work efficiently in multi-subnet multi-canister setup, then this database makes sense. If they won’t - it is better to learn this earlier. So, for the library, we will only implement the transactions engine, assuming that we’re making it to enable general purpose distributed transactions for any kind of application, not just databases. Our design is well alligned with these goals.
Estimated date: 1st of september 2023.
What will be implemented:
What will not be implemented:
As a demonstration of distributed transactions, we propose to implement an online-shopping app, similar to what was described as an example in Transactions section. More precisely, this is a dapp, that allows you to sell goods to other people, using cryptocurrency as a payment method. The payment is done via an external service, that works like an invoice canister - your smart-contracts create an invoice, the client pays for the invoice, and the service calling you back via a provided callback. The app itself will have three canisters in its perimeter: a user canister, a product canister and an order canister, each of which is responsible for managing the respective entity. The whole app seems like a realistic great example, that can be extended, utilizing the functionality of further library develepments.
This is a full-stack demo, with frontend and stuff. So the task is given as an enumeration of interfaces and flows to implement.
Estimated date: 1st of september 2023.
What will be implemented:
Buy button with a quantity field.