Confluence vs Microsoft Teams: What are the differences?
Developers describe Confluence as "One place to share, find, and collaborate on information". Capture the knowledge that's too often lost in email inboxes and shared network drives in Confluence instead – where it's easy to find, use, and update. On the other hand, Microsoft Teams is detailed as "Chat-based workspace in Office 365". See content and chat history anytime, including team chats with Skype that are visible to the whole team. Private group chats are available for smaller group conversations.
Confluence and Microsoft Teams are primarily classified as "Project Management" and "Group Chat & Notifications" tools respectively.
Some of the features offered by Confluence are:
On the other hand, Microsoft Teams provides the following key features:
- All your content, tools, people, and conversations are available in the team workspace
- Enjoy built-in access to SharePoint, OneNote, and Skype for Business
- Work on documents right in the app
"Wiki search power" is the primary reason why developers consider Confluence over the competitors, whereas "Free" was stated as the key factor in picking Microsoft Teams.
According to the StackShare community, Confluence has a broader approval, being mentioned in 1172 company stacks & 654 developers stacks; compared to Microsoft Teams, which is listed in 46 company stacks and 33 developer stacks.
We tried out a handful of communication tools including Slack, Microsoft Teams, and Google Hangouts Chat, before settling with Mattermost.
The customisability offered through your server's system console is unrivalled and in some ways overwhelming with the sheer amount of options that you're provided with.
All communication tools share 99% of their UI with each other, and Mattermost is no different, but that's not a bad thing. It also seems to have a less cluttered interface than the others we had tried, although I can't pinpoint the specific design choice that is the reason for this.
The fact that we can have control over all of our data (we're self-hosting it through AWS on a single EC2 instance) is also a great plus which none of the options that we looked into offered.
we were using
slack and at the same time we had a subscription with office 365. after a while we hit the slack free limitation quota. and it got annoying. the search ability was useless in free tier. and more annoying whenever you search, it opens a webpage and doesn't do it in the app.
on mobile there were many cases that I didn't get notification of important discussions. rooms was the way to separate a talk. but it become tedious. each time for a new subject that you wanted to discuss, you needed to add all the team members into a new room. and after a while the room goes silent. you will end up with a tons of not-in-use rooms that you don't want to clean up them for history purposes. also the slack UI for sub discussion is very stupid. if someone forget to check the checkbox to post the subdiscussion in the main discussion thread, other team members even won't notice such discussion is in progress.
we was paying for office 365 and thought why not give the teams a shot. we won't be in worth situation than we are. we moved to teams and we loved it instantly, we had a separate tab aggregated all the files upload. we could reply on other talk. no need of creating a new room. this way room belongs to a team and not a certain topic. our sub discussion was visible to the whole team. enjoyed integration with azure and unlimited history. the best part was integration with outlook. it was a full suit solution. our stats become busy on outlook meeting events. we get weekly analyse. we didn't need to host our wiki seperated. we've created wiki per team. the communication was much more fun.