Eight years of experience using NoSQL

Eight years of experience using NoSQL

Mike Bowers, an Enterprise Data architect at Jesus Christ's late Saints Church (LDS), introduced eight years of experience using NoSQL databases at the recent Enterprise Data World Conference (EDW. He talked about the design basis for selecting a NoSQL database.

If a large organization chooses to use a NoSQL database, it will take a lot of manpower and time to convert the relational database into a NoSQL database. It also needs to change the cultural management at different levels of the organization.

Mike shared the story of successfully promoting the emerging database technology (Document NoSQL database) to an enterprise with a large IT store. Now they use this technology to run 189 applications and process billions of transactions. The LDS church has 15 million members and provides thousands of documents in 188 languages. They generate 192 websites and applications (running on the Marklogic server), with billions of page views each year.

NoSQL databases adopt some initiatives, such as owning NoSQL champion and gaining support from developers and senior management teams.

Experience 1: each organization needs a NoSQL champion: This person needs to have an influence throughout the Organization and persuade developers and senior management teams in the company.

Experience 2: must be supported by the management: the senior management team in the enterprise prefers the enterprise-level commercial database, while the senior managers in the startup company prefer the open source database. Therefore, the team that changes to NoSQL reform must be supported by the Management and bring the NoSQL database to the Enterprise.

Experience 3: developers must be supported. The team also needs to introduce to developers that NoSQL databases support different data structures and support agile development. Mike said that Document NoSQL databases can provide faster development, while key/value databases provide faster performance. columnar databases provide online data processing.

Experience 4: training, training, and training: it is very important to train developers on using NoSQL databases. Without good training, the advantages of NoSQL databases cannot be reflected in projects.

He suggested using NoSQL databases to create a real solution. You can see that NoSQL databases can successfully execute your desired goals quickly and cheaply. NoSQL databases can reduce database licenses, reduce development costs, and provide better scalability.

Mike also compared several indicators of different databases, such as high bandwidth, low latency, analysis, operations, volume, and speed. Using NoSQL databases has some drivers, such as data modeling flexibility, performance, and horizontal scalability.

The team must reach a consensus on the use of specific NoSQL databases. Every team member participates in the decision-making process.

Lessons Learned from Eight Years of Using NoSQL

This article permanently updates the link address: