Hey everyone! Many of you might have run into an annoying issue recently: our Android app (even the latest version) won't open — it just shows a white screen and closes immediately. It breaks our hearts to share this, but it's caused by security update in Android OS. Recent changes in Android/Google policies prevent us from supporting the app. We are very sorry to share this sad news, but as of October 29, 2026, our Android app is no longer officially supported. We are truly heartbroken that things turned out this way. 🥲 To continue to have access to Z-Library, use the website, Windows Desktop app or Personal TG bots With lots of love and care, Your Z-Library Team🫂
97
199
3,090
117,906
Payments system design round. How many of these can you explain clearly: Idempotency keys Double-entry ledger Authorisation vs capture Refunds vs reversals Webhook retries and dedup Reconciliation Settlement cycles Chargebacks Exactly-once vs effectively-once The outbox pattern Holding money in a "pending" state 8 or more and you can walk into a fintech company's loop and do a decent job. Almost every backend engineer in India ends up working with payments systems at some point. Learn this list before that day comes.
12
21
219
8,403
pelel retweeted
Full Stack Web Development: A Comprehensive, Hands-On Guide to Building Modern Websites and Applications (IBPA Gold Award Winner) (Rheinwerk Computing) 📕 Get Now: link.amazon/B08R9jzNi
1
5
84
pelel retweeted
New 📚 Release! Docker for React.js developers by Kristiyan Velkov #books #docker #programming #coding #softwareengineering The 'It Works on My Machine' Excuse Ends Today. Understand Docker. Ship with Confidence. Own Production. This book is written for front-end developers who are tired of using Docker without truly understanding it. Instead of abstract theory or backend-centric explanations, it teaches Docker in a clear, practical way—aligned with how front-end engineers think and how real front-end applications are built and shipped. You’ll work with a real GitHub repository, follow real production workflows, and learn how to build, run, and deploy a React.js application using Docker—ending with a full deployment to Amazon EC2. Every step is explained with purpose, so you understand not just what to do, but why it works. By the end of the book, Docker will no longer feel like a black box. You’ll know how to create reliable builds, debug problems with confidence, and take ownership of your production environment as a front-end developer. If you want to stop guessing, stop copying commands, and finally ship front-end applications with confidence—this book is for you. Find it on Leanpub!
1
1
2
73
Backend engineers, you need to get this book. Mind blowing! 🔥 🚀 Haven’t seen any other resource that goes deep into Database indexes! sqlfordevs.com/ebooks/indexi…
7
72
381
45,521
pelel retweeted
🗄️ Database Internals: A Deep Dive into How Distributed Data Systems Work ✍️ Alex Petrov 📖 Get the book: amzn.to/4htmczk Want to understand what really happens inside a modern database? 🔍⚙️ Database Internals takes you beneath the APIs and abstractions to explore the storage engines, distributed systems, and internal mechanisms that make modern databases work. 📚 Inside, you'll explore: • Database storage classification & taxonomy • B-Tree storage engines and their design • Immutable Log-Structured storage engines • Storage-engine trade-offs and use cases • Database file organization • Page Cache and Buffer Pool • Write-Ahead Logs (WAL) • How nodes and processes communicate in distributed systems • Distributed communication patterns • Database cluster architecture • Consistency models used by modern databases • How distributed storage systems achieve consistency 🧠 Drawing on material from books, research papers, technical articles, and open-source database source code, the book focuses on the subsystems that determine how data is stored, organized, and distributed. 🎯 Perfect for: Backend developers, software engineers, database engineers, distributed-systems learners, architects, and anyone who wants to understand databases beyond surface-level usage. 💡 Don't just learn how to use databases. Understand the machinery underneath them. #DatabaseInternals #Databases #DistributedSystems #DatabaseEngineering #StorageEngines #BackendDevelopment #SoftwareEngineering #SystemDesign #DataEngineering #BTree #DistributedDatabases #TechBooks
4
9
263
The more I read this book by @RaVitillo, the more I’m happy with the purchase. A must-read book for every backend dev
10
78
677
10 rules of senior Node.js, from 157 production tips: They're the last page of The Conscious Node, the book I released in July. I never posted about it here, so this thread fixes that. 🧵👇
4
2
18
559
Get Programming with Node.js - Final PDF eBook Edition available now! pBook available Feb 22; ePub + Kindle available Mar 1 manning.com/books/get-progra… @TheWexler #nodejs #programming -- Check out the #liveBook: livebook.manning.com/#!/book…
2
3
Serverless Applications with Node.js is IN PRINT now! ePub + Kindle available March 1 manning.com/books/serverless… @slobodan_ @simalexan #serverless #nodejs #ClaudiaJS #AWSlambda #app -- Check out the #liveBook: livebook.manning.com/#!/book…
14
26
This is a great tip on how to effectively learn from the exercises when reading programming textbooks. From @TheWexler's new intro to Node book.
5
9
pelel retweeted
If you're moving from frontend to Node.js backend… books will take you further. Because backend isn’t about learning more syntax. It’s about understanding systems. These are worth your time: 📚 Node.js Design Patterns Where you stop thinking in code and start thinking in architecture, async flows, and real tradeoffs amazon.com/Node-js-Design-Pa… 🛠️ The Node Craftsman Book Hands-on, project-based Great for building backend intuition through real systems amazon.com/Manuel-Kiessling-… 🌐 Design and Build Great Web APIs This is the shift most frontend devs need thinking in APIs, contracts, and long-term evolution amazon.com/Design-Build-Grea… And the real goal isn’t finishing a book. It’s developing the ability to understand: • why something is slow • what happens under load • how systems fail • how to reason about tradeoffs That’s the real transition.
2
7
377
5 awesome books to get you started with Node.js 🔥 🔸 Node.js Design Patterns 🔸 Web Development with Node and Express 🔸 Practical Node.js 🔸 Mastering Node.js. 🔸 The Node Beginner Book
6
107
553
pelel retweeted
I find an amazing book called: Mixu's Node book Anyone that wants to have a deep grasp of Node.js will benefit from mixu's book. and it's free. Link - book.mixu.net/node
9
92
393
pelel retweeted
5 messaging patterns every system design interview candidate should know: 1. Point-to-point One message goes to one worker. 2.Publish/subscribe Subscribers receive messages for the topics they follow. 3. Fan-out One event is copied to multiple queues or consumers. 4. Request-reply A client sends a request and receives a response. 5. Event streaming Events are stored so consumers can process or replay them. Each pattern solves a different communication problem. Know when to use each one for your HLD interviews.
2
12
82
1,831
Top 10 practical resources to learn DevOps (for working devs): 1) Google SRE Book + Workbook (free) Ops principles, error budgets, and realistic incident math. 2) Kubernetes docs + kubectl exercises Stop at Deployments, Services, Ingress, HPA, PDB. Ship one app, break it, fix it. 3) Terraform docs + a real module repo Write modules for VPC/network + EKS/GKE + RDS. Learn state, drift, imports. 4) AWS Well-Architected Framework Good for tradeoffs: cost vs reliability vs operability. Use it as a design checklist. 5) Linux Upskill Challenge (free) If you can’t debug disk, memory, perms, and systemd, you can’t debug prod. 6) The Phoenix Project (book) Not technical, but it explains why pipelines and WIP limits matter in real orgs. 7) GitHub Actions or GitLab CI docs Build a pipeline with: test, build, SBOM, scan, deploy, rollback. Make it fast (<10 min). 8) Prometheus + Alertmanager docs Instrument one service. Write alerts that page on symptoms, not CPU spikes. 9) Incident writeups (GitHub: Shopify, Cloudflare, GitHub, etc.) Read for failure modes: bad deploys, thundering herds, expired certs, quota limits. 10) Practice project: one microservice, real ops Run it on k8s, add tracing/logs/metrics, blue-green deploys, chaos test (kill pods), restore from backup in <30 min
1
3
18
1,081
pelel retweeted
The move to 64-bit went fine (mostly). The Book of Debugging coming to shelves soon! nostarch.com/book-of-debuggi…
2
6
69
2,193
pelel retweeted
I Read Clean Code: A Handbook of Agile Software Craftsmanship, 2nd Edition and It’s Awesome dlvr.​it/TW54dl
2
8
1,403
pelel retweeted
I Read 30+ Books on Software Architecture: Here Are My Top 7 Recommendations buff.ly/3tRvrI2
6
20
2,018