SmartIPlace’s Post

Polling Vs Webhooks . . - Polling Polling involves repeatedly checking the external service or endpoint at fixed intervals to retrieve updated information. It’s like constantly asking, “Do you have something new for me?” even where there might not be any update. This approach is resource-intensive and inefficient. Also, you get updates only when you ask for it, thereby missing any real-time information. However, developers have more control over when and how the data is fetched. - Webhooks Webhooks are like having a built-in notification system. You don’t continuously ask for information. Instead you create an endpoint in your application server and provide it as a callback to the external service (such as a payment processor or a shipping vendor) Every time something interesting happens, the external service calls the endpoint and provides the information. This makes webhooks ideal for dealing with real-time updates because data is pushed to your application as soon as it’s available. So, when to use Polling or Webhook? Polling is a solid option when there is some infrastructural limitation that prevents the use of webhooks. Also, with webhooks there is a risk of missed notifications due to network issues, hence proper retry mechanisms are needed. Webhooks are recommended for applications that need instant data delivery. Also, webhooks are efficient in terms of resource utilization especially in high throughput environments. #systemdesign #webhooks #polling

System Design Blueprint: The Ultimate Guide. . . We've created a template to tackle various system design problems in interviews. Hope this checklist is useful to guide your discussions during the interview process. This briefly touches on the following discussion points: - Load Balancing - API Gateway - Communication Protocols - Content Delivery Network (CDN) - Database - Cache - Message Queue - Unique ID Generation - Scalability - Availability - Performance - Security - Fault Tolerance and Resilience - And more — #systemdesign #coding #interviewtips

🚀 RabbitMQ. Message Routing Patterns 🌠 Overview In the RabbitMQ we can specify a few types/patterns of message routing. All their flows are presented in the carousel. So, message routing patterns: 🔸 Direct exchange 🔸Topic Exchange 🔸Fanout Exchange 🔸Headers Exchange 🚀 Direct exchange 🔸Sends messages to queues based on a message routing key. 🔸The routing key is a message attribute added to the message header by the producer. 🔸A message is routed to the queue(s) with the binding key that exactly matches the routing key of the message. 🔸Useful for distinguishing messages published to the same exchange using a simple string identifier. 🚀Topic Exchange 🔸Messages are directed to queues based on wildcard matches between the routing key and the routing pattern. 🔸The routing pattern determines whether a message is routed to one or multiple queues based on a match with the message's routing key. 🔸The routing key must be a list of words, delimited by a period ”.” 🚀Fanout Exchange 🔸Copies and routes a received message to all queues that are bound to it. 🔸The provided keys will be ignored. 🔸This is useful when the same message needs to be sent to one or more queues with consumers who may process the message in different ways. 🚀Headers Exchange 🔸Messages are routed based on arguments containing headers and optional values. 🔸Header exchanges are similar to topic exchanges, but they route messages based on header values instead of routing keys. 🔸A message is considered a match if the value of the header equals the value specified upon binding. Source : Taras Iskiv #dotnet #rabbitmq #softwaredevelopment

Do you know all the components of a URL?    Uniform Resource Locator (URL) is a term familiar to most people, as it is used to locate resources on the internet. When you type a URL into a web browser's address bar, you are accessing a "resource", not just a webpage.    URLs comprise several components:    🔹The protocol or scheme, such as http, https, and ftp.  🔹The domain name and port, separated by a period (.)  🔹The path to the resource, separated by a slash (/)  🔹The parameters, which start with a question mark (?) and consist of key-value pairs, such as a=b&c=d.  🔹The fragment or anchor, indicated by a pound sign (#), which is used to bookmark a specific section of the resource. #url #webapplication #websitedevelopment #computerscience #server #client #address   Source : ByteByteGo

How to get started with system design. Read these articles (part 2): 10) Scaling Hashnode feed: https://lnkd.in/eaf4K_-4 9) Microservices at Netflix: https://lnkd.in/eZSM3CRB 8) Service discovery: https://lnkd.in/eCYYwQfU 7) Quotient filter: https://lnkd.in/e6nTXKDY 6) What happens when you type a URL: https://lnkd.in/eusuDn5z 5) Hinted handoff: https://lnkd.in/eM-CqK9f 4) Gossip protocol: https://lnkd.in/eBtqUVB6 3) Troubleshooting access to a website: https://lnkd.in/eER3Ci-X 2) Tips to pass system design interview: https://lnkd.in/eb-PS2nc 1) Code splitting: https://lnkd.in/edwCKJgQ What would you add to this list? Also I write a weekly newsletter to teach system design. Join 36,001+ like-minded software engineers: https://lnkd.in/ed4URjuY part 1: https://lnkd.in/euS_bPK9 --- If you liked this post. 🔔 Source: @Neo K. ♻ Repost to help others find it. 💾 Save this post for future reference. #coding #programming #softwaredevelopment #systemdesign

Event-driven architecture (EDA) is exciting until you deal with event versioning. The solution is a pattern, an Adapter, but with a twist. (Like 90% of the problems in Software Development) The Problem Your schema changed with some breaking changes. You have to update your Producer and 3 of your consumers. You may think you can have coordinated deployments. Good luck; you will be stuck in 27 meetings, and something will go wrong.  A Solution Create a new Topic; use this topic to publish the new schema versions. Update the producer to generate the new schema and point it to the new topic. Create an Adapter listening for messages in the New Topic and translating the message to the old format, then saving it into the old topic. Start migrating the consumers and pointing them to the New Topic. Once you finish the migration, you can decommission the Adapter and get rid of the old topic. Benefits The Adapter ensures backward compatibility, allowing existing consumers to continue functioning. This allows for a gradual migration of consumers to the new event schema. There is no big coordinated deployment with downtimes and no endless meetings. Testing will be more focused and controlled, as each consumer's transition can be tested independently.

🎙️ 𝐒𝐡𝐚𝐫𝐞 𝐲𝐨𝐮𝐫 𝐭𝐡𝐨𝐮𝐠𝐡𝐭𝘀 𝐚𝐛𝐨𝐮𝐭 𝐂𝐐𝐑𝐒 ? 𝐂𝐐𝐑𝐒 is a pattern initially articulated by Greg Young. Essentially, it revolves around the idea that updating information can employ a different model than reading information. While this separation can be advantageous in specific scenarios, it's important to be cautious, as, for the majority of systems, implementing CQRS introduces a potentially risky level of complexity. The main idea of CQRS is to introduce a split of the conceptual model into separate models for update and display. Many implementations involve the Mediator Pattern and database duplication in addition. Here's some 𝗕𝗲𝗻𝗲𝗳𝗶𝘁 𝗮𝗻𝗱 𝗰𝗼𝗻𝘀𝗶𝗱𝗲𝗿𝗮𝘁𝗶𝗼𝗻 🎯 𝗦𝗰𝗮𝗹𝗮𝗯𝗶𝗹𝗶𝘁𝘆 CQRS allows the read and writes operations to be scaled independently, since they are handled by separate models. This means that read-heavy applications can be scaled more easily without impacting the write operations, and vice versa. 🎯 𝗣𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲 By optimizing each model for its specific use case, CQRS can lead to significant performance improvements. The query model can be designed for fast data retrieval, while the Command model can be optimized for consistency and durability. 🎯 𝗦𝗲𝗽𝗮𝗿𝗮𝘁𝗶𝗼𝗻 𝗼𝗳 𝗖𝗼𝗻𝗰𝗲𝗿𝗻𝘀 CQRS provides a clear separation of concerns, making the codebase easier to understand and maintain. Developers can more easily reason about how changes to the codebase will affect the overall system. 🎯 𝗙𝗹𝗲𝘅𝗶𝗯𝗶𝗹𝗶𝘁𝘆 CQRS allows each model to evolve independently, since they are not tightly coupled. This means that changes to one model can be made without impacting the other model. ⚠️ 𝗜𝗻𝗰𝗿𝗲𝗮𝘀𝗲𝗱 𝗖𝗼𝗺𝗽𝗹𝗲𝘅𝗶𝘁𝘆 CQRS can increase the complexity of the application, since there are now two distinct models to maintain. This can lead to a steeper learning curve for developers and a more complex codebase overall. ⚠️ 𝗘𝘃𝗲𝗻𝘁𝘂𝗮𝗹 𝗖𝗼𝗻𝘀𝗶𝘀𝘁𝗲𝗻𝗰𝘆 Since the Command and Query models are separate, there may be a delay between when data is written and when it becomes available for reading. This delay is known as eventual consistency and must be accounted for in the application design. ⚠️ 𝗗𝗮𝘁𝗮 𝗗𝘂𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻 Since the Command and Query models are separate, there may be some duplication of data between them. This can lead to increased storage requirements and may require additional effort to keep the data in sync. #cqrs #design #pattern #programming #software #softwareengineering Source : Romain Ottonelli Dabadie

🚀 SQL Unveiled: Master the Database Universe with this Comprehensive Guide! 💻✨ 📌 This book covers complete SQL - Basic to Advanced concepts. #dataanlytics #dataanalysis #datascience #SQL #structuredquerylanguage #mindmap #community #SQLMindMap #DatabaseSkills #DataScience #TechMapping #LinkedInPost 📊💻

GitHub has 372M repositories. 24 repos you can't miss out as a software engineer: Interview preparation: 1. Tech Interview Handbook: https://lnkd.in/d2F5z4Af (by Yangshun Tay) 2. Guide to software engineering interviews: https://lnkd.in/dm2MbsgD (by Kevin Naughton) 3. Devops exercises: https://lnkd.in/dPCDT55k System design: 4. Big Tech engineering tech blogs: https://lnkd.in/dJaGjeES 5. System Design 101: https://lnkd.in/d5itZHgQ (by Alex Xu) 6. System design primer: https://lnkd.in/dkPScaCW (by Donne Martin) 7. Essential JS design patterns: https://lnkd.in/dWmBwK-i (by Addy Osmani) 8. Awesome scalability: https://lnkd.in/de4UZbiA 9. Awesome System Design Resources: https://lnkd.in/dU6wFXkn (by Ashish Pratap Singh) 10. Coding Challenges solutions: https://lnkd.in/dJV_8pgH (by John Crickett) LLM/AI: 11. Hands on LLM: https://lnkd.in/dww8GPdt (by Paul Iusztin) 12. Papers we love: https://lnkd.in/dkjsCq8z 13. Notes on AI for software engineers: https://lnkd.in/dANSnC4f 14. LLM 101 course: https://lnkd.in/dVKwvVUR (by Maxime Labonne) 15. ML paper of the week: https://lnkd.in/d66HxP52 (by Elvis S.) Complete roadmaps: 16. Path to senior engineer handbook: https://lnkd.in/dC3dQvy6 (by Jordan Cutler) 17. 100+ Resources to become a great Engineering leader: https://lnkd.in/dFwV2GMv (by Gregor Ojstersek) 18. DevOps roadmap in 2024: https://lnkd.in/ddE5DkDJ (by Dr Milan Milanović) 19. The Book of Secret Knowledge: https://lnkd.in/d69jrK4T 20. Free programming books: https://lnkd.in/d5JCRakw 21. The ultimate developer roadmap: https://lnkd.in/dsCJgDnS (by Kamran Ahmed) Frontend: 22. CSS for JS dev notes: https://lnkd.in/dCNavrNv (by Tiger Abrodi) 23. Javascript Questions: https://lnkd.in/dt_96xJZ (by Lydia Hallie) 24. Typescript advanced patterns workshop: https://lnkd.in/deTBDhCb (by Matt Pocock) What are your favorite repos? #systemdesign #softwareengineering #programming Source : Alexandre Zajac