Blog

I haven't blogged about releases in a while. For that I am sorry, there have been releases on going, including patches and more features like maintaince mode, de-registration and many more that I have forgotten. There are release notes for them all.

I have improved the testing coverage of the things that are important a lot and have been working with some people using it in large environments to iron out some bugs. But now things are looking good. I have some plans, minor enhancements that I have added issues for but the reverse proxy is where there will be a lot of focus coming.

If anyone wants to dig in and help that would be awesome, any area is welcome but especially these

1. Another provider other than consul, zookeeper or redis? This will help prove out and find now issues around abstracting the provider
2. General help on the reverse proxy, I plan to change to doing this with ASP.NET Core 2.0 and then quickly moving to the abstractions they are building out there.
3. A json comparison engine for Swagger docs for doing API change validation and rules.

Anyway keep hanging around, bring the bug reports, and PR's are always welcome.

Cheers

Tim

The first issue is the stripping of trailing names from the executing assembly should now be fixed with ".Host", ".Library" and so on all removed by default. You can configure the suffixes you would like removed through the ServiceManagerConfig object.

There has been a pretty large refactor of the client libraries. As with any very early API it has taken some time using the library in the real world to gain an understanding of what works and what doesn't. This has shown that the current API for registering your services required a lot of boilerplate code. Also if you wanted to change a single setting it required you to set a lot of settings you would like to leave it as the defaults.

We have started a new documentation site with a new Logo!