Frances
M. Brzycki Module 2
Why
your company should care about its database, Andrew Nusca URL
Why was this article, blog,
post, or multimedia chosen?
Foundation
is critical to how queries and reporting is done on data. If you don't have a
strong "blue print" regarding design it will impact your retrieval
time. In the 21st century end users don't want to wait for their information. I
want to learn best practices companies deployed regarding solid database design
and see if I agree with them. Today’s businesses live and die by
their applications, which means that the plumbing matters. (Nusca, 2015). The plumbing he is referring to is the system
architecture.
What makes it interesting, appropriate, or
reputable?
I work in healthcare and manipulate data for key
decision-makers. I see how good and bad design of databases impact the
retrieval time regarding obtaining information. It is critical to know your
data and what makes the best index in manipulating this data e.g., primary key
or foreign key. Your query retrieval can
be seconds or minutes depending on your design considerations and planning done
upfront. I'm always assessing and
evaluating how I can make data retrieval tools better for my end-users when it
comes to shifting through vast amounts of data or cloud computing. I'm of the
opinion it's all about engaging your user and giving them a great experience
when using the application or system.
Is it an opinion? Case study? Research study?
Product review? This article is both an opinion and product
review.
What was the need, problem, issue or trend
addressed in the article, blog, post, or multimedia?
The author shared with the reader it is important
to have a business model that reflected the needs of his/her customers to have
a competive edge in the 21st century if they want to play in the space of
online computing. An example given was the online publishing business needed to
change its business model from a brick and mortar to online "real
time" model e.g., McGraw-Hill.
What was the solution for which technology had an
answer?
Database designs that are scalable,
performance-driven and reflect the organizations business model are paramount
to survive in the market place today. The product NoSQL is a tool that claims
provides this level of service to its clients by using "distributed
processing" opposed to "central processing". Their claim is to
spread the database out over several processors as opposed to one main
processor.
What implications might this have in healthcare
delivery?
I have mixed feelings about this tool. The approach
to "distribute" the database sounds feasible however, there needs
additional investigation to be done regarding software licenses and hardware
costs in addition to security considerations e.g., HIPAA and PHI that are spread out over multiple client
sites. I'm not running out to purchase this package right away.
What did you learn from it that might have
application for your practice? As a software developer this tool claims vendors have a
schema-less database model that can be easy to use when working with formats
that aren't rigid compared to relational databases that are very structured. I
would like time to test this tool with the huge databases that are required to
shift through regarding claim and client data to see if it might have a
potential fit within my organization.
References
Nusca, A. (2015). Why your company should
care about its database. Fortune. Retrieved from http://fortune.com/2015/01/29/couchbase-nosql-database/
