 that Michael Brown namespace lockdown. We're good. All right, the most important piece of infrastructure is hosts. So a big part of React is creating this ring and need a few hosts to create that ring. And that ring is simply just made up of partitions. So you break up that ring into partitions and then React spreads those partitions evenly amongst the hosts. So for instance, I can't cover it a little bit. But if you have 128 partitions and eight hosts, you'll end up with 16 partitions per host. All right, so now we have a ring. We have partitions. What's happening with your data behind the scenes? So by default, the default value is to replicate each piece of data that we store three times. And that ensures the resiliency throughout the cluster. So if Brad's walking by our server rack, stills a big gulp on one of our React hosts. It goes down. The cluster still functions. And it's with no manual intervention. You can access all this data through HTTP or Google Protocol Buffers, which are pretty cool. Another huge feature that we really enjoy and use a lot of is the Post Commit Hook, which allows you to integrate a function into the React database. And whenever you store a record on a particular bucket, you can fire that function. So how we use that is we use the Post Commit Hook to send data to the mirror, which is our whitelisting application, and then the Kafka. All right, so you're still not impressed? You want a little bit more. All right, so React is multi-cluster, as Niaja mentioned. Going in between and moving data from different locations is not a problem. So think of your data as lettuce, iceberg lettuce. So there's two ways that React manages this. One is real-time replication. The other is full sync replication. So real-time replication is the process of just moving new changes in data to a new cluster. This is really nice. This is how you ensure data is synchronous across all the clusters. The other type is full sync replication. This is the historical data that you want to transfer. And we initially, when we first set this up, we used it as a way to provide disaster recovery scenarios. So we had a slave cluster that was constantly getting rights. And so if anything should happen, we're safe. Great high availability. The other great thing about full sync replication is it can go multiple ways. So you can have a data center in California, Virginia, and Europe all sharing, all actively writing to each other. And data is here. So are we in sync? That's actually 98 degrees. But and I'm just here to say, in React, we trust. Oh.