Sayantan D.’s Post

Getting a random follower in Github is the best feeling ever. 😎 Now if only there was a way to send messages on Github... 👀 --- For more laughter & knowledge follow 👉 https://lnkd.in/eiSq-cnW #javascript #memes #developer #react #programmers

The magic behind your React App! . . At the end of the day, your browser just understands the same old, “Html, Css, Javascript” Webpack + Babel does all the heavy lifting for you.

Package-lock.json is a crucial file in the world of JavaScript and Node.js development. It serves as a manifestation of your project's dependency tree, providing a detailed record of all the packages and their versions that your project relies on. Lets try to understand its features: Dependency Tree Snapshot: When you use npm to install packages or update your project's dependencies, npm generates a package-lock.json file. This file essentially captures a snapshot of your project's dependency tree at that moment. It lists all the packages your project uses and the specific versions of each package. Reproducibility: The main purpose of package-lock.json is to ensure that anyone else working on your project can reproduce the exact same dependency tree on their machine. This is crucial for maintaining consistency across different environments and for collaborative development. Time-Traveling: Package-lock.json also acts like a time machine for your project's dependencies. You can revert to previous states of your project by referring to older versions of this file. It allows you to roll back to a known and working state without the need to commit your entire node_modules folder. Version Control: It's meant to be committed to your version control system (e.g., Git). By doing so, your team ensures that everyone is working with the same set of dependencies. This consistency is essential for continuous integration and deployment processes. Performance Optimization: Package-lock.json optimizes the installation process. It helps npm skip redundant metadata resolutions for packages that have already been installed, saving time and bandwidth. Readable Diffs: It makes changes in your project's dependencies more visible. When you update or modify your package.json, the changes in package-lock.json can be easily reviewed in source control, making it easier to track updates and potential issues. Compatibility: Starting from npm version 7, package-lock.json files contain sufficient information to understand the entire package tree, reducing the need to inspect package.json files. This improves performance and compatibility. Hidden Lockfiles: npm also maintains a "hidden" lockfile inside the node_modules/.package-lock.json folder to avoid redundant processing of dependencies. This hidden lockfile speeds up installations by providing an already processed tree of dependencies. In summary, package-lock.json is a critical file for managing and maintaining your project's dependencies. It ensures consistency, reproducibility, and performance while facilitating collaboration among developers working on the same project. It's a key tool for building robust and reliable JavaScript applications. #webdevelopment #npm

How is data transmitted between applications? . . The diagram below shows how a server sends data to another server. Assume a chat application running in the user space sends out a chat message. The message is sent to the send buffer in the kernel space. The data then goes through the network stack and is wrapped with a TCP header, an IP header, and a MAC header. The data also goes through qdisc (Queueing Disciplines) for flow control. Then the data is sent to the NIC (Network Interface Card) via a ring buffer. The data is sent to the internet via NIC. After many hops among routers and switches, the data arrives at the NIC of the receiving server. The NIC of the receiving server puts the data in the ring buffer and sends a hard interrupt to the CPU. The CPU sends a soft interrupt so that ksoftirqd receives data from the ring buffer. Then the data is unwrapped through the data link layer, network layer and transport layer. Eventually, the data (chat message) is copied to the user space and reaches the chat application on the receiving side. Over to you: What happens when the ring buffer is full? Will it lose packets? – Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages): https://bit.ly/3KCnWXq #systemdesign #coding #interviewtips .

Do you believe that Google, Meta, Uber, Twitter, and Airbnb put almost all of their code in one repository? This practice is called a monorepo. Monorepo vs. Microrepo. Which is the best? Why do different companies choose different options? Monorepo isn't new; Linux and Windows were both created using Monorepo. To improve scalability and build speed, Google developed its internal dedicated toolchain to scale it faster and strict coding quality standards to keep it consistent. Amazon and Netflix are major ambassadors of the Microservice philosophy. This approach naturally separates the service code into separate repositories. It scales faster but can lead to governance pain points later on. Within Monorepo, each service is a folder, and every folder has a BUILD config and OWNERS permission control. Every service member is responsible for their own folder. On the other hand, in Microrepo, each service is responsible for its repository, with the build config and permissions typically set for the entire repository. In Monorepo, dependencies are shared across the entire codebase regardless of your business, so when there's a version upgrade, every codebase upgrades their version. In Microrepo, dependencies are controlled within each repository. Businesses choose when to upgrade their versions based on their own schedules. Monorepo has a standard for check-ins. Google's code review process is famously known for setting a high bar, ensuring a coherent quality standard for Monorepo, regardless of the business. Microrepo can either set their own standard or adopt a shared standard by incorporating best practices. It can scale faster for business, but the code quality might be a bit different. Google engineers built Bazel, and Meta built Buck. There are other open-source tools available, including Nix, Lerna, and others. Over the years, Microrepo has had more supported tools, including Maven and Gradle for Java, NPM for NodeJS, and CMake for C/C++, among others. Over to you: Which option do you think is better? Which code repository strategy does your company use? -- Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages): https://bit.ly/3KCnWXq #systemdesign #coding #interviewtips .

When it comes to exchanging data, there are different methods to choose from: #Polling: Regularly checking for updates. Examples: News websites refreshing content, social media apps loading new posts. #Webhooks: Notifications when data is ready. Examples: PayPal notifying payments, GitHub alerting code pushes. Bonus: Exploring More Communication Options in the Web World: #LongPolling: Server holds responses. Examples: Real-time chat apps, online games with opponent updates. Server-Sent Events (#SSE): One-way stream of updates. Examples: Stock market apps, live weather alerts. #WebSocket: Real-time two-way channel. Examples: Google Docs collaboration, multiplayer online games. #MessageQueues: Asynchronous messaging. Examples: E-commerce inventory, ride-hailing assignments. #PushNotifications: Direct updates. Examples: Messaging apps, breaking news alerts. if you like this quick information, connect or follow Ankit Pangasa Image Credits: Brij kishore Pandey