Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-3289

Make the use of different/multiple storage engines transparent to apps

    XMLWordPrintable

    Details

    • Type: Epic
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Icebox
    • Component/s: None
    • Labels:
      None
    • Epic Name:
      Engine abstration

      Description

      MaxScale is in a great position to hide some of the complexity associated with using different storage engines from applications and developers. The goal is to effectively hide the notion of storage engines so developers just work with databases and tables. They don't have to worry about which table to use and when. In a sense, the same is true for DBAs. Simplifying the use of multiple storage engines and providing a centralized location to manage it in terms of ensuring applications get the most of our storage engine choices.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              shane.johnson@mariadb.com Shane Johnson (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:

                  Git Integration