Skip to content
Hallway
0:00 / 0:00

#mongodb#nosqldatamodeling#dynamodb

From RDBMS to NoSQL at Enterprise Scale

MongoDB

109K subscribers • 1 video on Hallway

YouTube
  • Recommended by 2 people: 2 in engineering communities.
  • Presented by Rick Houlihan, Director of Developer Relations at MongoDB
  • Made by the vendor. The company whose product it covers made or sponsored it.
  • An opinion. It argues one side of a question engineers disagree on.

Advanced. Deep dive for people who know the field.

3K views3 years ago2 recommendations

Databases and dataSoftware designNoSQL and document databasesDatabase internalsDesign patterns

Rick Houlihan explains NoSQL data modeling design patterns and best practices for migrating enterprise workloads from relational databases.

NoSQL isn't just a database. It's a new way of thinking about data. Traditional RDBMS has been baked into software development for decades. Moving development organizations from RDBMS to NoSQL means overcoming technology momentum and the natural bias to use solutions that are already well understood. Prior to joining MongoDB, Rick Houlihan led the NoSQL Blackbelt team for Amazon during their migration from RDBMS to NoSQL. This session is designed to introduce developers, technologists, and technical decision-makers to the NoSQL mindset and explore the design patterns and best practices developed by Rick and his team during that process. Join him for this insightful session that breaks down NoSQL data modeling for real-world workloads and dives deep into the core value of MongoDB for both SDEs and product stakeholders. Speaker: Rick Houlihan, Director, Developer Relations Company: MongoDB Level: Beginner .local London ’22 playlist ➡️ mdb.link/2hqQVoy Subscribe to MongoDB ➡️ mdb.link/4qa66rA #MongoDBlocalLondon22

Why it's here

2 people recommend this

What people say. Recommended as a definitive guide on how to properly model relational data in NoSQL databases without relying on lookups.

Moments people linked to

u/jose_plutomiin r/node • Recommends

On “mongoDB vs PostgreSQL”

Please stop spreading FUD about "relational data" and MongoDB. All data is relational otherwise we wouldn't care about it. You can model relational data \*just fine\* in ANY document / NoSQL database, you just have to do it differently or you're going to have a bad time. [video
2View on Reddit

u/jose_plutomiin r/node • Recommends

On “Migrating from Express.js to Fastify.js and MongoDB to PostgreSQL – Am I making the right decision?”

I never mentioned $lookups, this is using MongoDB wrong and I can guarantee is what everyone is doing here and having a bad time. > you have to find all the documents where it's embedded to update it there as well. I never mentioned this either, you can still keep separate documents completely unrelated on the same collection without embedding. Lookup key overloading or composite keys, here's an example: [video
2View on Reddit

u/pottaarghin r/node • Recommends

On “why people say mongodb is not good for relational data ?”

If you store your data in mongo is the same schema/structure as you would Postgres, then yes, you will have a terrible time. This is on the engineer for not reading the manual. Lookups between collections should be a last resort for most application queries, not the default. Recommend this video link to this video
1View on Reddit