正在加载视频...

视频加载失败

Consistent Hashing Explained Simply Let's break down consistent hashing in a way that's easy to get. It's a handy technique for distributing data evenly across servers. And if you're more of a visual learner, don't miss the attached video which brings this concept to life. Here's how it works:...

36,787 次观看 • 2 年前 •via X (Twitter)

4 条评论

Riccardo Causo 的头像
Riccardo Causo2 年前

the mother of all animations! 👍

Nirmalya Sengupta 的头像
Nirmalya Sengupta2 年前

The animation makes this even more retention-ready! Well done! 👍👍👍

Simform 的头像
Simform2 年前

I would add that consistent hashing is a fundamental concept in distributed systems and is used in many real-world applications. For instance, it’s used in load balancing, where requests are distributed across multiple servers, and in data sharding, where data is partitioned across multiple databases.

Manoj Khangaonkar 的头像
Manoj Khangaonkar2 年前

"Consistent" is a poor name choice for this technique.

相关视频

React tip: "use client" misconceptions (2/5) 🚫 "You cannot nest Server Components inside Client Components because "use client" turns everything into Client Components." ✅ We can pass the rendered result of Server Components to Client Components as props. Simple example: (Server Component) (Client Component) (Server Component) is designed for the client. It needs to instantly open and close when clicked. is designed for the server. It uses packages that don't work in the browser and needs to fetch data close to where it's stored without exposing credentials. So, how can we nest a component that uses server APIs inside a component that uses client APIs... without using `import`? React props to the rescue! --- (0:00) 1-4: Reminder: Importing code forms a module dependency graph. Adding dependencies to a server or client bundle. (0:23) 5-6: Reminder: Using components eventually forms a rendered component tree. (0:37) 9: Oh no! We get an error when trying to `import` a client API (useState) into a server module. (0:44) 10: We know the trick by now: Add "use client" to mark `2.js` as a client entry point. This moves the module to the client bundle and allows us to use client APIs like `useState.` (0:51) 11: But we get a new error! "use client" moved all imported dependencies into the client bundle, including our ORM package, which doesn't work in the browser. (0:59) 13: Let's refactor without changing our rendered component hierarchy. First, we move the `Cart` import to the parent file that imports `Modal`. This moves `Cart` outside the "use client" boundary and consequently the client bundle. (1:11) 15: Then, we pass down the rendered result of `Cart` as a prop to `Modal`. This allows `Cart` to be entirely rendered on the server as a Server Component before being passed down. `Modal` has no knowledge of what the `cart` prop is. Its only responsibility is placing whatever it receives into the `{cart}` slot. (1:15) 16: Finally, it's common to use the special `children` prop for a component's primary content. The key insight is that we were able to use props to retain our desired component hierarchy even though we changed our module dependency graph.

Delba

43,989 次观看 • 2 年前

Which one is our priority for securing a digital future for Zimbabwe? The Honourable Speaker's position while providing a clear, logical, and data-informed counter-argument we appreciate his efforts and submission. Let us have a conversation on our priorities in the current Zimbabwean context which we presented yesterday: This is a critical national conversation on our digital future. The proposition of a Google data centre is undoubtedly appealing. Building a centre of Technological Excellence that houses multiple Tech companies and a Start-up Ecosystem is also prudent, though we are calling it a Technology Park. However, I was of the following view which I am willing to be criticised and guided on. The strategic prioritisation of a national ICT Park ecosystem currently is the foundational path to sustainable, sovereign growth and capacity for Zimbabwe. We are reaching out to every province through the Digital Centres, Innovation Hubs at Universities and Colleges. Infrastructure which we need to capacitate better. This is a decentralised system utilising and expanding the infrastructure we have. The central question is not if we want major players like Google; that is not questionable, but when, how and on what terms. Why are we building our own foundation, house, techno park and mini ICT Parks in the provinces and districts? We absolutely need at least a one hyperscale data centre, but centralisation in the current and future environment can be restrictive. This was our plan: 1.The Foundation Before the Skyscraper: Capacity and Traffic We need to increase our national data volumes and internet traffic . Our urgent priority should be upgrading our national backbone, specifically the Optical Fibre on Power Transmission Lines (e.g., Powertel's network from Insukamini to Johannesburg), to peer efficiently with global giants. This builds the foundational "digital highway" we manage. 2.Generating Traffic Through Digitalization A data centre is a response to demand, not a creator of it. We must first drive digitalization aggressively through digital payments, process automation, and e-governance to generate the significant local traffic that would make a data centre viable. Furthermore, we must incorporate Edge Computing strategies to process data closer to the source, a more efficient model for our current needs and in compliance to our Cyber and Data Protection Act which we can amend if need be. Being a regional internet and cybersecurity hub is crucial as the Speaker alluded to me mentioning it to SADC Parliamentary Forum, this is the ultimate goal. 3.PPPs are key to lessen the burden to the fiscus and we are ready to accommodate organisations willing to assist government.(Cont)

Hon Tatenda.A. Mavetera

490,198 次观看 • 7 个月前