[DOCU-721] Database choice Created: 11/Apr/16  Updated: 30/Sep/19  Resolved: 30/Sep/19

Status: Closed
Project: Documentation
Component/s: content
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Antti Hietala Assignee: Unassigned
Resolution: Done Votes: 0
Labels: outdated
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

We say Derby is not a good choice in production but don't explain why. What constraints does it have? Where is Derby appropriate? Help the user decide.

Provide more guidance on choosing a database (persistent storage):

  • Question raised in a forum post: What is the use of MySQL
  • Why not Derby in production? Where can you use it?
  • General database recommendations
    • Use the database system where most knowledge is available in your organization.
    • Use MySQL if an open source DBMS should be used and there is no deeper DB knowledge is available.
    • Use MySQL only with InnoDB Storage Engine.
    • Use PostgreSQL if you have already people / knowledge to handle it.
    • etc.


 Comments   
Comment by Julie Legendre [ 30/Sep/19 ]

In order to better focus our efforts on DOCU tickets that are still relevant and important, all tickets older than 18 months have been labelled as outdated and are being automatically closed.
If you think your ticket is still relevant and should remain open, please add a comment and set it back to open.

Generated at Mon Feb 12 01:11:47 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.