Data Modeling with PostgreSQL Schema

Executing the basic CRUD commands is nothing new when it comes to building a system. A well-thought system it’s very agnostic, and concepts are transferable within different lower level products. Some of the most popular RDBMS involve PostgreSQL, OracleSQL, MySQL. But where does the data comes from? How often does the data change? How many files do we have, and how often we get new ones? Can we blame IoT 🛰 devices?

To the infinity and beyond… - Buzz Lightyear 1995

In the following application are given directory paths of where the client-side system is storing data files based on a music application product. I analyzed the data, build its entities and form the basic link between them. The analytics team is particularly interested in understanding what songs users are listening to.

cur.execute("DROP DATABASE IF EXISTS ...")

Github


This project was completed under the Data Engineer Udacity Nanodegree link

tech: PostgreSQL, Python, Pandas