Question 1

How do I set up CondenserDotNet with Docker for containerized microservices?

Accepted Answer

You'll need to run Consul in a separate container for service discovery, then configure CondenserDotNet to connect via its client library. The lightweight design makes it easy to containerize, but detailed Docker examples are sparse in the docs.

Question 2

CondenserDotNet vs Ocelot: which is better for a .NET API gateway?

Accepted Answer

CondenserDotNet is lighter and tightly integrated with Consul, ideal for simple, Consul-based setups. Ocelot offers more features out of the box like authentication and routing but can be heavier and less focused on Consul.

Question 3

Does CondenserDotNet support JWT authentication or OAuth?

Accepted Answer

No, it doesn't include built-in authentication mechanisms. You'll need to implement custom middleware or use an external identity provider, adding complexity to your security layer.

Question 4

Can I use CondenserDotNet without Consul, say with Kubernetes service discovery?

Accepted Answer

No, it's designed specifically for Consul integration. For Kubernetes, you'd need to adapt or use alternative tools like Envoy or a Kubernetes-native ingress controller.

Question 5

How to handle SSL/TLS termination in CondenserDotNet?

Accepted Answer

It relies on Kestrel for SSL, so you can configure certificates directly. For production, you might need to pair it with a reverse proxy like Nginx for advanced TLS management.

Question 6

What are the performance benchmarks for CondenserDotNet under high load?

Accepted Answer

Performance is tied to Kestrel's efficiency, which is high, but real-world benchmarks are not provided in the docs. Testing in your environment is recommended due to variability in microservices traffic.

CondenserDotNet

What is CondenserDotNet?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions