The ORM complexity problem has a simple, production-ready solution hiding in plain sight in the Java world.
To fulfill the need for additional database processing speed and storage, the goal is to scale-out (add more commodity nodes to the system) rather than having to scale up (add more CPU or memory to each node). And to handle this need, two new kinds of scale-out databases have emerged: NoSQL and NewSQL. Let’s take a look at what sets them apart.
In this article I will discuss about the entity mapping procedure in JPA. As for my examples I will use the same schemathat I used in one of my previous articles.
It is silly, but I just had a conversation with one of our developers on SQL Injection. In RavenDB we support replicating to a relational database, which obviously require using SQL. We are doing things properly, with parameters and everything.
Josh Berkus at Database Soup wrote a post recently explaining how to find duplicate indexes in SQL. He has written a few queries to help those who need to filter through large amounts of indexes within a database. Berkus says his queries help to minimize the number of false positives that occur.
The Best of the Week (Sep. 19): SQL Zone
Join the DZone community and get the full member experience.Join For Free
Check out this 8-step guide to see how you can increase your productivity by skipping slow application redeploys and by implementing application profiling, as you code! Brought to you in partnership with ZeroTurnaround.
Opinions expressed by DZone contributors are their own.