Journal Entry 7

Frances M. Brzycki Module 7

5 Predictions on the Future of Databases (From a Guy Who Knows Databases) Derrick Harris   URL

Why was this article, blog, post, or multimedia chosen?

This article was selected because it ties into our module with looking at the future of database technology. I’m always interested in seeing what the experts think about the future of technology and seeing if I agree or disagree with their way of thinking.   

 What makes it interesting, appropriate, or reputable? 

Michael Stonebraker “is a lightning rod in the database world and knows his stuff” (Harris, 2013). He is making five predictions regarding the future of databases in the twenty-first century.

Is it an opinion? Case study? Research study? Product review? 

This article is based on Michael Stonebraker’s opinion who is a leader in the database field.

What was the need, problem, issue or trend addressed in the article, blog, post, or multimedia? 

The author wanted to share with the user some key database management system (DBMS) considerations regarding technology prior to selecting a tool.

What was the solution for which technology had an answer? 

The solution was providing the key decision-maker with the information and knowledge to consider before bringing in-house a new database management system (DBMS). The five points to consider include: one size will fit none (consider both SQL and NoSQL to solve your problem), there’s room for a lot of winners (look at the new database system architecture before reverting to legacy relational database systems),

NoSQL will come back down to earth (this product will embrace the Atomicity, Consistency, Isolation and Durability (ACID) for performance and scalability), Oracle will feel the squeeze from SAP (these two corporations compete for customers), Facebook will keep searching for a MySQL replacement (according to Stonebraker Facebook needs to find a more state-of-the-art DBMS solution instead of resorting to legacy system technology) (Harris, 2013).  

What implications might this have in healthcare delivery? 

Database tools are needed to solve healthcare delivery problems. The strategic leaders in the organization need to evaluate the benefits and barriers or bringing a SQL versus NoSQL product in-house.  For example, looking at data storage SQL uses a relational model comprised of rows and columns. Rows contain all of the information about one specific entity and columns are all the separate data points. NoSQL encompasses a host of databases each with different data storage models. The main ones are documents, graph, key-value and columnar. Another example is scalability of a product. SQL scaling is vertical meaning more data and therefore needing a bigger server which can be expensive. NoSQL scaling is horizontal across servers meaning multiple servers can be an inexpensive commodity or cloud instance resulting in cost-savings instead of vertical scaling. You can partition complex operations across many servers/disks and have it work really fast. It all depends on your assessment and selecting the right tool to solve the problem. .

What did you learn from it that might have application for your practice? 

This article solidified my opinion that different databases can be beneficial for solving complex business or healthcare needs and all these databases can share the same “database space” e.g., Oracle versus NoSQL.  The bottom-line is the seasoned developer needs to do their due diligence in determining which database product will deliver the best end product for the client or patient that solves their problem. Databases are tools and the software developer needs to determine if the flathead screwdriver (NoSQL) or Philips screwdriver (Oracle) is needed to do the job.

References

Harris, D. (2013). 5 Predictions on the Future of Databases (From a Guy Who Knows Databases). Retrieved from https://gigaom.com/2013/12/14/5-predictions-on-the-future-of-databases-from-a-guy-who-knows-databases/