bolt VS developer-roadmap

This crate started out as just a way for me to learn how boltdb works, while learning Rust at the same time. But somehow people started finding and using it and seem to like the simple API, so I figured I might as well share it in case someone else finds it useful too. If you want to know more about my motivations and the history of this crate, you can read the release notes on version 0.8.0!

Some example of embeddable database could be genji, badger and boltdb

Designing Data Intensive applications- specifically chapter 3 and 4 which deal with strategies and algorithms for storing and encoding data to be stored on disk and their pros and cons.

Once you read that, I'll suggest reading the source of a simple embedded key-value database, I wouldn't bother with RDBMs as they are complex beasts and contain way more than you need. BoltDB is a good project to read the source of https://github.com/boltdb/bolt, the whole thing is <10k lines of code and is a full blown production grade system with ACID semantics so packs a lot in those 10k and isn't just merely a toy.

Bolt db and Bolt db's author post to go with it.

https://github.com/boltdb/bolt is a ACID B+ tree key-value store

For a single server, SQLite, or boltdb[0]

I've never had to scale horizontally. I develop in Go and you can get very far along with just vertical scaling (aka beefier hardware).

Therefore I can't give concrete examples of a distributed db-as-a-library.

But all that you need is to extend the functions that fetch data to not just fetch from disk but from "peers" as well. For this to work you need servers (instances) to know about each other, and as you add more they also get added to their peers - sort of like a bittorrent network. I don't think it's difficult to do.

SQLite might not be suited for being distributed (although RQlite[1] claims to have done it).

Making a distributed data storage based on boltdb[0] is probably more feasible.

Whatever the case, there's no reason why a data storage engine can't be a library, even if it's distributed.

[0]: https://github.com/boltdb/bolt

[1]: https://github.com/rqlite/rqlite

If you're starting your journey in web development, here is a roadmap to follow. Understand that Web development is not merely an extension of programming; it's a distinct field that requires a unique blend of coding and visual design skills. Embrace the importance of visual aesthetics from the get-go, and continuously work on improving your design sense. Trust me it will pay off in the long run, and you'll be able to create truly exceptional web experiences that not only function well but also look and feel amazing.

Github developer roadmaps (backend, frontend, cloud ...)

Roadmap.sh (https://roadmap.sh/)

Web Developer-Roadmap GitHub Link: developer-roadmap Crafted by kamranahmedse, this roadmap acts as a compass for developers navigating the vast landscape of technologies. Covering front-end, back-end, and DevOps, it aids developers in charting a learning path aligned with their goals.

✅ kamranahmedse/developer-roadmap: https://github.com/kamranahmedse/developer-roadmap

It may also be beneficial to start with a high-level overview of what there is to learn in a given area, to understand the overall lay of the land - and then use ChatGPT to dig deeper into selected topics. There are many good resources that provide such an overview, like roadmap.sh or my "Definitive Guide to Succeeding as a Professional Dev".

5. Roadmap

Equipment: Find out more about career paths in development at https://roadmap.sh/. For a detailed self-taught program, see Kamran Ahmed’s Computer Science Roadmap: https://roadmap.sh/computer-science.

Roadmap.sh serves as a comprehensive guide for developers planning their career paths and skill development. It offers structured roadmaps for different domains, helping developers navigate their professional journey.