I see... so the MariaDB top-half (by "top-half" I mean everything that sits above the storage engine) doesn't do nasty things like caching? If it did, then writes at other MariaDB sites wouldn't show up in reads performed at the site caching the data. 

If the MariaDB top-half does nothing more than essentially translate user operations / queries into calls on the SE, then in theory nothing special must be done to deploy MariaDB at multiple sites accessing a shared storage engine.

Jonathan

On Tue, Jul 19, 2016 at 10:20 PM Daniel Black <daniel.black@au1.ibm.com> wrote:




On 20/07/16 14:31, Jonathan Ellithorpe wrote:
> Follow-up: I see in the blog pointed to by Daniel mentioned an SE for
> Cassandra.... so I take it the answer is yes? Does anyone have
> experience with this / know if anything "extra" must be done to make
> that work?

It falls to the responsibility of the storage engine to ensure that the
ACID guarantees are implemented.

> Jonathan
>
> On Tue, Jul 19, 2016 at 9:23 PM Jonathan Ellithorpe <jde@cs.stanford.edu
> <mailto:jde@cs.stanford.edu>> wrote:
>
>     Thanks for the references! That helps a lot
>
>     One other question I have is: can MariaDB work in a distributed
>     fashion? To be more clear, the storage backend I'm developing is
>     distributed, like Cassandra, and I would like to deploy many MariaDB
>     instances that all access the same storage cluster. Can this be done?


_______________________________________________
Mailing list: https://launchpad.net/~maria-discuss
Post to     : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp