1:1 calls, interview prep & career guidance with Sandeep Pal.
Free online compilers with a path into tools and coding practice.
Web, mobile, ecommerce & growth — end-to-end for your business.
Public developer portfolio with certs & learning badges.
Formatters, converters, SEO checkers & more — no install.
Insights, tutorials, and career tips from the engineering community
Imagine you're using Uber. You request a ride. Within seconds, your request reaches an available driver near you. But here's the interesting question. How did Uber know which driver service to contact?
Imagine you're scrolling through your Instagram feed. You like a post. Your friend refreshes their phone immediately. For a few seconds... they still don't see your like. Did the system lose your data? No.
Imagine you're transferring ₹10,000 from your bank account to your friend's account. The process looks simple. Your account balance decreases. Your friend's balance increases. Now imagine something goes wrong halfway through. Your account is debited. But your friend's account is never credited because the database crashed. The money disappears.
Imagine you're building the next Amazon. Your application needs to store: Customer information Product catalog Orders Payments Reviews Shopping carts One of the first questions you'll face is: Should I use SQL or NoSQL?
Imagine you're using Amazon during the Big Billion Sale. You search for: "iPhone 16 Pro" Within milliseconds, thousands of matching products appear. Now imagine Amazon had to scan every product in its database before showing the results. Instead of milliseconds... It could take minutes. Imagine the experience for millions of users.
System Design Series — Part 32 Imagine you're using Amazon during a big sale. You click "Buy Now." Behind the scenes, your request travels through multiple services: Order Service Payment Service Inventory Service Notification Service Shipping Service
System Design Series — Part 31 Imagine you've built a successful e-commerce application. Everything works perfectly. One day, your API suddenly receives 2 million requests in just a few minutes. Some requests come from real users.
System Design Series — Part 30 Imagine you log in to your internet banking application. You enter your username and password only once. After logging in, you can: Check your account balance Transfer money Download statements Pay bills You never enter your password again until you log out. But here's the question:
How does the server know it's still you? Does the server remember every logged-in user? Not usually. Instead, most modern applications use something called a JWT (JSON Web Token). JWT is one of the most widely used authentication mechanisms in modern web applications, mobile apps, APIs, and microservices.
care@toolliyo.com
Install Toolliyo like an app Free
Home-screen access to tutorials, coding practice & career tools — no app store needed.
On iPhone/iPad: tap Share then Add to Home Screen.