On Mon, 2 Apr 2012 12:48:29 +0300, Henrik Ingo <henrik.i...@avoinelama.fi> wrote: > REST API and HandlerSocket/MemcacheAPI are completely different > things. REST API is "convenience" api. Easy access over http and > key-value (or sql, even!) semantics. > > HandlerSocket and Memcache API provide "RAW" access, bypassing SQL > parser, with the key objective of achieving better performance. They > typically achieve 2x (for writes) to 7x (for reads) more, so it is > well worth having them. Marcus' GSoC is a natural progression of this > idea: Move the SQL parser (or part of it) to client side is good > scaleout architecture. You get to keep SQL (and legacy apps) yet get > better performance out of the server. > > HTTP is poor choice performance wise and of course in json_server we > use Execute API so at least for now it "adds back" all the SQL > overhead anyway.
But it doesn't have to. We have a cleaner (but not clean) engine API and with a variety of tweaks we can probably get something out that's usable directly from a number of places: replication slave, json_server, memcached etc. -- Stewart Smith _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : drizzle-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp