{"id":48481,"date":"2016-05-04T00:00:00","date_gmt":"2016-05-04T00:00:00","guid":{"rendered":"https:\/\/www.techopedia.com\/why-nosql-trumps-relational-databases-for-mobile-applications\/"},"modified":"2018-07-11T14:55:21","modified_gmt":"2018-07-11T14:55:21","slug":"why-nosql-trumps-relational-databases-for-mobile-applications","status":"publish","type":"post","link":"https:\/\/www.techopedia.com\/2\/29256\/development\/mobile-development\/why-nosql-trumps-relational-databases-for-mobile-applications","title":{"rendered":"Why NoSQL Trumps Relational Databases for Mobile Applications"},"content":{"rendered":"
Mobile application<\/a> development has taken off in recent years. The shift toward smartphones and tablets has given a huge boost to the number of mobile device<\/a> users across the globe. Because of this growing community of mobile users, the demand and expectations for mobile applications have grown significantly as well. In order for developers to fulfill the demand for mobile applications, streamlining the development process so that it is more efficient and less stressful has become increasingly important. Using NoSQL<\/a> for mobile applications does just that. (Get some background on NoSQL in NoSQL 101<\/a>.)<\/p>\n The relational database<\/a> model simply isn’t ideal for the dynamic needs of mobile applications. For one, traditional SQL<\/a> databases use fixed schemas. This creates issues because with mobile applications, there are many situational requirements. As developers come up with new ideas and features for their applications, making changes becomes a time-consuming task because constant changes have to be made to the database schema.<\/p>\nWhy Relational Databases Aren't Good Enough<\/span><\/h2>\n