You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Working with Confluence API in some add-ons I've noticed that some functions available from "managers" and some from "services".
For example:
CommentService (https://docs.atlassian.com/confluence/6.3.4/com/atlassian/confluence/content/service/CommentService.html) and CommentManager (https://docs.atlassian.com/confluence/6.3.4/com/atlassian/confluence/pages/CommentManager.html)
LabelManager (https://docs.atlassian.com/confluence/6.3.4/com/atlassian/confluence/labels/LabelManager.html) and LabelsService (https://docs.atlassian.com/confluence/6.3.4/com/atlassian/confluence/labels/service/LabelsService.html)
and so on.
What is the point to divide API functions into managers and services? What is the main difference between them?