IDEAS home Printed from
MyIDEAS: Log in (now much improved!) to save this article

NoSQL and SQL Databases for Mobile Applications. Case Study: MongoDB versus PostgreSQL

Listed author(s):
  • Marin FOTACHE


  • Dragos COGEAN


Registered author(s):

    Compared with "classical" web, multi-tier applications, mobile applications have common and specific requirements concerning data persistence and processing. In mobile apps, database features can be distinctly analyzed for the client (minimalistic, isolated, memory-only) and the server (data rich, centralized, distributed, synchronized and disk-based) layers. Currently, a few lite relational database products reign the persistence for client platforms of mobile applications. There are two main objectives of this paper. First is to investigate storage options for major mobile platforms. Second is to point out some major differences between SQL and NoSQL datastores in terms of deployment, data model, schema design, data definition and manipulation. As NoSQL movement lacks standardization, from NoSQL products family MongoDB was chosen as reference, due to its strengths and popularity among developers. PostgreSQL serves the position of SQL DBMSs representative due to its popularity and conformity with SQL standards.

    If you experience problems downloading a file, check if you have the proper application to view it first. In case of further problems read the IDEAS help page. Note that these files are not on the IDEAS site. Please be patient as the files may be large.

    File URL:,%20Cogean.pdf
    Download Restriction: no

    Article provided by Academy of Economic Studies - Bucharest, Romania in its journal Informatica Economica.

    Volume (Year): 17 (2013)
    Issue (Month): 2 ()
    Pages: 41-58

    in new window

    Handle: RePEc:aes:infoec:v:17:y:2013:i:2:p:41-58
    Contact details of provider: Postal:

    Phone: 0040-01-2112650
    Fax: 0040-01-3129549
    Web page:

    More information through EDIRC

    References listed on IDEAS
    Please report citation or reference errors to , or , if you are the registered author of the cited work, log in to your RePEc Author Service profile, click on "citations" and make appropriate adjustments.:

    in new window

    1. Alin ZAMFIROIU, 2012. "Integrability and Interoperability of Mobile Applications," Informatica Economica, Academy of Economic Studies - Bucharest, Romania, vol. 16(4), pages 150-158.
    2. Paul POCATILU, 2012. "Building Database-Powered Mobile Applications," Informatica Economica, Academy of Economic Studies - Bucharest, Romania, vol. 16(1), pages 132-142.
    Full references (including those not matched with items on IDEAS)

    This item is not listed on Wikipedia, on a reading list or among the top items on IDEAS.

    When requesting a correction, please mention this item's handle: RePEc:aes:infoec:v:17:y:2013:i:2:p:41-58. See general information about how to correct material in RePEc.

    For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: (Paul Pocatilu)

    If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.

    If references are entirely missing, you can add them using this form.

    If the full references list an item that is present in RePEc, but the system did not link to it, you can help with this form.

    If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your profile, as there may be some citations waiting for confirmation.

    Please note that corrections may take a couple of weeks to filter through the various RePEc services.

    This information is provided to you by IDEAS at the Research Division of the Federal Reserve Bank of St. Louis using RePEc data.