What do y'all think is the best stack for a greenfield microservices project? The services will be written in c# or node on .net core. Things change so fast, so I'm peeking my head above the water after a year. We aren't in the cloud yet, but are planning on it, so something portable would be a requirement.

​

API Gateway/Service Registry

---

Ocelot (mature enough?)

Service Fabric (last project was ick)

ServiceStack

Orleans/Akka.net

Microdot (no clue)

Integrate with proven other gateways (Kong, Ureka/Zuul/Traefik/Caddy)

Other? What am I missing?

​

Authentication - Ideally the gateway would already have integration for different providers Windows Auth, OAuth, others and support federation if possible.

Keycloak? do I pay for it

Auth0?, Do the gateways already have support for them?

​

Onto the services

---

Circuit Breaker/Feature Flags

Polly (love this project)

Scientist.net

Other?

​

Data Access

---

What's EF.core like these days? Still generate garbage extents?

Dapper or other microORM

​

Queue/PubSub

---

RabbitMQ or Other?

Use actors instead?

Serialize & compress messages (wire, protobuff, or just leave it json)

​

Configuration

---

Central Configuration Service?

Store config in json files?

Inject into env variables instead, no files?

​

Secrets

---

Seperate secret service? Part of Config Service? Use 3rd party?

Connection Strings

Keys

Certs

Passwords

​

Caching

---

Redis

Something else?

Just use Mongo

​

CI/CD -> into docker for windows

---

VSTS

circle CI

octopus

​

What else? Testability, Automation

Swagger/Swashbuckle/Postman/Insomnia

​

Am I missing something?

​