music/mdbc - The most crucial recipe is a multi-site database cache (mdbc) that enable ONAP components that maintain state in a SQL database to avail the benefits of MUSIC without compromising their need to use transactional SQL DBs. These ONAP components can rely on existing db clustering techniques like MariaDB for transactionality and complex querying within a site. mdbc will intercept each of these read/write calls to the db cluster and mirror this state to other geo-distributed sites through MUSIC either synchronously or asynchronously (configurable at a table-level). For example, components like the ONAP Service Orchestrator that use MariaDB to maintain state can directly use this recipe with no change to their SQL code.

Age	Commit message (Expand)	Author	Files	Lines
2018-11-30	Upgrade to MUSIC 3.2.1	Rob Daugherty	2	-5/+7
2018-11-29	ownership and relinquish	Enrique Saurez	17	-2203/+2752
2018-11-26	MySQL JUnit test	Tschaen, Brendan	6	-41/+34
2018-11-20	Replay operations into SQL DB	Tschaen, Brendan	5	-173/+250
2018-11-20	MusicSqlManager Removal, othe code refactors	Tschaen, Brendan	18	-2098/+1622
2018-11-20	Merge "TxDigest replay and code restructure"	Bharath Balasubramanian	25	-648/+757
2018-11-19	Query processing with Calcite	Vikram Potturi	41	-0/+282
2018-11-16	TxDigest replay and code restructure	Tschaen, Brendan	25	-648/+757
2018-11-14	Remove unwanted Trigger creation	st782s	4	-2/+9
2018-11-05	Modularized mdbc build	Rob Daugherty	58	-0/+12413