How is turbo_session different from memcache/Cache

turbo_session follows a similar mentality of all of the above (and uses "bins" similar to cacherouter) but also provides a failover mechanism so if one of the storage methods fails, the next in line will be used. So if you have memcache and files configured, should memcache crash or run out of RAM, file storage will be used and the site will remain functional (some users will lose their sessions and will have to re-login).

does it work well in combination with cacherouter?