Also, 1 GBps == 8 Gbps

That is awesome!

@@ByteMonk where are you located?

Any startup experience? Funding, technical oversight?

Web servers are a common platform for hosting APIs, but there are other options available. For example, APIs can be hosted in cloud platforms, such as AWS or Microsoft Azure.

@@ByteMonk this means API gateway will forward request to web server (Apache running on ec2). Which will forward request to microservice running on Lambda?

@@mz7640 I think you would typically have the API gateway forward the request to the microservice directly. Each microservice will be running an HTTP server to handle incoming HTTP requests.

@@mz7640 your assumptions are as per the monolithic architecture but Instagram example here is built using Micro Service Architecture which does not follow traditional webserver-Appserver interaction approach.

Every expert was once a beginner. Knowledge is accessible to anyone willing to learn and grow, so don't underestimate your potential - with dedication and effort, We all have the ability to be leaders of our own journey :)

​@@ByteMonkdamn thanks for this❤

Tbh, a lot of tech people treat things as far more complicated than they need to be and other things as far simpler than they are. This video is detailed, but it is also high level in some places. He is showing you a method of how things COULD be implemented. It’s a jumping off point, an inspiration.

The actual stuff here is simple, but its not easy to complete. I think thats where the confusion comes. Simple does not equal easy. Ex. Push ups are simple, but doing 200 push ups is hard. Take it a step at a time and as you go, youll realize you know more than you thought

@@ThatsJoshTyler Thankyou for your brief insight and pov on the subject matter being discussed here. I gotcha

Excellent observation. This is going to be a long answer and a good conversation topic during the interview. While real-time loading offers a dynamic and engaging user experience, it's important to carefully consider the trade-offs and design choices to ensure optimal performance and scalability. Advantages of Real-time Loading: Dynamic Content: Real-time loading allows users to see the latest updates and activities as they occur, creating a more engaging and interactive experience. Instant Feedback: Users receive immediate feedback on their actions, such as likes and comments, enhancing their engagement with the platform. User Engagement: Real-time feeds can increase user engagement and retention, as users are more likely to stay active and interact with the app. Challenges and Bottlenecks: Scalability: Real-time systems need to handle a high volume of concurrent users and activities, which can strain the infrastructure and impact performance. Latency: Ensuring low-latency delivery of real-time updates can be challenging, especially as the user base grows. Network Traffic: Frequent updates can generate significant network traffic, affecting the app's responsiveness and consuming bandwidth. Mitigating Challenges: Caching: Implement caching mechanisms to reduce the load on the backend and minimize redundant requests. Distributed Architecture: Employ a distributed architecture to distribute the load and scale horizontally as the user base grows. Batch Processing: Aggregate and process updates in batches to minimize the number of real-time requests. Content Prioritization: Prioritize important updates and ensure that less critical updates are delivered in a less resource-intensive manner. Ultimately, the decision to implement real-time loading depends on the specific requirements of your application, the user expectations, and the technical capabilities of your infrastructure. It's essential to conduct thorough performance testing, monitor system health, and continuously optimize the real-time feed delivery to strike the right balance between engagement and performance

This looks like a chat GPT reply - I’m not saying it’s wrong to use GPT to reply but it’s also less genuine than hearing the authors original thoughts.

@@frankcallahan3631 In our experience chatGPT and other tools hallucinate a lot, and produces too much information. However, when needed, we prompt them with our thoughts to get feedback and use some of the text it generates, but always proof read and refine them. Thanks for your feedback, will strive to be as genuine and raw as possible in future.

@@ByteMonk I loved the video by the way.

And I subscribed

Thanks for the feedback, I try to balance speed for each video. For this video, can you also check out playback speed KZfaq provides and try playing it at 0.75%

It’s fine for me.

Yeah, these videos are made from interview perspective. I imagine Implementing a blocking system will involve handling database operations and building the necessary API endpoints to enable users to block and unblock others.

@@ByteMonk I think block is more complicated than just blocking and unblocking.. Suppose you have blocked an user and that user commented in one of your friends post. How do you prepare custom post metadata that doesn’t include the blocked user activities. ?

Great point, this could be a follow up question/discussion during an interview or a separate system design question altogether. To prepare custom post metadata that doesn't include the activities of blocked users, you can follow these steps: 1. Retrieve Post Metadata: Fetch the metadata of the post that you want to display, including the comments and activities associated with it. 2. Filter Blocked Users: Iterate through the comments or activities and identify any users who have been blocked by the viewer. Check against the blocked user list to determine if the comment or activity was generated by a blocked user. 3. Exclude Blocked User Activities: Remove any comments or activities generated by blocked users from the post metadata. This can be done by either excluding them from the response or flagging them as blocked. 4. Prepare Custom Metadata: Create a modified version of the post metadata that excludes the activities of blocked users. This may involve creating a new object or modifying the existing one to remove the blocked user information. 5. Return Custom Metadata: Return the custom post metadata to the client application for display. Ensure that the modified metadata only contains the activities of non-blocked users, providing a customized view that respects the blocking preferences of the viewer. By filtering out the activities of blocked users during the preparation of post metadata, you can create a custom view that doesn't include any content or actions from blocked users. This ensures that the viewer's experience is tailored to their preferences, providing a more personalized and relevant feed without unwanted interactions from blocked individuals.

@@ByteMonkso helpful! Thank you!