I'm working on a project that is almost literally your example of reducing a relational database to a key value store, despite client applications having complex problem domains to model.
The consequence has been catastrophic data consistency problems and the whole programme rapidly grinding to a halt.
I think the problem is the overly broad definition of 'business logic' that encompasses everything from data integrity to presentation logic.
Or put another way, approximately enough to power 110 of the most powerful supercomputers in the world, the Sunway TaihuLight, that would give a combined performance of 10 exaFLOPS.
Bitcoin replaces one tyranny with one that is far worse.
If it succeeded in displacing existing currencies as you attest, it would amount to an unprecedented and catastrophic redistribution and concentration of wealth.
80% of all bitcoins that can ever exist have been mined and are already owned; this is a monstrous design decision far more unjust than the inflation bitcoin sought to prevent.
Our current corrupt and stinking financial system is far preferable to the neo-feudal world of bitcoin where all spending power is concentrated in the hands of a tiny number of tech overlords who had the sheer good fortune to literally own all the money.
If you don't need real time then why use improbable?
If you want to simulate a new bus route then run an offline simulation using whatever tools you like with as much complexity as you like.
In fact you'd likely want to run your simulation much faster than real time to answer specific questions quickly, like finding traffic or passenger hotspots.
I doubt you'd want to sit there watching virtual buses driving around a 3d city, but rather quickly see heat maps change as you play with parameters.
Do those simulations need to be real time and massively multiplayer?
I don't see the need for this tech in the high fidelity city simulation cited in the linked article: that would much easier to implement as an offline simulation.
Training seems like the most likely usage: eg. disaster response or large scale military scenarios.
I have to agree with the earlier poster that tech is not the limiting factor for massively multiplayer games.
We’re evolving the architecture of a mission-critical justice platform and looking for a hands-on Principal Engineer.
We are looking for a track record of reducing complexity and an appreciation for databases as foundational pillars of correct applications.
We value engineering judgement over specific frameworks—if you’re a great engineer who can ramp up quickly we want to talk.
Apply: https://careers.publicsectorresourcing.co.uk/en_GB/careersma...