| Age | Commit message (Expand) | Author | Files | Lines |
|---|---|---|---|---|
| 2018-10-29 | Migrate MDBC code to org.onap.music |   Arthur Martella | 70 | -226/+226 |
| 2018-10-26 | Additional cleanup to match pseudocode |   Enrique Saurez | 17 | -313/+194 |
| 2018-10-26 | Change code structure to match pseudocode | Enrique Saurez | 13 | -178/+180 |
| 2018-10-25 | Update Music Interface and readme instructions |   Tschaen, Brendan | 7 | -65/+85 |
| 2018-10-22 | New gitignore | Enrique Saurez | 23 | -752/+347 |
| 2018-10-17 | Finish adding METRIC code | Tschaen, Brendan | 29 | -369/+817 |
| 2018-10-16 | Initial commit | Tschaen, Brendan | 81 | -0/+13575 |
 |
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 |