# NoSQL flash cards: Journeyman level

10 NoSQL terms at the Journeyman level, as flash cards.

Updated: November 19, 2026

- [Study these as flash cards](https://www.ask-codey.com/decks/nosql/3/flash)
- [Play Memory with them](https://www.ask-codey.com/games/memory?category=nosql&level=3)

## Terms in this deck

- [Access Pattern Design](https://www.ask-codey.com/glossary/access-pattern-design): Designing NoSQL data around the queries the app will run.
- [BASE](https://www.ask-codey.com/glossary/base-nosql): The relaxed guarantees many NoSQL systems give, versus ACID.
- [CAP Theorem](https://www.ask-codey.com/glossary/cap-theorem): During a network split, a distributed database must pick consistency or availability.
- [Eventual Consistency](https://www.ask-codey.com/glossary/eventual-consistency): Copies catch up shortly after a write, so a read may briefly be stale.
- [Partition Key](https://www.ask-codey.com/glossary/partition-key): The field that decides which partition stores a record.
- [Replication](https://www.ask-codey.com/glossary/replication): Keeping copies of data on several machines for safety and read capacity.
- [Secondary Index](https://www.ask-codey.com/glossary/secondary-index): An index for looking up records by a field other than the main key.
- [Sharding](https://www.ask-codey.com/glossary/sharding): Splitting data across several machines by key.
- [Strong Consistency](https://www.ask-codey.com/glossary/strong-consistency): Every read sees the latest write.
- [TTL (Time to Live)](https://www.ask-codey.com/glossary/ttl-time-to-live): A setting that makes a record delete itself after a set time.

[Read them in the glossary](https://www.ask-codey.com/glossary/subjects/nosql/journeyman)

Source: https://www.ask-codey.com/decks/nosql/journeyman
