Taking the Complexity Out of Service Discovery
What do you like best?
Everything is controlled from a single SDK. You can register all your microservices through the sdk and access them from any layers of orchestration without having to hardcode or use a database table
What do you dislike?
I feel like it might be a little easy to break microservice barriers with something like this. It might end up making some hard references unintentionally if the developer isn't careful.
Also, it is not currently available in the GovCloud, so if you're software is there, you will have to wait.
Recommendations to others considering the product:
There's no need to rewrite another service discovery module. Just register your microservices and any important information with CloudMap and use that in your orchestration layer.
What problems are you solving with the product? What benefits have you realized?
The primary use case I have is service discovery. I can use it at an orchestration layer for how to contact my microservices without having to pass in static values on startup to a container or pass in environment variables to a serverless function.
I have also used it for tracking business events. When you don't fire things off using something like SNS, it's good to keep a business event repository for your application. CloudMap works perfectly for tracking things across microservices like that.