#20: Weekly Recap — Database Fundamentals
Happy Friday (for real this time)! Hope you had a joyful Diwali for those celebrating it. Here is your weekly recap on the theme of database fundamentals.
Don't feel bad if you haven't made significant progress this week. What's important is to keep moving forward, no matter the pace. Focus on the journey, not just the destination.
Issues
Weekly Podcast
Knowledge Check
What’s the meaning of the ACID acronym?
What does consistency mean in the context of ACID?
What’s the CAP theorem?
Is the C in ACID the same as in CAP?
Which one is infeasible in practice: CP, AP, or CA? Why?
What’s the PACELC theorem?
What’s the missing dimension that is brought by PACELC compared to CAP?
If you’re currently working with a database, are you aware of its trade-offs?
What are the safety and liveness properties?
Guaranteeing the delivery of a message: is that a safety or liveness property?
Guaranteeing that an application cannot access memory out of bounds: is that a safety or liveness property?
Explore Further
You can’t sacrifice partition tolerance // Make sure also to read the erratum on whether a node failure is a partition.
Visual of the Week
This is your last day to enjoy full, free access. Starting next week, free subscribers will only receive one issue per week. Upgrade today to enjoy a limited-time 50% discount on your first year of paid subscription.
Want a preview of the next six months first? Take a look here. We will discuss database fundamentals, reliability, code health, coding challenges, algorithms and data structures, cognitive biases, unit tests, systems performance, database isolation, computer architecture, cloud, functional programming, API, caching, rollout, communication, code performance, and database consistency.
Next week, the theme will be… reliability fundamentals! 🎉