« Vous n’étiez pas née que j’aidais des Juifs à quitter l’URSS, alors que j’étais pro-communiste »
La jolie leçon de @JLMelenchon à cette macroniste devenue silencieuse 🤣
🗣️ SQUEEZIE s’exprime sur les rentiers : « Les gens qui veulent vivre de rentes, les gros gros chiens dans ce domaine ils achètent les apparts les plus petits possibles, parce que le ratio prix d’achat vs loyer il est phénoménal. Mais c’est que de la misère humaine, ils allument des étudiants ou des gens dans la misère à 500 balles par mois pour une taverne de gobelins »
Most APIs don't fail because of bad code. They fail because of unpredictable traffic.
If you’re building a backend meant to scale, "working" isn't enough. It has to be resilient.
Here are 5 patterns every Senior Backend Engineer uses:
1. Rate Limiting (The Shield): Don't let one rogue client or a bot scrape your entire DB. Use Token Bucket or Leaky Bucket algorithms to protect your resources.
2. Circuit Breakers (The Fuse): If a downstream service is hanging, don't keep calling it. Stop the "cascading failure" by failing fast and giving the service time to recover.
3. Idempotency Keys (The Safety Net): Network requests fail. If a client retries a "Payment" request, your system should know it already processed it. Use UUIDs for critical mutations.
4. Dead Letter Queues (The Trash Bin): Don't just discard failed background jobs. Move them to a DLQ so you can inspect, debug, and replay them later without losing data.
5. Timeout Policies (The Timer): Never let a request hang indefinitely. Every outgoing call needs a strict timeout. A hung thread is a wasted resource.
The Golden Rule: Design for the 1% of the time when things go wrong, not just the 99% when they go right.
This guy uploaded 200+ company wise interview questions with video solutions on Google Drive.
Another guy uploaded the same type of resources on GitHub
Atp, you don’t even need to buy LeetCode Premium
link : https://t.co/MCrLzFTTxJ
Certainly one of the BEST channels for System Design:
https://t.co/oIaXtfwOgj
1. API Design
https://t.co/y13ymiLR9c
2. Sharding
https://t.co/Kh7aRGwCWu
3. Caching
https://t.co/y6cs0Ha8Tq
4. Concurrency
https://t.co/gugqA4I1ZR
5. Data Modeling
https://t.co/x6dVIYEmSF
6. Rate Limitter
https://t.co/x6dVIYEmSF
7. DB Indexing
https://t.co/npxaC0fY6V
8. CAP Theorem
https://t.co/TsPKqPaDIN
9. Kafka
https://t.co/gBoFBmd1te
10. Redis
https://t.co/lYMCl0HxTY
11. System Design of Uber, WhatsApp, Bitly, etc.
https://t.co/WzqXuVawPW