# Why would someone choose MongoDB vs the built in MySQL?

**URL:** <https://community.dreamfactory.com/t/why-would-someone-choose-mongodb-vs-the-built-in-mysql/424>\
**Category:** App Configuration\
**Created:** [October 4, 2014, 5:21pm UTC](https://community.dreamfactory.com/t/why-would-someone-choose-mongodb-vs-the-built-in-mysql/424 "2014-10-04T17:21:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Markz](https://yyz1.discourse-cdn.com/flex035/user_avatar/community.dreamfactory.com/markz/32/137_2.png) [@Markz](https://community.dreamfactory.com/u/Markz)\
**Post date:** [October 4, 2014, 5:21pm UTC](https://community.dreamfactory.com/t/why-would-someone-choose-mongodb-vs-the-built-in-mysql/424/1 "2014-10-04T17:21:21Z")

</div>

Is creating schemas in launchpad the same for both MondoDB and the built in MySQL?

It seems that it doesn’t matter what data store one selects for the backend since it’s kind of black-boxed.

If that is the case then why would someone choose MongoDB over MySQL?

---

<div class="post-metadata">

**Author:** ![benbusse](https://yyz1.discourse-cdn.com/flex035/user_avatar/community.dreamfactory.com/benbusse/32/4_2.png) [@benbusse](https://community.dreamfactory.com/u/benbusse)\
**Post date:** [October 6, 2014, 3:06pm UTC](https://community.dreamfactory.com/t/why-would-someone-choose-mongodb-vs-the-built-in-mysql/424/2 "2014-10-06T15:06:50Z")

</div>

You can connect to SQL and NoSQL. What type of database you choose is really up to you. There are pros and cons for each, it really depends on your use cases. The APIs in DreamFactory really work the same, regardless of whether you’re using a SQL or NoSQL database on the backend.

In terms of schema management, DreamFactory currently allows you to manage SQL schema (both the MySQL db that comes with DreamFactory or any remote SQL db that you connect to). We’ll support NoSQL collection visibility / management in the future.