pageald
Joined 9 years ago
Joined 9 years ago
Just baseless speculation; I dont work for Facebook or have an inside source.
Feature flags do introduce complexity, but that can be partially mitigated by having good defaults and deleting flags once they're no longer needed. Even without that, as long as there are good defaults, you won't run into any problems until you have hundreds of flags.
I once worked on a system with tens of thousands of configuration flags that could all be overridden in an inheritance-esque chaining scheme, like Server A inherits regional config Foo which inherits from business unit config Bar, which inherits from three other 5000 line properties files. And naturally, almost none of these properties had defaults, so starting from scratch with a new configuration was impossible, leading to snowballing technical debt from copy pasting old configs. shudders
There are lots of non-remote jobs that pay higher than my current salary, but I don't see that many remote jobs in the $180k to $200k range.
The test isn't going anywhere until there's a reliable field sobriety for weed. Companies don't want employees operating heavy equipment stoned, and unfortunately there's no way to test that somebody smoked in the last day or two, only that they've smoked in the last X weeks/months, depending on their habits.
If that's not fast enough, you can bake an AMI and scale more proactively (e.g. scale when your server is 70% utilized rather than 95%)
I do think it's an excellent configuration management and provisioning tool, but Go Cloud solves a different problem.
I guess Minecraft is one notable exception.
In situations where real-time updates are important, the key is to minimize your indices as much as possible. Read up on heap only tuples (HOT). If that all isn't enough, maybe consider sharding your database.
Never run VACUUM FULL; it locks too aggressively. Let autovacuum do the job.