NoSQL

I've been asked to pick up MongoDB, of which I know less than nothing.

How have other DBAs found the transition? Not specific to MongoDB, but generally across database administrators of all time, what you find is that whenever the company decides to use a new persistence layer, and I'm using the term persistence layer because sometimes it's a database, sometimes it's a NoSQL thing, sometimes it's like a service that's managed by a cloud.

If it's a place where data lives, they tend to bring it to the database administrator and go, here, You manage data,

manage

systems

and how to manage data in a large-scale distributed systems when there are peer-to-peer and grid computing environments and so on.

So this was a precursor to some of the NoSQLs of the world.

For example, something like what Cassandra is doing today, right? That's what my doctoral thesis did at that time.

Of course, not at that scale and all that, but obviously it's a research prototype.

Yes.

That sounds like the NoSQL equivalent of an SQL injection attack.

If I'm a threat actor, that's just leaving the front door wide open with a neon sign pointing to the vault.

I'm just going to pass malicious JavaScript right into that query string and hijack the server.

That kind of thought experiment forces you to weigh performance against security tradeoffs, which is the daily reality of modern systems engineering.

And we will leave you with a final provocative thought.

We started this deep dive by comparing relational databases to rigid concrete skyscrapers and NoSQL to flexible Tupperware.

The classic dilemma.

There are dozens of options today, so picking the best one can be a challenge.

Our default vector DB is ChromaDB, but there are other ways to store data, such as RDBMS, NoSQL, and NewSQL.

You can even add pgVector to PostgreSQL and get yourself a vector store.

A vector store typically consists of three layers, indexing, storage, and processing.

LUMOZ supports OP stack plus ZK fraud proof, initiating a new paradigm INL2 architecture Lumos's modular compute layer has pioneered a new layer 2 architecture model, filling the gap in the current market for a mixed solution of ZK and OP.

113, NoSQL, System Design Cheat Sheet Wide Column Stores, Graph Databases, Time Series Databases, NoSQL, System Design, Interview, Key Value, Databases, Document Databases, Columnar Databases 114.

Why do you need JWT in your ASP.NET Core project? The story is about how to create a web API to generate JWT and then use it for authorization in the CRUD web API.

115.

And, you know, the whole thing about the webinar is that, you know, me being a fractional CTO, I help you make that tough call because when you're making this decision, your technical depth matters.

your experience of what has worked before or not, that matters, right? And those issues could be anything from like choosing between a relational database to NoSQL, right? Choosing between, you know, building an integrated platform so your AI is integrated to your workflow versus building and buying a software and another AI app that does something outside of your system, right? So the webinar is full of examples like that, but it all hinges on that, you know, same decision-making, you know, whether to build, buy, or kill.

No, that's a great, great point.

I like that, build, buy, or kill.

But if the process dies, the state disappears, right? For anything that needs to survive beyond that process, we usually externalize it.

This might be a relational database or a NoSQL database or a key value store, or it could be an object store, a file, or sometimes...

You need semantic memory.

You have semantic memories with the database.