When not per tenant you still have this problem, and typically resolve by releasing database migrations separately to the code that uses changes (ensuring backwards compatibility).
I guess per-tenant you would handle similarly but build some tooling to monitor the state of migrations. It might even be easier in some ways, as you might be more able to take table locks when migrating per-tenant.
The lenders will come out alright. Even if the utilities end up being renationalised their debt will be converted into government bonds. The mugs here are the public, which end up paying to service the debt that has been used to issue dividends.
With an ageing nuclear fleet built mostly in the 70s and 80s France has the cleanest electricity of any country in Europe (except those with abundant hydro).
Football Radar | Systems Engineer | London | Remote (UK) | Full-time
We're looking for an experienced Systems Engineer / Site Reliability Engineer to help us deliver high quality software and shape our technical roadmap over the coming years.
The Development department consists of 20 developers across 4 sub-teams: Analysis, Modelling, Systems and Trading. As part of the Systems team, you'll get the opportunity to enhance our DevOps culture, taking our collaboration and automation to the next level. We're on a mission to improve stability and standardisation, and shorten feedback loops in order to make our team more efficient in delivering business value. We're also looking for someone who can help us integrate security considerations into our development process.
With regard to deposit scams, the system we have in the UK works pretty well - the landlord must put the deposit in a government-approved escrow scheme, which then decides any disputes over how much of the deposit should be held back (anecdotally quite fairly).
If the landlord fails to protect your deposit, and does so in what might be considered bad faith, a court will often order them to pay you 3x the deposit as compensation - so they all end up actually doing it.
I guess per-tenant you would handle similarly but build some tooling to monitor the state of migrations. It might even be easier in some ways, as you might be more able to take table locks when migrating per-tenant.