Atlassian Confluence vs. Digital.ai Release vs. Progress Chef

I would recommend Atlassian Confluence for companies that want to have internal documentation and minimum governance processes to ensure documentation is useful and doesn't have a lot of duplicated and non-updated content. I wouldn't recommend Atlassian Confluence for companies with a low budget since this product might be a little costly (especially with add-ons).

Incentivized

Mainly used in release management where all deployments are well managed and processed further based on the approval system. Complete enterprise-level solution with minor difficulties which need to be added to product improvement features. Integration with other CI-CD tools makes it easier to perform tasks in terms of release and deployments.

Incentivized

Chef is a fantastic tool for automating software deployments that aren't able to be containerized. It's more developer-oriented than its other competitors and thus allows you to do more with it. The Chef Infra Server software is rock-solid and has been extremely stable in our experience. I would definitely recommend its use if you're looking for an automation framework. And it also offers InSpec which is a very good tool for testing your infrastructure to ensure it deployed as intended.

Incentivized

• Cross product linking - If you use other Atlassian products then Atlassian Confluence is a no-brainer for your source of documentation, knowledge management etc. You can show previews of the linked asset natively E.g. showing a preview of a JIRA ticket in a Atlassian Confluence page.
• Simple editing - Though the features available may not be super complex right now, this does come with the benefit of making it easy to edit and create documents. Some documentation editors can be overwhelming, Atlassian Confluence is simple and intuitive.
• Native marketplace - If you want to install add-ons to your Atlassian Confluence space it's really easy. Admins can explore the Atlassian marketplace natively and install them to your instance in a few clicks. You can customise your Atlassian Confluence instance in many different ways using add-ons.

Incentivized

• Cross-team release workflow control using email, texts, scripts allow our release management to be truly a 360 process.
• XL Release allowing our Jenkins toolchain to control the beginning of release trains which is very powerful.
• XL release allows us to expose the business process flow for anyone to read direct at the source which runs the process instead of a separate vision.

Incentivized

• Chef is great at deploying code to both small and large groups of servers.
• We use chef to standup new servers as well as deploy updated code to existing servers and it does this very well.
• Being able to make a change and have it push manually or automatically to any subset of servers has changed the landscape of how our IT teams operate.

Incentivized

• UI Design is very simplistic and basic could make use of more visually interesting colour choices, layout choices, etc.
• Under the 'Content' menu, it defaults to having a landing page for all L1 and L2 category pages. Meaning as long as the broader content category has a sub-category, it still creates a separate landing page. In my team's case, this often creates blank pages, as we only fill out the page at the lowest sub-category (L3).
• Hyperlinks are traditionally shown as blue, however, this results into very monotonously blue pages in cases where a lot of information is being linked.

Incentivized

• Pagination of data - across tool.
• User Roles Management API can be improved.
• Case insensitive ID's are treated differently making user face login and access issues.
• Dependency on Universal template/custom plugins creation should be reduced.
• Code versioning of templates is very difficult.
• Better error handling.
• Futures Timeout Issues.

Incentivized

• Chef could do a better job with integration with other DevOps tools. Our company relies on Jenkins and Ansible, which took some development and convincing for plug-ins to be created/available.
• It would be nice if kitchen didn't only have a vagrant/virtual-box prerequisite. Our company one day stop allowing virtual-box to run without special privileges, and that caused a lot of issues for people trying to do kitchen tests.
• Chef could use more practice materials for the advanced certification badges. There was not a lot of guidance in what to study or examples of certain topics.

Incentivized

I am confident that Atlassian can come with additional and innovative macros and functions to add value to Confluence. In 6 months, Atlassian transformed a good collaborative tools into a more comprehensive system that can help manage projects and processes, as well as "talk" with other Atlassian products like Jira. We are in fact learning more about Jira to evaluate a possible fit to complement our tool box.

Great for organizing knowledge in a hierarchical format. Seamless for engineering and product teams managing software development. Helps in formatting pages effectively, reducing manual work. Tracks changes well and allows for easy rollbacks. Granular controls for who can view/edit pages. Search function is not great which needs improvement. Hire some google engineers

Incentivized

The tool is easy to use, easy to navigate and learn. Manages releases with proper approvals in a systematic manner. Though it needs minor improvements in terms of pagination (data loading), access management, but, overall the tool helps in increasing productivity and less time for production deployments.

Incentivized

The suite of tools is very powerful. The ability to create custom modules allows for unlimited potential for managing all aspects of a system. However, there is pretty significant learning curve with the toolset. It currently takes approx 3-4 months for new engineers to feel comfortable with our implementation

Incentivized

I do not recall having outages or applications error so far, very reliable and available.

Incentivized

We never worked against the tide while using Confluence. Everything loads considerably fast, even media components like videos (hosted on the platform or embed external videos from Youtube, for example). We are not using heavy media components a lot, but in the rare occasion we happen to use one we have no problems whatsoever.

Incentivized

It loads quick enough for basically all our systems. Because we have this for local dev environments, speed isn't really a big issue here. Yes, depending on the system, sometimes it does take a relatively long time, but it's not an issue for me. One thing that is annoying is that if I want to make a small change to a cookbook and re-run the Chef client, I can't just make the change in the cache and run it. I have to do the whole process of updating the server.

Incentivized

This rating is specifically for Atlassian's self-help documentation on their website. Often times, it is not robust enough to cover a complex usage of one of their features. Frequently, you can find an answer on the web, but not from Atlassian. Instead, it is usually at a power user group elsewhere on the net.

Incentivized

Support is not good at all. To this day, I have to mail my queries and their support site does not log in for me (me alone). But, upon contacting many times, no one helps with a proper response. Though good thing is, I get a proper response over mail too. But, being informative about the tool and not on the issues faced by users outside of the process to get support should also be addressed equally. Which is currently missing in support.

Incentivized

Support for Chef is easily available for fee or through the open source community as most the issues you will face will have been addressed through the Chef developer community forums. The documentation for Chef is moderate to great and easily readable.

Incentivized

Overall, I am very satisfied with the initial implementation (and the subsequent upgrades and implementations made over the years).

This product has never rose to the level of being an major issue at an executive level. It has quietly and valiantly done it's job for our company!

Incentivized

We chose Atlassian Confluence over SharePoint because it's much more user-friendly and intuitive. Atlassian Confluence makes collaboration and knowledge sharing easier with its simpler interface and better search. While SharePoint can be powerful, it often feels clunky and complex, making it harder for our team to actually use it.

Incentivized

XL release is simpler to configure and deploy to the organization than other change management platforms I have used. That simplicity has minor drawbacks requiring you to fit into a limited set of control methods but that exercise helped us simplify a needlessly onerous process.

Incentivized

We considered the three leading competitors in the field: Chef, Puppet and Ansible. Ansible is a very strong competitor and has a nice degree of flexibility in that it does not require a client install. Instead the configuration is delivered by SSH which is very simple. Puppet seems like it has fallen off the pace of the competition and lacked the strong community offered by Chef. We chose Chef because of the strong support by the company and the dynamic and deep community support.

Incentivized

The pricing seemed inline with our products in this space. Nothing out of the ordinary in contract, term, or pricing structure

Incentivized

This tool is very adaptable. So much so we use it for three completely separate projects, in three very different ways.

Incentivized

The entire professional services team was great to work with. The curriculum was tailored to our specific use cases. The group we worked with were very responsive, listened to our feedback, was very easy to schedule and accommodate. I cannot say enough good things about our professional services experience

Incentivized

• The AI feature which lets me find relevant documents while reading one document is really beneficial.
• Centralising of knowledge systems is one of the key differentiators for large organisations.
• As long as folks keep using Google Docs and Atlassian Confluence, there is going to be a challenge in building a continuum.

Incentivized

• XL release has improved our consistency of release process, removing multiple days worth of manual status checking and coordination.
• XL release has allowed us to increase the number of beta releases we can support due to simplifying our release actions.

Incentivized

• Chef is a good tool for baselining servers. It will be a good ROI when there are huge number of servers. For less number of servers maintaining a master will be an over head.
• One good ROI will be that the Operations Team also gets into agile and DevOps methodologies. Operational teams can start writing scripts/automations to keep their infra more stable and their application stack more reliable.
• Implementation of Chef eliminates the manual mode of doing things and everyone aligns to automation mind set. It helps in change of culture.

Incentivized