JHipster provides support for many kinds of databases, ranging from SQL to NoSQL. The following are some considerations when choosing a DB:
- For most cases, a SQL DB would be more than sufficient, hence if you do not see any reason to go with other NoSQL solutions, stick to SQL and choose from MySQL, Postgres, Oracle, MariaDB, and MS SQL:
- If you are on an enterprise with Oracle or MS SQL subscriptions, then it would make sense to choose them as you would benefit from the support and enterprise features provided
- If you need to store and query a lot of JSON data, then Postgres offers the best JSON support with full-text search capabilities
- For most simple use cases, MySQL or MariaDB will suffice
- Always choose a second-level Hibernate cache when working with a SQL DB
- When choosing a development database for SQL:
- Choose an H2 file DB if you want a simple development setup with persistent data.
- Choose the same DB as the production DB if you want faster restarts and your persistent data doesn't need to be wiped every now and then. If you are using the provided Docker images, then wiping data will not be an issue.
- Choose an H2 in-memory DB if you do not want any persistent data during development and would like a clean state on each restart
- If your use case requires a lot of heavy data reads/writes, and if the data is not very relational, then Cassandra would be a perfect fit, as it is distributed and can work under extremely heavy loads.
- For a normal, non-relational data structure, MongoDB may be sufficient. You could also use Postgres as a NoSQL JSON store if needed.
- If you need enterprise support for NoSQL, CouchBase is a good option.
- Use Elasticsearch along with the primary DB for full-text search. If you only need simple filtering, use the JPA filtering option provided. Refer to: http://www.jhipster.tech/entities-filtering/.