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.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hi Community! My name is Amir and I’m on the Jira Service Desk product marketing team at Atlassian. Our team would love to understand how you’re leveraging our ecosystem for Jira Service Desk. Wha...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs