Yeah, I mean, I did have one more question too, right? So you talked about how you, I believe you said kind of the core of the way things restored similar to MongoDB, right? So you have collections as document database, but you're calling tables, right? What is actually the nomenclature for different things like you? Is it similar to SQL where you have tables, then you have rows of records? Is it the same kind of style you have?

So in SreelDB, you have tables. So similar to Postgres tables, similar to MongoDB collections effectively, though, instead of rows. So every single document can be schemalous, which means every single document could have different data. You can define a schema for your database or for your tables, and in which case, each record has to look or have the same fields. But under the hood, those records are still stored in a document way. Each record stores the document, the field names along with each field. So I guess that's another negative to the database when you're comparing it to a true relational database. The relational database will store the column types and then just store the values with those columns in SreelDB as with other document databases, you're storing the fields along with that. That gives you the flexibility to have nested arrays, nested objects, which can or don't have to be assigned a schema, but it also gives you that limitation of each, the size of your data will be slightly larger because

you're storing more information with each record. Okay. Yeah, I don't think I have any more questions on my side. There's something else that you think everybody should know about SreelDB before we sign off.

Hey, look, if you haven't tried it, give it a try. I mean, we believe this can be the defacto database in the world. It simplified our lives and made it a lot easier for us to build things. And you haven't tried, like I said, give it a go. We think you'll like it.

And with that, thank you guys for coming on. Thank you. Thank

you.