Why services needs repositories?

Question

I want to create a library of services in my company.

Both to create a list of apps my managers can select for a newcomer, to link issues, monitor status and dependencies.

The easiest example,

we use Google as SSO, Gmail, Okta, and Confluence.

I would like to create all these apps as services.

1) there is no documentation about best practices for types, I assume, Gmail is an app, and Google SSO is a Capability, but this is my guess... the 'create a service' article completely ignores that topic.

2) in my idea, Okta would be Tier 1, Gmail Tier 2, Google as SSO tier 2, Confluence Tier 2

3) then I would like to connect Confluence, with Google SSO, which then depends on Okta

4) none of these services depends on CI/CD so in theory there is no need for any kind or repository.

How I can build what I want to achieve if my software portfolio is 99.5% based on external services?

Fabian Lim · Answer

Yes. Feel free to contact a solution partner or look me on LinkedIn and we can help you out.

Michal Klucz_u41u44 · Answer

Thank you Fabian,

This makes sense (however is misleading, as the examples given are totally described as 3rd party tools... like, really rarely anyone is designing own payment platform).

But...

1) Asset is just another product. so that is clearly an additional cost.

2) the most frustrating part.. we are a small company, I have two agents.. so I COULD try the free plan, but.. we pay annually, and for the unknown reason the free tier is only available for monthly payment which obviously makes no sense as it's 'free'.

Fabian Lim · Answer

Hi @Michal Klucz

I agree with you there is no clear documentation on best practices.  You don't need to use the repos feature, these are used for devOps teams where they upload code and then you can track changes more efficiently.

I think what you are doing will work.

For many of our clients we ignore the "Services" and we build a new "Application Inventory" in assets separately.  It gives us more flexibility to add more attributes than the predefined ones used in the "Services" Schema.

Regards,

Fabian