pagila VS AdventureWorks-for-Postgres

The tutor told us that he wrote the whole file for us, but now thanks to both your leads I have found out that the file PAGILA is a GIT project at https://github.com/devrimgunduz/pagila , the "translation" of Sakila training database for MySQL.

One day, I was puzzled about how to generate some random data for development and testing without leaving my warm SQL console (in my case, psql). That’s when this set of SQL-scripts was born to generate a large amount of data for Pagila, a popular PostgreSQL sample database. You can find these scripts here: https://github.com/synthesized-io/pagila-data-generation (in "sql" folder) – and adapt them to your database schemas. I would be extremely grateful for any advice and ideas.

Create HTTP and/or gRPC server for pagila database (DVD rental database). Each server should expose metrics for scraping as well as emit traces (either to Zipkin or Jaeger, or if you feel adventurous you can support both). Start with either HTTP or gRPC and first implement just Customer service that would return customer by ID and allow inserting new one, that should be good start. When done with server(s) create GUI applications, one native, one for web (Rust + WebAssembly). Everything should be pushed to GitHub, have GitHub Actions configured for tests and build.

You can get interesting sample db here: https://github.com/devrimgunduz/pagila - it uses quite a lot of different features of pg, including fkeys.

Would running a sample database in a container also be too much? You could have some example images with a schema like Pagila loaded into them.

You can use this Adventureworks for Postgres repo to practice.

Microsoft's Adventureworks OLTP sample database in postgres.