| Age | Commit message (Expand) | Author | Files | Lines |
|---|---|---|---|---|
| 2018-11-20 | MusicSqlManager Removal, othe code refactors |   Tschaen, Brendan | 2 | -4/+12 |
| 2018-11-20 | Merge "TxDigest replay and code restructure" |   Bharath Balasubramanian | 3 | -482/+46 |
| 2018-11-19 | Query processing with Calcite |   Vikram Potturi | 3 | -0/+0 |
| 2018-11-16 | TxDigest replay and code restructure | Tschaen, Brendan | 3 | -482/+46 |
| 2018-11-14 | Remove unwanted Trigger creation |   st782s | 2 | -9/+11 |
| 2018-11-06 | Self contain the unit tests | Tschaen, Brendan | 6 | -449/+48 |
| 2018-11-05 | Modularized mdbc build |   Rob Daugherty | 13 | -0/+1933 |
 |
index : 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. | Grokmirror user |
| aboutsummaryrefslogtreecommitdiffstats |