Design Good Schemas - Get a Better Database - Nuri Halperin - NDC Oslo 2023

Table schemas in relational databases have a huge impact on your future performance and ability to maintain your application. In a world of CI/CD this is amplified since it can hold back your deployments and flexibility.

So how do you design tables that serve your applications well? Is normalization to the Nth degree sufficient? Can't I just throw an index on a table and get good performance? Just develop a POCO/POJO and let your ORM take care of it? (No, no, and no!)

In this session, you'll find out how to step up your schema-design game by adopting a relational mentality. The session will cover aspects of modeling, mapping models to tables, and all the way down to data types and fields.

Check out our new channel:
NDC Clips:
@ndcclips

Check out more of our featured speakers and talks at

[mwA]

My expierence with ORMs has been positive, and when they get in the way I can always use SQL.

[TheBayru]

Very enlightening, encapsulates everything I dislike about geo-databases of all sorts (blobs, opaque datatypes, multi-entity-tables, out-of-domain values, ...)

[RoamingAdhocrat]

how do you feel about GUID primary keys, except the first one is a generated GUID and the rest are sequential from that

[reallylordofnothing]

at 41:39 Begins a 5 min rant because he gets caught out of being asked what if the natural key changes and keeps insisting to deal with that is less painful than doing joins.

[olegprog]

can't agree with the advice to use natural primary keys
speaker can't even answer the most obvious question - how to choose natural primary key for the 'users' table?

[oguzhanK]

Bu 220v olmasi guzel ama kac saat dayanir acaba kontak kapaliyken?