fabio VS CoreFX

After some research and testing, I landed on using Consul and Fabio as the demo infrastructure. Of course, there is a myriad of other options to accomplish this task, but because of the low configuration and ease of use, I was impressed with this pairing. Both projects are mature and well-supported, and very flexible--just because you can run them with low configuration, doesn't mean you have to. I wanted to keep this demo constrained, but the exercise did get me excited about exploring things further: circuit breakers, traffic splitting, and more complex service meshes.

Sniffing the SNI from the underlying TCP connection is the proper way to do this.

a couple examples I know of(only know go ones of the top of my head):

https://github.com/fabiolb/fabio/blob/master/proxy/tcp/tls_c...

HAProxy, Traefik, FabioLB, gobetween, and F5 BIG-IP also support native integrations with Consul for service discovery / service mesh.

Check out https://github.com/fabiolb/fabio instead of traefik, it's 100x simpler and "just works". Traefik... I don't like traefik. Fabio is as simpler than traefik in the same way that the hashistack is simpler than k8s.

I use Hashicorp Consul and Hashicorp Nomad for service discovery and task scheduling respectively, with wesher for my internal private management network that Consul, Nomad, etc run on to protect the management interfaces. Fabio bridges the gap between the wesher wireguard VPN and the rest of my home network.

How do you feel about using Fabio (https://github.com/fabiolb/fabio) - in addition to/or replacement for traefik?

https://github.com/dotnet/corefx/pull/28278

System.Buffers v4.0.3.0 / v4.6.28619.01 @BuiltBy: dlab14-DDVSOWINAGE069 @Branch: release/2.1 @SrcCode: https://github.com/dotnet/corefx/tree/7601f4f6225089ffb291dc7d58293c7bbf5c5d4f / v4.6.28619.01

You’re right. Thanks for correcting me. The logic of applying the predicate for the two are inversions of each other, and they are even implemented in the same file: AnyAll.cs.

- EF Core is not MSSQL first. EF Core is an abstraction layer and is in no way tied to Sql Server. In fact, Microsoft's own getting started tutorial uses Sqlite (1). I've personally used the Postgres drivers in production and they are as good/production-ready as Microsoft's SQL library for EF Core.

- "Many libraries ship with two implementations..." I've yet to come across these "many" libraries in the 5 years since I've been building services with .NET Core.

"The community is really culty" - I'm not sure where this is coming from. It's hard to refute such vague criticisms.

- "It's practically open source in name only" - Here is the base class library source: https://github.com/dotnet/corefx/releases

1. https://docs.microsoft.com/en-us/ef/core/get-started/overvie...

Dotnet foundation publishes their C# coding style along with an editorconfig and some tooling to support it.

I created the bug report on GitHub. After that, the .NET development team fixed some code fragments described in the article. Among them - the errors with interpolated strings. The corresponding pull request.