I've only seen one article predicting this. Bankruptcy means different things in different countries, so assuming a restructure of finance and payment of suppliers.
Still interesting to me. Is the AI winter coming (again)?
Years and years ago I worked at an organisation where I was expected to role play Dungeons and Dragons (polystyrene swords and all). When I refused it got tense.
The tipping point happened when I found a bug in the CTO's database code and it would run out of memory (not closing JDBC ResultSets). Then I started finding coins on the floor, I'd just pick them up and hand them in, I knew what was going on.
I didn't last long, glad I was ejected when I was.
Fortune’s Forumla by William Poundstone is an excellent book. Edward Thorpe has most of his papers published too, they’re all good for a read [though I cannot be held responsible if you’re going to beat the dealer at Blackjack, I don’t need Kelly to know how that will turn out :)]
It does ignore fault tolerance yes I agree, because right now I don't need it. When you're bootstrapping this stuff you want to be as lean as you can. The plan is to move to Kafka, which I do use a lot btw, when there's a case to move to that level of throughput. If I had my way now I'd use Kafka, my wallet on the other hand disagrees.
I know the reason for needing three machines for a Kafka cluster. And I'm certainly not pitching Durable Queue as a Kafka alternative unless, as in my case, the throughput will be so low in the initial stages as not to warrant a full Kafka cluster.
I could have run Kafka on a single node.....
The "a bit like Kafka", weak yeah it is but the solution posted presented a fairly quick way to establish a queue and decouple messaging from the running application, that was the whole point.