Re:How LaunchDarkly Serves Over 4B Feature Flags Daily
by jkodumal on Friday September 09, 2016 @01:54PM
(#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.
Re:How LaunchDarkly Serves Over 4B Feature Flags Daily
by koolba on Friday September 09, 2016 @02:44PM
(#12464980)
> 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.
Curious, why the choice of MongoDB for anything? In my mind "core" data tends to be very structured and require true transactional updates, both of which are cornerstones of a relational database (cough Postgres). Sure it's possible to use MongoDB, but what was the driver for it?
Re:How LaunchDarkly Serves Over 4B Feature Flags Daily
by jkodumal on Friday September 09, 2016 @03:13PM
(#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 high volume data into other stores-- analytics into DynamoDB, searchable data into ElasticSearch, etc.
The last remaining piece is our core data, and there's no strong push to move it out of Mongo.
I suspect this is a joke, but I'm still confused? If 4B things happen every day, how is that finger-toe countable? Does this mean that relatively slowly-changing things like "customer name" are stored in mongo while events etc. are stored elsewhere?