Depends on your needs. Using the same box reduces network traffic and dependencies and keeps things very simple - "that box runs all of Jira". But a separate server means you know that the database server processes won't consume resources that JIRA could be using and vice-versa. So there's no simple answer to this one really!
Not a lot, unless you start trying to do "clever" things like ignore the API and talk directly to it, or run reports of it etc. Jira databases tend to be small - most users will find the database chews up a few Gb at most. On a well-tuned/monitored Jira, you'll mostly find the CPU ticks over at a couple of % usage most of the time. However, that said, it's really not easy to just say "well you can just use a small weak machine". It depends on your usage. Whatever you do, monitor the database service.
Hi Rich, if your enviroment is big enough I would recommend you to have in different servers. Plus, if your JIRA server goes down you can have a second enviroment and point it to the database. Remember is not recommended to have two working enviroments pointing to the same database.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG