Forging die kopf

Ambitious Experimental Database Management System written to experiment with techniques and concepts I learn to mimic/mock (as nearly as possible) the 🧠.

I will be posting new blogs under this series, each about something I learned along the way. The repo for this series will be publicly available under my personal account. Any contibutions are most welcome 😘

Why

Recently I started learning about database engineering and rust-lang. I wanted someway to test what I just learned. I am more of a...

See for yourself guy, hence the project kopf

Brief

This project is named kopf, meaning head in German. I gave it such a name because that is what this project's design philosophy originates. kopf heavily borrows functional behaviors of the human head, actually the brian, but linguistic German for brain is Gehirn. I find it hard to pronounce, hence kopf it is 😂.

I always inspire this beast inside each of us, it is tunned by the evalution, battle tested by the time, astonishing heavy-compute-powered, high fault tolerant and self-healing concurrent computer, brain and its associates; litteral head, i.e. kopf.

Design Philosophy

As mentioned above, I will base kopf to human-brain. Thus, as of now I came up with this system:-

kopf_v1.0.0_rc_system_design

kopf will be module-based(somewhat derived from micro-services arch) and be able to plug-n-play at runtime. I will equip hybrid of spiral and waterfall sys-dev-lifecycle to suit my convienience.

Each module will have a prototype version in python and actual implementation in rust and C(for legacy libs I'll use using FFI) along with some springled go for network stuffs. I am using multiple languages to get a hang of each these languages and to familiarize myself with new concepts in well diversed ecosystem 😉.

Updates and Follow Ups

I am planning on blogging my journey in this train on my personal website and personal Hashnode side. My journey will be called Forging die kopf, follow me up there to get a quick grasp of what the f*@k is giong on 😁.

NOTE. This is series is asynchronous. It only gives you futures/promises. Actual result might delay or never happen 😘 and fail. Please make sure, you check out later. Sections marked with [WIP] means, they will be updated when I've finished documenting them. Sorry for such an inconvenient methodology, but I wanted to have this series like a journal in this journey. And life has been asynchronous to me so far, thus is the series!

FAQs

How to use this DBMS?
- Please don't. This is experimental and not to be used in production/development!
Can I contribute?
- Absolutely! If you have free time to waste, please join me.
Suggestions?
- Most Welcome 🙏. Use Issues panel or Comments section in blog
Ran out of questions to answer . Please be kind enough to ask me 😎

Attributions

Icon/Mascot from macrovector and series/social template bg by Laura Ockel.

The Abstract & Epilogue

Ambitious Experimental Database Management System written to experiment with techniques and concepts I learn to mock the 🧠