[MXS-3289] Make the use of different/multiple storage engines transparent to apps Created: 2020-11-06  Updated: 2021-03-31

Status: Open
Project: MariaDB MaxScale
Component/s: None
Affects Version/s: None
Fix Version/s: Icebox

Type: Epic Priority: Minor
Reporter: Shane Johnson (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Blocks
blocks MXS-3286 Smart Engine-aware routing in MaxScal... Closed
blocks MXS-3287 ColumnStore-aware routing Closed
blocks MXS-3288 Automatic HTAP DDL Closed
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.


Generated at Thu Feb 08 04:20:20 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.