This repository was archived by the owner on Feb 16, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 61
Document performance considerations #708
Copy link
Copy link
Open
Labels
priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.‘Nice-to-have’ improvement, new feature or different behavior or design.
Description
Proposal
Emblem's decision record for session state should mention the latency characteristics of the various options as well as cost.
Problems this will solve
I'm not convinced we should be pointing customers at GCS for session store. #258 Firestore, which is built on top of Spanner is a lot faster than Datastore and makes some sense in this environment. Choosing Firestore would have required enabling the API, but would otherwise be of minimal impact on the user.
Alternatives
Small users should be considering Firestore. Larger users may be interested in Redis / Memcache or Postgres / AlloyDB / Spanner or Bigtable.
Additional context
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.‘Nice-to-have’ improvement, new feature or different behavior or design.