From a business perspective, this means they will not be investing in innovation on the platform anymore. Instead, they will focus their efforts on maintaining the current operations and keeping the lights on.
So biological garbage collection pauses then? skip sleep, and the brain tries to run gc cycles during runtime. Causing attention and performance latency spikes. Evolution wrote the original JVM.
In the situations you mentioned, it doesn't seem the end goal is to be 100% correct about things. Approaching these situations with a curious mindset is key. You may be able to provide a set of options that encompass your understanding of the thing being asked without pinning yourself down to a specific outcome. Once you've allowed folks to understand the potential options, you can tell them you can get back to them with specifics and understanding of implications.
> The pattern also puts an additional burden on the database. Therefore, we should consider the potential performance hit on the database
Massive understatement, one of the downsides that we've found with this pattern is the increase increase in binlog size for our database replication topology. One must be very careful with this pattern as to not create downstream issues with replication delay and such.
The watch deactivates most features and locks as soon as you take it off of your wrist. You'd need to re-enter your password to unlock it. so it is unlikely that throwing it would trigger the feature.
Also from their initial demo, the fall detection uses more input than just a fast falling motion. Apparently humans fall in a specific way that the watch detects
I am not familiar with the ad space, but isn't there a provider/method/framework that would allow people embedding ads on their apps/websites/platforms to select the types or categories of ads they'd be comfortable with?
This is a space that I am deeply interested in, but my team have not found a good pattern around this for MySQL. We currently use a combination of MySQL Slap and Jmeter, but we feel like there are better ways to do this.
What manner of failure would cause such globally deployed and distributed systems to go down like this? I'm very interested to read up on this when they release details of the failure.
If you would like to force enable Electrolysis. Within about:config create a new boolean pref named browser.tabs.remote.force-enable and set it to true.
I don't really see a benefit in updating existing instances in this manner. Launching replacement instances with the new code is much easier for us, and it also provides a super fast means of rollback.
In the past I've thought about using the an ec2-meta-data style endpoint for secrets that would accessible by an agent with some sort of key. that way the application always dynamically requests the secret as oppose to setting it statically at launch.