Isos and Atlassian have been talking a lot about Cloud lately, but what about the tried-and-true Data Center offering we all love? I'm happy to say that Data Center is alive and healthy with an exciting roadmap ahead. Following are just a few features that were recently announced--and there are bunch more in the pipeline!
Data Center Refresher
Atlassian's Data Center, often referred to as simply DC, is the self-hosted/on-premise deployment option designed to help Atlassian customers effectively scale their mission-critical Atlassian applications. Through active clustering, teams can work around the clock with uninterrupted access to the tools they need to get their jobs done.
One of our favorite ways to deploy DC is in a public cloud, like AWS, Azure, or even GCP. This gives all of the scalability of a cloud deployment with all of the control of a self-hosted solution. The diagram above is an example quick-start architecture for deploying to AWS.
Rate Limiting to Stop Runaway Automations
Both Confluence DC and Jira DC now have the concept of rate limiting! The biggest enemy of a large-scale Atlassian implementation can be all of the internal automations that plug into the tools. Rate limiting is the single best defense against this and should be set up on every DC installation, without exception. Let’s take a closer look at this option and how it works:
Requests allowed: Every user is allowed a certain amount of requests in a chosen time interval. It can be 10 requests every second, 100 requests every hour, or any other configuration you choose.
Max requests (advanced): Allowed requests, if not sent frequently, can be accumulated up to a set maximum per user. This option allows users to make requests at a different frequency than their usual rate (for example, 20 every 2 minutes instead of 10 every 1 minute, as specified in their rate), or accumulate more requests over time and send them in a single burst, if that’s what they need. Too advanced? Just make it equal to Requests allowed, and forget about this field — nothing more will be accumulated.
As a longtime Jira Admin, I was always confused as to why certain activities were logged to the audit log and other activities were excluded. Atlassian has stepped up their audit logging game not only in Jira, but also in Confluence, Bitbucket and Jira Service Desk. Atlassian has taken a much more comprehensive approach to logging across all of the DC tools to ensure complete traceability of all actions taken in the products. For those concerned about governance and change management, these audit log changes are a welcome improvement.
Advanced Permission Management in Confluence
Diagnosing permission issues in Jira issues is made easier by the long-tenured Permission Helper feature. Confluence administrators are finally getting some love and should really benefit from this new DC tool. Given the fact that sensitive data often find their way into Confluence, this tool should become a space administrator's new best friend!