Viewing profile — jkodumal
jkodumal
HN member- Joined
- Thu, Feb 27, 2014, 4:19 AM UTC
- HN karma
- 49
- Public activity
- 22 items
- HN profile
- View on Hacker News ↗
About jkodumal
No profile information was provided.
Recent public activity
-
comment
Comment #29283037
Not quite a Saab 900, but perhaps the Bollinger B-1? https://bollingermotors.com/bollinger-b1/
-
comment
Comment #27977162
We've been using Sleuth at LaunchDarkly as a single pane of glass for all changes going out into production. The addition of DORA metrics is exciting-- as an engineering leader, Ac…
-
comment
Comment #13931419
JSON Patch ( http://jsonpatch.com/ ) also uses it.
-
comment
Comment #13388642
There's VSCO, Fluid, Roofstock, LaunchDarkly, and Uber coming soon. There's probably a few more great companies that I'm forgetting.
-
comment
Comment #12711345
Fun fact-- it was started by one the founders of HipChat.
-
comment
Comment #12466479
That's mostly right. We don't use ES as a primary datastore, though.
-
comment
Comment #12466073
I mentioned this briefly in the article, but we thought about doing something with Lambda + API Gateway. But doing the math, 5k RPS pushed through API Gateway is about $1500 daily …
-
comment
Comment #12465903
We've thought quite a bit about how to make this work as a service. The key to our architecture is that evaluating a feature flag for a user does not involve a remote call. We make…
-
comment
Comment #12465242
We had a lot of operational experience with Mongo from our previous jobs at Atlassian, and started out storing almost everything in Mongo. As we scaled out, we migrated all of our …
-
comment
Comment #12464565
I think it depends on the workload. Serving 4.6k static pages per second, cached on a CDN, is not too difficult. However, handling an analytics workload of 4.6K RPS is a little har…
-
comment
Comment #12464545
I was being cheeky :) Events are stored in DynamoDB. We use mongo for "core" data like accounts, feature flags, etc, but none of the high throughput stuff touches MongoDB.
-
comment
Comment #12220530
For temporary feature flags, we try to clean up as soon as possible. As part of the rollout plan for a new feature, we'll have defined what metrics we're trying to achieve, and onc…
-
comment
Comment #11485738
Of course-- we have a dogfood instance of LaunchDarkly. We use LD as our plan permissioning system (the plans you see on our pricing page are managed by LD). We also use it for ops…
-
comment
Comment #11485729
Our goal is to build a developer-focused platform that gives teams the ability to adopt feature flags as a core part of their dev cycle-- including pretty much all of the use cases…
-
comment
Comment #11485251
We do have some features to help manage the lifecycle of feature flags. For example, we can determine when a flag has been "flipped on" for everyone, and notify you that it's time …
-
comment
Comment #11184854
We've been using DeployHub at LaunchDarkly for a bit now, and it's a great tool to have in our arsenal. The thing I like about it is that it focuses on doing one thing well. Too ma…
-
comment
Comment #10936372
Co-founder of LaunchDarkly here-- we're dropping our startup package to $9 / month in the next week. Come check us out.
-
comment
Comment #10729487
Thanks for the shout-out! One of the cool things about LaunchDarkly is that you can use it out-of-the-box without needing to provision any additional infrastructure. By default, th…
-
comment
Comment #10503809
We do have multiple feature flags in place at once. Our dogfood server (we use LaunchDarkly on LaunchDarkly) has about 30 feature flags going at any given time, and we're a relativ…
-
comment
Comment #10501332
I haven't heard of module flag-driven development-- would love to hear more details. We manage the cleanup issue by defining a "removal branch" that cleans up the feature flag at t…
-
comment
Comment #10500097
CTO of LaunchDarkly here. We kind of embrace it a little bit-- locavore booleans as a service. But the real power behind the idea is not the ifdef piece, it's the idea of dynamic, …
- story