Re:Show HN: Caddy 2
by mholt on Monday May 04, 2020 @09:19PM
(#23075359)
> Was it influenced by Envoy?
Not really -- it was more like, I sat down and thought about it: "I want to be able to change ANYTHING about my server using a simple REST endpoint. Hmm..." and then I remembered that JSON can be traversed using path-like notation. I'm not the first to implement this kind of API, but it wasn't a borrowed design. It's elegant as heck though. Every time I use it, I'm like "Ahhh that felt nice."
> Are there any influences/overlap with Envoy?
Probably, but I don't use Envoy. I'm pretty confident that Caddy 2 is capable of doing anything Envoy can do (with the added benefit of memory safety) -- just gotta write modules for it, maybe with some extension to the core to expose surface for those modules to hook into, but shouldn't be too hard to do that.
> Is Caddy overlapping in the space of Envoy in any notable way?
Yeah I think so; it's a greatly flexible reverse/sidecar proxy.
Not really -- it was more like, I sat down and thought about it: "I want to be able to change ANYTHING about my server using a simple REST endpoint. Hmm..." and then I remembered that JSON can be traversed using path-like notation. I'm not the first to implement this kind of API, but it wasn't a borrowed design. It's elegant as heck though. Every time I use it, I'm like "Ahhh that felt nice."
> Are there any influences/overlap with Envoy?
Probably, but I don't use Envoy. I'm pretty confident that Caddy 2 is capable of doing anything Envoy can do (with the added benefit of memory safety) -- just gotta write modules for it, maybe with some extension to the core to expose surface for those modules to hook into, but shouldn't be too hard to do that.
> Is Caddy overlapping in the space of Envoy in any notable way?
Yeah I think so; it's a greatly flexible reverse/sidecar proxy.
I hope you enjoy using it!