Bitbucket: Bitbucket Server vs. Bitbucket Data Center


Objective

How does Bitbucket Server differ from Bitbucket Data Center?

Environment

Server/Data Center

Procedure

Bitbucket Server is a single instance of Bitbucket running on a single machine. It can only handle as much load as a single machine is capable of handling before performance degrades. If the machine goes down for any reason (for example, hardware failure, network fault, or planned maintenance), then Bitbucket Server is unavailable to users for the downtime. 

Bitbucket Data Center looks like a single instance of Bitbucket Server to users, but under the hood, it consists of a cluster of multiple machines ("cluster nodes") each running the Bitbucket Server web application, behind a load balancer. This provides important benefits over Bitbucket Server:

  • Performance at scale: A cluster of many machines running Bitbucket Server can handle more load than a single machine.
  • High availability: If one cluster node goes down, then the remaining cluster node(s) can continue servicing requests so users should see little or no loss of availability. 
  • Smart mirroring: Smart mirrors can improve Git clone speeds and configuration for distributed teams.
  • Data Center MigrationData Center Migration is a tool for admins to allow consolidation of multiple Bitbucket instances, or move from a server to a Data Center instance. Git data can be imported or exported into Bitbucket Data Center from another Bitbucket Server or Data Center deployment, along with pull requests, comments and attachment history.
  • SAML 2.0 support: This feature enables you to implement SSO through an IdP for your users

For more information, see:

 





Last modified on Dec 10, 2018

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.