swift-tagged VS Eureka

A few dependencies I'm using everywhere are https://github.com/pointfreeco/swift-identified-collections and https://github.com/pointfreeco/swift-tagged.

I’ve done something similar (not including rockets, don’t worry!) in Swift with its typealias feature. Thankfully there is a way to actually force compiler errors in such situations with something like https://github.com/pointfreeco/swift-tagged

And then your disagreement disappears. For more info: https://github.com/pointfreeco/swift-tagged

I’m on mobile right now so I’ll read in detail later. For now, what does this offer beyond some existing phantom type solutions like https://github.com/pointfreeco/swift-tagged

I like Tagged https://github.com/pointfreeco/swift-tagged

I was setting up microservices based on Netflix Eureka and experimenting on top of spring-cloud and after weeks of research and development the question rose!

The closest thing I've found is Netflix's Eureka, though its very Java oriented and I found hard to use.

There's an open issue documenting this problem on Spring Cloud Netflix and Netflix Eureka.

if you want to get more knowledge of the services, eureka etc, you can debug it. but I will digest you use the library instead of the annotations: https://github.com/Netflix/eureka

Service discovery — Traditionally provided by platforms like Netflix Eureka or Consul.

With multiple services running, it’s hard to discover where they’re located. The dependencies between multiple services are not always easily found, and new services may be deployed with a new dependency on an older service. Those services can be deployed anywhere in the infrastructure, so what you need is a Service Discovery service. There are plenty available, such as Netflix Eureka or HashiCorp Consul.