how to fetch a value from persistence.xml to build.properties?

Will future apps be built with no database but only Redis (or other key-value stores) as a persistence layer?

  • We have witnessed the storage technology pushes both the power consumption level and price tag of Memory chips lower and lower. We have also witnessed that NoSQL is gradually replacing SQL for solving new problems in the new era. It is not a simple "new tech replacing old tech" thing, but a paradigm shift in data structure design. I know that for certain apps, we still need RDBMS or NoSQL or even both. However, what I am interested in is that will future apps be built without either of those but only Redis as a persistence layer. More information This is a follow-up question of this question:

  • Answer:

    Redis is still a database, it's just a different kind. NoSQL is a broad term for several types of databases (and it includes key-value, document based, graph, columnar, etc.) while SQL refers to traditional relational database systems. What we have today is choice, but there's no "correct" choice. Everything depends on what the application needs for persistence and performance. These new systems are not magical technology but designed to solve specific challenges. Redis is just a key-value store that allows complex data structures and if that's all an application requires then it'll work just fine.

Mani Gandham at Quora Visit the source

Was this solution helpful to you?

Other answers

SQL and NoSQL make the database spectrum. It's either SQL or not, i.e. NoSQL, so if the apps will be built without either, that means they will not have any persistance Redis is a DB, it's a key-value store. It also handles lists, sets, hashes so it's quite versatile. Redis' strength and weakness is the fact it's in memory, so it requires a different approach than "let's shove everything in here and worry about it later". There is absolutely no reason Redis can't be used as a sole data store as long as it's managed correctly. In a lot of cases it solves problems, in some cases causes them, but that's no different than any other system. One main point to realize is that whether it is SQL or NoSQL or SomeOtherSQLish thing. Use what's right for you and what fits your data. The reason K/V, Object, Document, etc stores exist is because a monopolistic SQL solution wasn't cutting it. Not that there was anything inherently wrong with SQL, not because someone someone wanted to make Frankenstein, it's because they just thought their data better fit into a non-relational structure.

Igor Putilov

In general, no, simplistic data stores like Redis will not replace databases (of any kind).  Every non-trivial application will probably need to deal with persistent data using a variety of data/operation and consistency models - from eventually consistent get/put on whole objects to strongly consistent transactions using a single field in millions of rows/objects whatever. Key/value stores will have their place.  So will document stores, "wide column" stores, object stores, even block stores and file systems.  A single application is likely to use many of these, either deployed solely for its own benefit or consumed as multi-tenant services.  It's called "polyglot persistence" and that's what will replace the "single source of truth" model for data storage in older applications.

Jeff Darcy

Redis, MongoDB and other NO SQL DBs do not strictly follow ACID properties of the Database. We basically use Redis , MongoDB in cases where we just need to store Information as key-value pair.  Some of the example could be apps which just store information on 1 time basic and overwrite it when the new value come for the same key. I personally use Redis in one of my projects where i store RTT [ Round Trip Time ] between 2 routers per flow. Here the flow-id is the key. Now coming to RDBMS , we cannot completely remove them for persistence layer. SQL Server , Oracle DB etc are the heart of any Web Application where all the data resides. So any app , which is a wrapper over a big software will also use this DB to pull data. So yes we are seeing the increase use of "No SQL DB" , but RDBMS will not be completely wiped out.

Sambit Mishra

Just Added Q & A:

Find solution

For every problem there is a solution! Proved by Solucija.

  • Got an issue and looking for advice?

  • Ask Solucija to search every corner of the Web for help.

  • Get workable solutions and helpful tips in a moment.

Just ask Solucija about an issue you face and immediately get a list of ready solutions, answers and tips from other Internet users. We always provide the most suitable and complete answer to your question at the top, along with a few good alternatives below.