This article will be the first of a series of posts where we'll be learning about the PostgreSQL database and its internals. I admit that this is quite a vast topic, but I'm on a journey to learn it, and this series is a concise version of what I've learnt (Be my guest).
Before we begin this long adventure, it is beneficial to answer the question, "Why study the internals of PostgreSQL?"
10,000 Reasons
Having no thought, we all know the topic of database internals is not negotiable for those who are/aim to be database developers. An understanding of how databases work is paramount in the development of a database. Creating improvements to existing databases will also require understanding how it works presently.
What about those who aren't database developers? Maybe you're a developer who has to deal with databases (and most do), or perhaps a database administrator. In the dynamic world of databases, you will stand an advantage by knowing the trends. It will increase your understanding of the peculiarities of the different databases and aid the decision process of which one better suits your business needs.
Also, understanding the underlying infrastructure of databases will enable you to track down performance issues and optimise queries.
Conclusion
Although studying databases can be intimidating at first, learning it benefits the hobbyist, student, software developer, or database developer.
Top comments (0)