Viewing profile — thorgaardian

A lot of people will argue that state helps protect against drift, but the real reason I find that you have to have state is to store values that won't be returned a second time an…

Looks awesome! I hadn't had the chance to dive into eBPF yet, but I had hoped someone would be able to use it in a clever way like this! I was digging through the docs and it looks…

Interesting use-case for it. Without prior knowledge of a solution like this I would have suggested you send the webhooks to a queue backed notification system (e.g. SNS backed by …

That last paragraph is an interesting addition I handn’t considered actually, so great answer! While I’d be hesitant to use a 3rd party, hosted solution for this use case, I can al…

What you described in the first sentence is commonly referred to as an API gateway - protecting ingress traffic into a publicly accessible service/app (e.g. Kong, AWS API gateway, …

I’d speculate this is likely a result of one or both of the following: 1. A de-risking strategy. Investing early effectively discounts a future acquisition, but doesn’t go so far a…

This is a problem I've seen at every company I've ever worked at. Everyone starts off thinking they'll have independence, but it's only natural to build on what already exists and …

Confirm.io | Backend Engineer | Boston, MA (ONSITE) | Full-time Confirm.io is an 18 month old, Series B funded SaaS startup providing APIs and SDKs to authenticate state and federa…

Thanks for the suggestion! We're actually using a lot of k8s inspired processes to power the tool, and may end up building on top of k8s as we learn more about how other developers…

I have and personally I'm quite fond of it, but it doesn't quite go far enough imo. Linkerd is very lean and requires virtually zero knowledge of how the underlying service it mana…

Looks just like that. As dstaten said, "just Promise.all but for microservices". I've been contributing to an open-source project called snappi.io - a microservice blueprint that i…

> I think that standardisation should happen at the level of the stack/component (not at the application level). Most application developers don't know enough about specific compon…