Talend, a global open source software leader, today recognized five key points companies should watch out for when dealing with NoSQL and implementing this new technology. As a speaker at the NoSQL Now! Conference in San Jose, Talend’s Ciaran Dynes, VP of Products, will be available at the event to speak about these and other tips for enterprises considering NoSQL. Join his panel session with other industry experts titled, “NoSQL grows up: Standards and Conventions” on Thursday, Aug. 22, at 2:00 p.m. PT.
Today, NoSQL is very much on the minds of companies looking to scale. Big Data is the driver for NoSQL’s rise but not the only reason to use NoSQL. It brings pure scalability – particularly horizontally – and the flexibility needed within application development, among many other benefits. Many NoSQL databases are designed to run well on large clusters, making them more attractive for large data volumes as well. If you’re working in the enterprise application world, now is the time to start familiarizing yourself with alternative data storage options. Talend offers five recommendations for enterprises to cope with this new technology and gain the benefits from NoSQL:
- Don’t wait – prepare now. From an IT perspective, start familiarizing yourself with NoSQL now, whether you have a project that currently needs it or not. A proof of concept now will help companies be ready to implement NoSQL when it comes. Don’t wait until you have to do it – start preparing the way now so you can make a more informed decision when you might need it.
- New technologies bring more complexity – be ready for the challenge. Each data storage mechanism introduces a new interface to be learned, and it often creates a performance bottleneck. NoSQL databases do not come with the maturity of other, tried-and-true databases, so you’ll need to understand how the technology works to get up to speed. Using the right technology will make this easier, but the challenge won’t go away. For example, the ease of use for the developer building a new application through NoSQL now burdens the operations team – the benefit of the database comes at a cost to complexity. Operations are ultimately responsible for supporting NoSQL, and the data storage associated with it (i.e., uptime, reporting, archiving.)
- Start with new projects – weigh cost vs. complexity. It takes a great deal of time and resources to invest in and learn a new technology. Rather than introducing the complexity to utility, core projects, you should look for new projects that are strategic in nature. Consider new projects that are worthy of the complexity, time and investment NoSQL can bring. It’s important to weigh the benefits vs. the cost.
- Consider reporting and analytics activities – know when to integrate. When you introduce databases, there is always going to be a business intelligence piece to it. NoSQL technology is so immature today that many of the reporting tools are unable to integrate with it. Take your down-stream reporting needs into consideration: They may require intermediary layers, so understanding when and where your reporting tools need to integrate with your data is important.
- Absence of standardization – beware of the risk. Because NoSQL is a more immature technology, there is no standard query language. As you introduce more of these NoSQL tools, there will be no commonality among them and migration to a solution from different vendors can be more costly and more complicated. There is a risk associated with selecting any technology that is not standards-based. This is an important consideration for integration needs as well as lowering your IT costs, so introducing technology that is not based on industry standards should be considered only when absolutely necessary.
“The benefits to NoSQL make it a valuable technology to implement, but the immaturity of it creates obstacles that enterprise companies need to be aware of,” said Bertrand Diard, co-founder and chief strategy officer, Talend. “As you introduce NoSQL, it creates complexities within the organization that need to be managed very carefully. Through these recommendations, we hope to help the people assigned to managing these new projects within the enterprise to better understand what to consider when implementing NoSQL and how to best achieve the results as this technology rapidly progresses.”