IT Infrastructure: NoSQL Database: 5 Ways to Make It Enterprise-Ready
IT Pros Don't Want to Learn Multiple New Programming Languages
If a shift away from traditional RDBMSes based on SQL programming is to occur, developers and DBAs have to learn other design and programming techniques to deal with the database. Right now, most NoSQL vendors are building their solution around a proprietary API that creates adoption headaches and cost for the enterprise to train DBAs and programmers on these new techniques. Instead, widely known soft-schema relational database interfaces, such as the Java Persistence API, or JPA, should be adopted by the NoSQL vendors. This will allow enterprises to lower the cost and risk of adoption by leveraging existing employee skill sets. At the same time, businesses can capitalize on the architectural scale-out advantages of a NoSQL solution. Most developers know these interfaces already, and this makes it easier for enterprises to switch to a new DB platform.
Everyone in the enterprise is now talking about how to leverage big data, and a good chunk of that discussion includes the evolution of NoSQL database technologies. Experts are saying that 2012 is the year when IT departments start adopting NoSQL in earnest, but is the enterprise ready yet? What needs to happen in NoSQL's evolution to make it prepare it for highly complex data requirements? To find out, eWEEK asked Robert Greene, vice president of technology at Versant and a 20-year veteran of the database industry, to break down what needs to happen for NoSQL to become enterprise-ready. Versant is an object-oriented database provider, and the company is taking its own approach to the NoSQL movement. For instance, Greene said that NoSQL solutions need to leverage more of the classic database techniques for concurrency control and design their internals to take full advantage of modern multi-core hardware architecture. In addition, Greene said NoSQL is learning what the object database industry learned several years ago as it sought to deal with soft schema over a relational storage engine. However, enterprises will not change all their internal processes and replace existing systems for the sake of NoSQL. To evolve, NoSQL must address interoperability with existing systems, to couple through ETL, to facilitate data manipulation through enterprise tools, and it needs to present itself as a well-defined resource to existing monitoring and management processes.