For our use case, we found the best approach was to clone all of the data to a temporary table with indices and constraints disabled, perform the updates, re-enable indices and constraints, and then replace the production table with the temporary table. This only works if you are able to update your data in bulk, and if some lag time in your updates is OK. This also has the benefit of never locking your production table.
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.
My first thought after reading the headline was that they had been placed under some kind of litigation hold and had to immediately back up all of their data on US customers to comply.
Just baseless speculation; I dont work for Facebook or have an inside source.
Environment variables are the best way to handle feature flags. The 12 factor app provides some guidance for doing it the right way. [0]
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
How does one find these high paying full time remote jobs? Most that I see with salaries listed on weworkremotely, Stack Overflow Jobs and the like top out around $150k.
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.
>(though maybe if marijuana becomes legal nationwide that will no longer be part of the test)
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.
It's code that provisions or configures VMs, containers, cloud resources like RDS, etc. Usually this is accomplished using tools like Terraform, Ansible playbooks, SaltStack, Kubernetes, and the many other similar tools.
Are there a lot of American expat software engineers in the UK? For most people, it would be a steep pay cut to move from the US to anywhere in the EU.
There is lots of truth to this, but it's not that hard to save up for 6 to 24 months of expenses on an engineer's salary, assuming you are living within your means. Dependents complicate the situation, but don't make it impossible.
In my experience using AWS, you can spin up new autoscaled instances pretty quickly. I don't even have a custom AMI, I use a generic image and run startup scripts to kick off my server software. Takes < 3 minutes to spin up a new one and start accepting requests.
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%)
Terrafirm isn't provider neutral. It is just a declarative wrapper for cloud provider APIs. Code using one provider is not easily translated to another.
I do think it's an excellent configuration management and provisioning tool, but Go Cloud solves a different problem.
Has there ever been a high profile early access game that crossed the finish line? It seems like studios usually take the money and run, like Bohemia Interactive with DayZ. Five years and tens/hundreds of millions of dollars in revenue and the game is abandonware.
Simulating millions of users should be well within the capabilities of a company as large as Amazon. Off the shelf load testing tools like Locust can create thousands of fake users with one worker.
What features of Kubernetes are only available for a price? Since Kubernetes is fully open source and self hosted/available from any cloud provider now, how is it crippled?
Thoughts on Nomad after admittedly minimal dabbling: I pushed for using Nomad at my job without success. Managerial perceptions of Kubernetes as "the consensus" is a self-fulfilling prophecy. Nobody wants to pick a technology with a fraction of the buy-in of Kubernetes or be forced into paying boku bucks for an enterprise contract. Hashicorp's insistence on releasing premium closed-source features doesn't work when its biggest competitor is fully free and open.
I found it dead simple to get up and running with Nomad, but it is (perhaps intentionally) missing a lot of features of Kubernetes. For instance, if you want load balancing and auto-scaling, you need to rig it up yourself. In K8s, you set up a service and horizontal pod autoscaling and you're done.
How does this work? Do you work 40 hours compressed into 3/4 days, or do you take a pay cut? Do you find that you are able to be productive for entirety of the 10 or 14 hour days required by a compressed workweek?
>I’ll be on sabbatical from my job. . . and working on building better profiling tools for Ruby (and maybe Python??).
I can't comment on Ruby's profiling stack, but I think that cProfile is a great tool for finding bottlenecks in Python. Usually, I've found that sorting functions by cumulative execution time is sufficient. You can't do flame graphs out-of-the-box, however.
This is ridiculous. It's one thing to claim that 100k is "not enough" if you live in a high cost of living (which is still dubious, considering the median income in NYC is half of that.) If that's not enough for you in Kansas, the fact is that you're living far beyond your means.
I think it's telling that one family cited credit card debt like it's an act of nature instead of a conscious choice. And just because you qualify for a million dollar mortgage doesn't mean you should get one. Spend that big salary on a home near your workplace and sell the $40,000 SUV.
The sooner we wake up from the "dream" of being deep underwater in debt to fund an ecologically and economically unsustainable lifestyle, all the while just a paycheck or two away from complete ruin, the better off we'll be.
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.