Yes, and that's the main advantage of choosing (a) or (b). But it's not quite as hard as it sounds; since all your state is safely in fdb you "just" have to worry about load balancing a stateless service.
got it, what will you suggest to do something like that? a simple RPC with a good async framework I've read,
like what? an RPC service on top of Twisted for python, similar things in other languages?
thanks :)