[Hscale-user] Hscale + high write performance

[Karel V. <ka...@ou...>]

Hi, I am looking at sharding as a means to spread the load of write
operations.  I understand that XA sharding is a 'far future' idea for
Hscale, but I am wondering if it would make sense to use the FEDERATED
storage engine on the sharded tables:

The application would see 'my_huge_table', which HScales translates to
my_huge_table[1-3] on server 0.

--server 0--
my_huge_table_1 ===> federated, connects to server 1
my_huge_table_2 ===> federated, connects to server 2
my_huge_table_3 ===> federated, connects to server 3

Would this kind of setup make sense? It still has a one-server
bottleneck, but at least we do not to buy 'better/faster/bigger' storage
for that one server, we can spread the actual storage to multiple
servers.
Would this help with write performance or would the FEDERATED engine
give too much overhead on server 0?

Regards,
Karel