It is not unheard of to encounter a situation in enterprises where microservice architecture has been "too succesful".

There may be even 500 microservices and their number is growing rapidly. The situation might no longer be under control, sometimes even the responsibility for maintaining them is unclear or "shared". It is easier to implement a new microservice than track down who could implement something there.

I have encountered this problem several times, so I started a side project to bring such situations under control. It is still alpha, but first part -- scoping the problem -- is already pretty useful, allowing you to select, visualize and tag etc. microservices.

If anybody is interested, the code is here:

https://github.com/mikko-ahonen/arch-ascent/