How to choose the right database for your application - Zoe Steinkamp - NDC Oslo 2023

In this talk, we will review the strengths and qualities of each database type from their particular use-case perspectives. Although having everything in one database seems like the straightforward path, it is not always the most cost or time effective path. Many Databases have become more specialized for the types of data they handle. Learn how to make the right choice for your workloads with this walkthrough of a set of distinct database types (graph, in-memory, search, columnar, document, relational, key-value, and time series databases). Learn about current trends in the database ecosystem and then learn about a number of different specialized databases and their strengths and weaknesses. This presentation will go over some of the fastest growing segments in the database space.

Check out our new channel:
NDC Clips:
@ndcclips

Check out more of our featured speakers and talks at

[KeremyJato]

This was a cool talk. Well structured and very clear, and did a good job of contrasting how different DB types solve different problems. Nice stuff, Steinkamp

[RU-qvjl]

For over 99% of companies PostgreSQL and the extensions available are FOSS and can do anything they need. Relational, document, vector, timeseries, graph, KV, etc. Postgres has you covered. Want row store, compressed row store, column format storage or even parquet storage? Postgres has that covered. Want scaleout? Postgres has that covered too. It’s all free and you can deploy it anywhere. If you want to start with something start there. If you then realise that you need something that is a little bit better because it is very specialised then change. However, I cannot think of anything where there is an order of magnitude difference between Postgres + extensions and more specialised publically available DB that more than at most 1% of companies might need.

[mwonsil]

Before relational databases, we worked on network and hierarchical databases. The indexes were designed into the database. And by that, if we wanted to add or remove an index, we would have to unload and reload the database until 3rd party tools filled that gap. The hierarchical database tables could link to only one parent where network databases could link to multiple parents.I remember Object Oriented databases appearing in the 80s - a little too early? Great talk! I learned a lot.

[BhaskarJayaraman]

At 26:31 redis isn't looking for gossip somewhere but the protocol between primary and secondary redis replicas and how primary syncs with secondary

[fburton]

Great talk, interesting and informative. Thanks for that.
(Btw, you are still very young!)

[steftrando]

Great talk but she breathes out from her nose at the end of a phrase very often, and she needs a water bottle that stays open so she doesn’t have to constantly twist it open and closed.