Relational Database Models Vs. Entity Models

-

I wrote some time back in February Shifting Away From Tables To Entity Models discussing about fast adoption of Entity models for highly scalable systems moving away from RDBMS modeling and RDBMS databases.

DataStore (based on Google’s Big Table) in Google App Engine is an excellent contrast between  these two models.

RDBMS relational data management systems, simply put, most Database systems allow us to create data models of businesses in terms of rows and columns in a table. Tables can be ‘related’ to indicate dependencies of data between tables. RDBMS was on the best things that ever happened to software abstractions. Every business domain has been modeled to be a set of tables and relations between them.

However, recently another paradigm is taking shape (at least, I only noticed it in the last year), called as Domain Driven Development, DDD for short, that emphasizes the importance of modeling a business in the domain of the business itself rather than dictated by abstractions tied to tables. DDD clout calls them “Entities” (not Tables).  In certain ways, I read this shift from RDBMS to Entity model as “shift from horizontal (table) abstractions to hierarchical (entity) abstractions”.

I found some similar discussion on ReadWrite Enterprise Is the Relational Database Doomed? discussing much more comprehensively about the fallout of RDBMS towards Cloud based (Entity Model) databases.

As Google explained the reason of ‘scalability’ that led them to design Big Table, the author of this article also believe scalability is prime reason that may sway us to move away from RDBMS.

Relational databases scale well, but usually only when that scaling happens on a single server node. When the capacity of that single node is reached, you need to scale out and distribute that load across multiple server nodes. This is when the complexity of relational databases starts to rub against their potential to scale. Try scaling to hundreds or thousands of nodes, rather than a few, and the complexities become overwhelming, and the characteristics that make RDBMS so appealing drastically reduce their viability as platforms for large distributed systems.

Cloud databases like Google App Engine force a different modeling of your databases, for scalability. So I guess, best way to learn is to develop an app on Google App Engine.

Comments

Post a Comment

Popular posts from this blog

Newsworthy News in Red October : Dow Jones & Tax Dodgers

-
Dow Jones Index crosses the symbolic 10000 figure. U.S. stocks rallied, sending the Dow Jones Industrial Average above 10,000 for the first time in a year, on better-than-estimated earnings at JPMorgan Chase & Co. and Intel Corp. Bank of America Corp., American Express Co. and JPMorgan more than doubled since the Dow slid to a 12-year low on March 9 as global financial firms began recovering from $1.6 trillion in writedowns and credit losses. International Business Machines Corp. and Hewlett-Packard Co. jumped at least 54 percent since March 9 on signs the nation was recovering from the worst recession in seven decades. Source: Bloomberg And, about 7500 International Tax dodgers file for IRS Amnesty to avoid jail Some 7,500 international tax dodgers have applied for an amnesty program that promises no jail time and reduced penalties for tax cheats who come forward, the Internal Revenue Service announced Wednesday. … The program is part of a larger eff...
Read more

USCIS Selects Final H1B Petitions by Random Selection - Almost a 50% chance for each Application

-
U.S. Citizenship and Immigration Services (USCIS) announced today that on April 12 it conducted the computer-generated random selection process to determine which H-1B petitions, subject to the congressionally mandated H-1B cap for fiscal year 2008 (FY 2008), would continue to final processing. USCIS completed this determination ahead of the preliminary schedule noted on April 3, when it announced it had received enough petitions to meet the cap for FY 2008. The 123,480 cap-subject petitions received on April 2 and 3 were labeled with unique numerical identifiers and selected randomly by computer. The chosen numerical identifiers were then transmitted to the appropriate service center for further processing. Source: USCIS Announcement Number 123,480 looks a lot better keeping in view initial estimates. A good 50% chance for each application to be selected.  Update: 3rd May 2007 Hello friends, I understand your anxiety. But don’t loose your hope and/or temper yet. Please wai...
Read more

H1B 2008:USCIS released Preliminary Numbers

-
USCIS today released the final count of number of unique pieces of mail received for H1B petitions. It received 133,000 unique pieces of mail containing H-1B petitions. I guess, each piece of mail will ' mostly ' contain more than one petition, as no company would send each petition in a seperate package and its most unlikely that a firm applies for just one petition. Probably by the end of next week, we might know the actual number of H1B petitions filed and how lucky one must be to get through the initial filter. Source: USCIS Releases Preliminary Number of FY 2008 H-1B Cap Filings  (26KB PDF) 04/05/2007 During Monday and Tuesday, USCIS received 133,000 unique pieces of mail containing H-1B petitions. This is lower that the original USCIS estimate of 150,000. USCIS based the initial estimate on amounts from manifests received along with the mail. USCIS reached the updated number following a physical count of the mail. Each piece of mail may contain more than one H-1B pe...
Read more