Eureka VS InAppSettingsKit

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.

Granted, this is not SwiftUI, but check out InAppSettingsKit - I use this library in almost all my apps. With IASK, you only write plist entries for common settings fields, and everything else is easily configurable.

I was wondering, do you usually write your own code to implement in-app Settings page, or you make good use of third party library like https://github.com/futuretap/InAppSettingsKit to implement such?