Commit e977659c authored by Shawn McKinney's avatar Shawn McKinney
Browse files

mention coherency and 2.6

parent 0239045c
Pipeline #2879 passed with stage
in 57 minutes and 31 seconds
......@@ -34,6 +34,7 @@ More considerations:
- The sequence of operations isn't important. For example, read after update isn't required by the client.
- If your client can handle both connection pooling and load distribution then it's preferable to lloadd.
- Clients that require a consistent session (e.g. do writes), the best practice is to let them set up a direct session to one of the providers. The read-only clients are still free to use lloadd.
- 2.6 release of lloadd will include sticky sessions (coherency).
H2: Runtime configurations
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment