This is the best response so far. Session churn creates lots of db activity but lots of it is of low business value. Better to offload to a separate process.
Also session data is often Blobs which db's don't process as efficiently as columnar data.
At last an explanation that makes a bit of sense to me.
>Hopefully they own up to this, and explain what they're going to do to prevent another global-impact process failure
They probably needn't bother, every competent sysadmin from Greenland to New Zealand is probably disabling the autoupdate feature right now, firewalling it off and hatching a plan to get the product off their server estate ASAP.
Marketing budgets for competing product are going to get a bump this quarter probably.
>Crowdstrike runs on MacOS and Linux workstations too.
This is what chills me to the bone, there's loads of these installations worldwide on heterogeneous OSs but with very little oversight of the code. Companies have basically rolled over and stated, 'OK, we trust you'
I'm not usually a fan of strident calls to open source everything, but the source code at least for the channel file parser on all OSs should now be made public so that we can have an oversight of what so many have placed their trust in.
>"they have no reason to surveil boring ordinary individuals."
Tell that to Parsons, Winston Smith's loyal to the Party neighbour who's betrayed by his own child. If surveillance is allowed to become pervasive enough, nobody is safe.
An iterative model which has been up-front loaded with a firm architecture, feature elaboration, a rough development and testing plan, resources allocated and some basic milestones to hit so that upper mgmt. can get an idea when useful stuff might land.
The development _process_ can be as agile-y as you like, so long as the development of features moves incrementally with each iteration towards the desired end-goal.
Also session data is often Blobs which db's don't process as efficiently as columnar data.
reply