Describe to me the role of this service. What is the most accurate summation of its responsibilities? Not just of the things it has implemented today, but also factoring in any future features that it would be taking on.
"News & Calendar"
I understand from this that this services will provide all news- and calendar-related data. I do not understand where this data will come from. It could be from its own local database, it could be generating completely random content every time, it could be getting it from Confluence, or it could be getting it from a multitude of external services.
"Confluence connector"
I understand from this that this service will serve the data that comes from Confluence. It may not be returning all data from Confluence, but if we're going to need to fetch additional data from Confluence in the future, this service will be the one providing it.
Pick the name which most accurately reflects the interpretation, because that's exactly what the goal of naming something is: ensuring that the name adequately describes what you can expect from the thing.
we have decided to split them up in a way that there is only ever one service connecting to a different outside service
It seems "Confluence connector" is the correct name then.
"News & Calendar" might coincidentally also be an accurate summation because that's the only data you currently get from Confluence, but there's no guarantee that this will remain correct in the future.
- What happens if you no longer fetch the news from Confluence, but from Google, which (by your own definition) would have to come from a different microservice ("Google connector") which connects to the different external source (Google)?
- What happens if you now also fetch the wiki page content itself from Confluence?
In either case "News & Calendar" will no longer be an accurate name for your microservice, but "Confluence connector" will still be correct.
