Skip to content
This repository was archived by the owner on Feb 16, 2025. It is now read-only.

Document performance considerations #708

@lesv

Description

@lesv

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority: p2Moderately-important priority. Fix may not be included in next release.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions