Enterprise AI Trend Report: Gain insights on ethical AI, MLOps, generative AI, large language models, and much more.
2024 Cloud survey: Share your insights on microservices, containers, K8s, CI/CD, and DevOps (+ enter a $750 raffle!) for our Trend Reports.
Jennifer Reif is a Developer Advocate at Neo4j, speaker, and blogger with an MS in CMIS. An avid developer and problem-solver, she has worked with many businesses and projects to organize and make sense of widespread data assets and leverage them for maximum business value. She has expertise in a variety of commercial and open source tools, and she enjoys learning new technologies, sometimes on a daily basis! Her passion is finding ways to organize chaos and deliver software more effectively.
Stats
| Reputation: | 398 |
| Pageviews: | 99.2K |
| Articles: | 12 |
| Comments: | 2 |
CORE
Comments
Mar 26, 2024 · Jennifer Reif
I agree. We're storing more and more data, but that's also spread across a variety of database systems and architectures. Some databases are more sensitive about normalization (for optimization) than others, but it's definitely not a required rule. I think it's going to depend on the data, queries, and use case (and somewhat on the database involved). Thanks for your thoughtful comment! :)
Sep 21, 2023 · Jennifer Reif
Good point on the line numbers. I'll get that updated!
For something more complex such as testing against multiple databases, I would recommend using a devoted library such as TestContainers or Test Harness (mentioned in the last section of the post). That way (in Testcontainers, at least), you can spin up instances of each database in the test class, and run each test against the desired database. As a side note, using a different database for production than in development - I commend your bravery and daring! :D