database management system

mySQL, NoSQL, and now NewSQL? {4}

by Eric C
In today’s fast paced world with data growing at an exponential rate, a database must be scalable and perform well with today’s demands in storing data. SQL databases have been around for decades and the basic architecture wasn’t created with scalability in mind. Apparently there have been new advances in database technology and it includes instances of NoSQL and NewSQL. Michael Stonebraker is a seasoned database creator who is now a chief technology officer for VoltDB, explained the benefits of using “NewSQL” to better benefit today’s demands for database performance. Stonebraker stated that traditional SQL systems have many limitations and that includes performance. SQL databases are also not scalable onto more than one server. If one were to make an SQL database scale onto more servers for better performance, it would be very complicated to manage. NoSQL was indeed created to improve on scalability and is increasing in popularity; it also has its own limitations as well. The main problem with NoSQL is that it cannot perform complicated mathematical queries. However with NewSQL, it improves on all of the issues with SQL and NewSQL, making it a more efficient database system that can process requests faster and can scale to more than one server. According to Joab Jackson, the author of the article entitled “’NewSQL’ Could Combine the Best of SQL and NoSQL” from PCWorld, using NewSQL “can execute transactions 45 times faster than a typical relational database system” and “can scale across 39 servers, and handle up to 1.6 million transactions per second across 300 CPU cores” (Jackson). read more...

What to do With Too Much Data {2}

by Tyler K

In the article, the author discusses how the modern database often extends beyond a few hundred entities; modern day companies regularly are wading through terabytes of information, trying to drag useful & meaningful context out of massive loads of information. Several massive problems are brought up – searching through the data is tedious and yields irrelevant results, metadata could vary in the usefulness and the context might not be comprehended by others, attributes could mean the same thing but be sorted separately (ex: Mac, Macintosh, Apple Computer, iMac could all be different ways to describe the same product), and it is very difficult to standardize the data and determine who regulates and incorporates the standardization – and if it’s even worth the time to do so. Thus, the solution offered is simple – relax the standard. Let there be a little differentiation, and create unified product descriptions that can catch multiple ways of describing the same object, determine responsibilities for who is going to ensure data integrity. Even then, there is no hard solution, and the conclusion is that there must be a future implementation of database management systems that can form patterns and relationships with data, have well-documented information on where data is originating from, and develop a system to understand how much is being lost by inaccuracies in the data. read more...

Database for Medical Images in Developing Nations {3}

by Alexander H
Medical images have provided a strong foundation for the health care system in diagnosis and medical studies. Traditionally, developing nations have recorded and viewed images from film rolls. However, as technology advances, digitizing these images have become the normal means of use in many countries, but developing nations have yet to see this switch. “Database Management System for Digitized Medical Images” is a journal that seeks to eradicate this gap in technologies and bring together medical images into one cohesive package. The journal states the importance of having the ability to share medical images in a system that can be readily available to the health care system. Essentially, the database that is proposed will take medical images and digitize them. These images are then stored in the database where the user can call for these images and the database converts them back to grayscale for viewing. The conversion process will be handled by a program called Matlab. Once compiled, SQL will be the database management system of choice. Handling the user end viewing of the database will be the result of C# programming. The journal believes that bridging the gap with the use of this database management system will greatly affect the health care industry and its worldwide application can share rare medical anomalies readily. read more...