4 ms·

This is entirely because they had to fork their product and codebase between cloud and on-prem, and their resulting total failure on execution on their interna

This is entirely because they had to fork their product and codebase between cloud and on-prem, and their resulting total failure on execution on their internal product roadmap. Atlasssian has demonstrated a chronic inability over the past few years to maintain feature parity between what are effectively two different products. Atlasssian has had a really, really terrible feature execution delivery pace over the past few years - "Next-Gen Projects" were so immature at launch they were useless, and have been incredibly slow to mature. So they need to focus their developers onto building features on the Cloud product codebase, but I am not hopeful that this means they'll actually ship features faster.

x3n0ph3n3 6y ago
It's insane that they had to that rather than giving their On-Prem version the ability to scale the way you need a SaaS service to scale. Turning your SaaS Ops team into an On-Prem customer is a great way to dog-food your product.
- HarveyKandola 6y ago
  It's not easy unless you begin with that mind-set from day one. In fact, it gets tricky as you have "location-flagged" functionality depending upon Cloud or Self-hosted. We did this from scratch @ Documize by making (bold?) choices around deployment/runtime and database schema design for both SaaS and self-hosted "products": - run the exact same binary (we used Golang) - share/use the exact same database schema - data migration process the same for schema changes - support multi-tenanting: "enterprise" self-hosted also multi-tenanting so different teams/departments internally get different URLs - use the same "build" process to compile and ship Probably plenty more I could tell you!
  - x3n0ph3n3 6y ago
    I know it's not easy, but it's the only viable path form my experience. I ended up doing something similar, but taking our SaaS product and packaging it in a way that it could be run On-Prem. There was a really interesting feedback cycle where we wanted to make the On-Prem and SaaS deployments work as similarly as possible.
- jeff_redradish 6y ago
  Atlassian's Cloud products were initially (~2009) just the Server products with a few plugins bolted on to unify the UI, deployed in bulk. Over time the backends diverged, and here we are.
ashtonkem 6y ago
There’s an irony in Atlassian failing to manage their internal roadmap and timelines.
- oars 6y ago
  Love this!

x3n0ph3n3 6y ago

It's insane that they had to that rather than giving their On-Prem version the ability to scale the way you need a SaaS service to scale. Turning your SaaS Ops team into an On-Prem customer is a great way to dog-food your product.

HarveyKandola 6y ago
It's not easy unless you begin with that mind-set from day one. In fact, it gets tricky as you have "location-flagged" functionality depending upon Cloud or Self-hosted. We did this from scratch @ Documize by making (bold?) choices around deployment/runtime and database schema design for both SaaS and self-hosted "products": - run the exact same binary (we used Golang) - share/use the exact same database schema - data migration process the same for schema changes - support multi-tenanting: "enterprise" self-hosted also multi-tenanting so different teams/departments internally get different URLs - use the same "build" process to compile and ship Probably plenty more I could tell you!
- x3n0ph3n3 6y ago
  I know it's not easy, but it's the only viable path form my experience. I ended up doing something similar, but taking our SaaS product and packaging it in a way that it could be run On-Prem. There was a really interesting feedback cycle where we wanted to make the On-Prem and SaaS deployments work as similarly as possible.
jeff_redradish 6y ago
Atlassian's Cloud products were initially (~2009) just the Server products with a few plugins bolted on to unify the UI, deployed in bulk. Over time the backends diverged, and here we are.

ashtonkem 6y ago

There’s an irony in Atlassian failing to manage their internal roadmap and timelines.

oars 6y ago
Love this!