InterviewReady

The series is live! Episode #1: What is System Design - https://lnkd.in/gfBY4xrj Episode #2: Hosting an Ecommerce Website -https://lnkd.in/gUxfiugz Episode #3: Serving Webpages with CDNs - https://lnkd.in/gnu498Dy The upcoming episodes will be released weekly over the next six weeks, every Saturday at 7 PM IST. Release Schedule: https://lnkd.in/g_nauCXE We would love to know your thoughts on the series. #systemdesign #series

The system design videos at InterviewReady are revamped, starting with the fundamentals section. The overarching topic: Scaling an e-commerce website from 1 to 1,000,000 users. You will see how a simple app evolves into a complex distributed system as its requirements change and users scale. Here is the video release schedule: Episode #1, #2, #3: 9 November Episode #4: 16 November Episode #5: 23 November Episode #6: 30 November Episode #7: 7 December Episode #8: 14 December Episode #9, #10: 21 December All episodes launch at 7 PM IST. We will notify all registered InterviewReady users through email and website notifications. Thank you for your continued support. Cheers 😁🤞 #SystemDesign #Launch #InterviewReady

Story time. A frontend engineer was strangling a back-end engineer. When asked why- "He changed the client version from 1.1.3 to 1.1.4." the FE explained. "So?" "So? SO?! He made a breaking change on the patch update!! The company stock is down 15% and the CEO wants to know my current location!" This is a good time to talk about API versioning. Versioning has the following format: MAJOR.MINOR.PATCH (1.1.3) 1. MAJOR: May break expectations (not backwards compatible). 2. MINOR: Adds some new features without breaking anything (safe to move). 3. PATCH: No new features, just bug fixes and improvements (very safe). How does it work in real life? - Let’s say your current version is 2.5.3. - You fix a bug → next version is 2.5.4. - You add a cool new feature → next version is 2.6.0. - You change a core part of the software that breaks existing functionality → next version is 3.0.0. If you are an engineer, you would be wise to follow this system. It let's dependent systems update their libraries safely. No engineers were harmed in the telling of this story. ----------------- I talk about API contracts here: https://lnkd.in/dZ8nBuqq #API #Versioning #SystemDesign

How do you instantly increase trust in a customer's eyes? You host a website with "https". It tells the customer that the website is registered and secure. The technology is called SSH. It is used to send messages securely over any network. Here is how the magic happens: 1. Connection setup (TCP connection of port 22) 2. Version negotiation (SSH1 or SSH2) 3. Algorithm negotiation (For key exchange) 4. Key exchange 5. User Authentication (Using public key) 6. Session setup (to send encrypted data) TL;DR- SSH uses algorithms, key exchange, and authentication methods to send messages securely. Cheers! You can learn more about networks and networking in computers here: https://lnkd.in/gK6G-EjA #systemdesign #SSH

If you look at the definition that Google gives for programming, they call it coding across time. So if you write a piece of code, it's not just that you want to satisfy all the requirements of the client right now, but you also want to help future engineers satisfy future requirements. [1] Readability: It is emphasized that unreadable code increases engineering costs and can negatively impact an organization. [2] Extensibility: The ability to add new features without significant modifications to existing code reflects positively on team culture and the individual engineer. [3] Correctness: Bugs that go unnoticed in production can incur high costs for organizations. Code reliability is likened to a fundamental responsibility across various engineering fields. 10 years down the line, you may be an engineering manager, but if your code still exists and people are still working with it, there's a very strong reputation that you build. Some more good practices are described in the infographic below! How many good practices do you follow? ---- Check out more on why you need good coding practices here: https://lnkd.in/gK8uQ4Tp #coding #systemdesign

Wishing you a Diwali filled with light, laughter, and lasting memories. May this festival of lights bring you and your loved ones joy, success, and prosperity. Happy Diwali! 🪔🌟 #diwali #india #festival

LAST DAY TO GRAB 70% OFF! 🎉 👻 Our system design course is designed to help you shine in your system design interviews and be interview-ready. Your success is our treat—let’s get started! Visit us at https://interviewready.io/ to grab our treat this Halloween. We hope it was a good treat :P #sale #halloween #systemdesign

👻 Spooktacular alert! 👻 This Halloween, treat yourself to 70% OFF on our system design courses. Whether you’re prepping for MAANG interviews or levelling up your skills, this offer is for YOU! Don’t let this opportunity disappear! Head to https://interviewready.io/ #sale #halloween #systemdesign

Data breaches cost billions of dollars every year. So how do engineers secure their systems? It's usually a three point checklist: 1. Authenticating users 2. Restricting access to different parts of the system 3. Encrypting data transmissions and maintaining data integrity These simple steps are usually enough. Most hackers look for easy prey and move on after seeing a system that follows security best practices. As they say, appearances are an important part of security. Unauthorized access, data breaches, and system compromises while allowing legitimate users to interact with the system efficiently. To learn more about security in distributed systems, watch the video: https://lnkd.in/gXAgEZGV The infographic below covers some of the most commonly utilized techniques when it comes to managing APIs in distributed systems. Save it for the future! #API #security #distributedsytems #oauth

Facebook Memcached can manage billions of requests per second. Here are some of its technical highlights: 1.⁠ ⁠Optimizing for read queries (99% of their cache queries are read) 2.⁠ ⁠Improving their cache hit rates (Through memory slabs and Segmented LRU) 3.⁠ ⁠Data consistency throughout MySQL (through Change Data Capture) 4.⁠ ⁠Rate limiting using sliding windows It's a massive distributed key-value store tailored to Facebook's needs. Watch the white-paper explanation series here: https://lnkd.in/db7CQkFE Our month-end sale is LIVE! Get 70% off on our System Design course 😎 #facebook #memcached #meta #requests