CONCLUSIONS AND FUTURE WORK
We have discussed some technological features of NoSQL and NewSQL databases.
Developers need to be aware that NoSQL databases and their advanced improvements
collectively called NewSQL databases are not a replacement for RDBMS; they are
designed for a specific scenario in which can be successful. Some database technology
features are suppressed, some conversely are improved. We can observe that rather
native solutions are preferred for various data models and these systems are subsequently
integrated.
Without doubts, NewSQL databases contribute to applications that require Big
Analytics and/or those requiring transaction processing with ACID guarantee. They also
improve and extend functionality of traditional RDBMS. They often also absorb, e.g.,
through an API, data models and data manipulation capabilities of NoSQL databases.
Now, the challenge is not only to take in charge the volume of incoming data, but
especially speed analysis and relevant trigger actions. This requires a more advanced
integration with data analytics tools. More information about Big Data tools as such can be
found in [5].
Comparing the usability of DBMS in the past, a new issue appears now: a real
applicability of NoSQL and NewSQL. Due to the diversity of today’s database architectures
and their technological features, a system administrator must consider carefully which type
of database best suits applications before committing to one implementation or the other.
Today, NoSQL databases start to evolve and take on more traditional DBMS-like features.
Often, a mix of traditional DBMS and new NoSQL solutions is beneficial. On the other
hand, ad-hoc designs of NoSQL databases prevent their wider adaptability and
extensibility.