I'm not sure yet. Our sharding pattern initially will be single-tenant, so I guess I could use the Shard Map Manager to get the DB location for a given tenant id. Where 'location' indicates the shard connection string, which I can then provide to an LLBL adapter.
I also assume that the Shard Map Manager would take care of caching these locations for quick access, and I wouldn't worry about changes to the map at runtime.
However, if we later evolve the app to multi-tenant and need to use Data Dependent Routing, would that be an issue with LLBLGen?