> is using 'first-primary' the equiv of using not using sessions api at all - even if i have replica

is using 'first-primary' the equiv of using not using sessions api at all - even if i have replication enabled?
For the first call, yes, they are the same.

If you continue using the same session object though, your subsequent queries will potentially be processed by a replica that is at least up-to-date as your last read/write. If you don't use the sessions API ALL requests are going to the primary (treated as
first-primary
).

if 'first-unconstrained' detects a write through sessions will it be upgraded to a primary, thus adding extra latency?
Yes, if a query is a write, we will automatically forward it to the primary for execution. It still flows through the replica location though, so there might be some extra latency (or not) depending on these locations.
Was this page helpful?