One way to store NoSQL key keys is different from the relational way of thinking, because one-two-one relationships can be represented in the same table using lists and maps.
For example, if your user has several credit cards, each of which is a tuple (type of card, last 4 digits of the card, token from the processor representing the card, billing zip code), they may be present as a list of cards. JOINTS between two many-to-one tables exist because RDBMS models atomic data, where in Aerospike this data will be modeled as a complex data type.
source share