When you use Apps on you mobile device an App experience must be fast. So Application data must be transferred fast and of course secure. When you create an App you known the number of choices for storing back-end data for a mobile App are large. A common way for storing data is to use a back-end somewhere where data is stored in a traditional SQL database. This means that as you as App developer will have the responsibility for:
[list list_type=”0″ animation=”” actions=”icon-right-circle-1^icon-right-circle-1^icon-right-circle-1″ colors=”^^” list_item_content=”Creating a data model;^Creating (secure) interfaces for all communication between your App and your database back-end^Maintenance and health keeping on the database. For example your data should be able to survive disasters, like hardware failures and should be protected against all kind of security breaches” sc_id=”sc1452157590729″]
[title type=”h3″ font_size=”default” font_weight=”400″ align=”left” color=”” bottom_indent=”” use_general_color=”0″ use_border=”0″ animation=”” sc_id=”sc1452159022327″]Whoohoo, Big Data[/title]
Today everyone talks about big data. Big data can be defined as data where the volume, velocity or variety of data is great. With the rise of big data and more and more questions arise what the best way for storing data for Apps is. The field of data storage options is besides traditional SQL database storage extended with Document databases (e.g. mongoDB, Couchbase), Graph Databases (e.g. Neo4J), Wide Column Stores (e.g. Amazon DynamoDB and Redis) and Key-Value Databases (e.g. Cassandra and Amazon SimpleDB). Determining which of these storage options will make the perfect fit for your new App is a hard tasks.
And after choosing a storage option you still have the integration challenges to make it working correctly with your App. This will eat your scare development time. You know all your users see is in the end is the look and feel of your App. But the back-end of your App must be solid to meet your expectations like performance, reliability and security. So instead of working on good front-end design a lot of time is spend on back-end integration work.
[title type=”h3″ font_size=”default” font_weight=”400″ align=”left” color=”” bottom_indent=”” use_general_color=”0″ use_border=”0″ animation=”” sc_id=”sc1452159412189″]Database as a Backend[/title]
At Jexia we have taken an another approach: We have taken your back-end data as point of departure. We think that you as developer should not lose valuable development time on database development tasks when creating Apps. Figuring out what the best storage option for your data is and creating logic to store and retrieve data secure should not be time consuming. It should be simple:the back-end data storage should be fast, secure and reliable. All without difficult integration challenges.
[title type=”h4″ font_size=”default” font_weight=”400″ align=”left” color=”” bottom_indent=”” use_general_color=”0″ use_border=”0″ animation=”” sc_id=”sc1452159811919″]NoSQL Relations[/title]
Jexia gives all App developers the possibility to focus more on the real value added App development tasks, since the Jexia back-end will handle all complex data storage functionality for you. The heart of the Jexia data storage is partially based on industry proven nosql storage facilities. One core feature of Jexia is, is that all your data storage actions are based on simple REST API’s. The way you want to structure your data is up to you. You can store all your data as plain json, or structure your json documents in advanced to make retrieval and building logic easier. But you can also still use Jexia as traditional sql like storage. However, note that the Jexia back-end is no traditional SQL database. However Jexia does offer great options to easily structure your data and create relations. This all without having the traditional complex sql functionality. So if you want to create your new App fast with RESTful interfaces created automatically for you, give Jexia a try.