At least until problem 11, which I can't advance to because it tells me I have to solve the previous case even though it's solved.
I had to fix the id in two digits cases, now you'll be able to advance
i found myself mostly reading the summary on the left though.. it was doing most of the heavy lifting. the graph looked nice, but it didn’t really add much to the understanding for me.
The inspiration came from https://sqlpd.com, which does something similar for SQL. Since what I enjoy most is talking about System Design, I thought it would be a good idea.
There are 33 cases covering replication, consistency, load balancing, caching, messaging, storage, networking, and advanced topics like chaos engineering and distributed tracing.
The cases are sequential and increase in difficulty, with a ranking system from Rookie to Chief.
The project is open source and supports Portuguese and English.
It's live at https://sdpd.live.
I've been writing about system design for a while now, and I genuinely love the topic (I talk about it weekly on my blog https://olucasandrade.com). I always wanted a tool to practice it without having to hunt down a billion references across the internet.
Every tool I found was either paywalled for the basics or completely abandoned. So, I built my own, and I have no intention of letting it go. I believe this project has the potential to build a really great community. That's why I decided to "open-source" the entire platform. It's 100% open on GitHub, and I'm already creating issues for the next planned evolutions.
How this can help you:
The idea is simple: just like LeetCode, you can submit your solution (with a diagram + textual explanation), and you can view and interact with solutions from others. No favoritism here—I truly believe there's no better way to prepare for an interview or just sharpen your skills.
I don't plan to fully "productize" this until I hit my first major goal, so feel free to play around as much as you want, and please let me know if you find any bugs.
How you can help me:
First and foremost, dropping a star on the repository (https://github.com/olucasandrade/systemstudio) is a huge boost. That alone is massive support.
But if you want to help on a deeper level, feel free to open issues or even pull requests to add new features or work on existing ones. Honestly, the potential of this platform is not something I have enough bandwidth to explore alone. Finally, spreading the word is also a big help. I want this to reach as many people as possible who need it.
Cheers!
The link to the app is: https://systemstudio.app If it gets some traction, I'll share the next steps that I plan.
#lesgo
The thing nobody talks about, cause it doesn't sell: that advice "the right tool for the right job" is the battle cry of every vendor's marketing department.
The uncomfortable truth is that PostgreSQL is not "just a relational database." It hasn't been for over a decade. It's a data platform that does what most of these specialized tools do, using the same algorithms, with a single connection string, a single backup strategy, and a single place to debug when everything breaks at 3 AM.
Not "close enough." Not "good enough at small scale." The same algorithms.
All these buzzwords, unless we're talking about truly unbelievable scale, are achievable with just Postgres.Let me show you. Actually, no... simulate it and see for yourself.