Skip to main content

Electoral Load-balancing

I can't help but think that I'd not get away with load-balancing of resources assuming an equal prioritisation of requests as the British political system allows with votes. No doubt the Tories got the most seats and should rightly be charged with forming a government. However,  based on raw votes the distribution is unequal and the system is weighted in favour of the main two parties...  and the emergent SNP! The table below is based on UK elections result data from The Guardian assuming you get the number of seats relative to the number of votes cast.

Suppressing minorities or mitigating extremities? Or a bit of both... It should not though be for the incumbents; and the system is a product of them, to decide. Perhaps our electoral system could do with an updated load-balancing strategy.

of the
Scottish National Party5631+25
Liberal Democrat851-43
Democratic Unionist Party84+4
Sinn Fein440
Plaid Cymru34-1
Social Democratic and Labour Party32+1
Ulster Unionist Party220
UK Independence Party182-81
Trade Unionist and Socialist Coalition01-1
Traditional Unionist Voice000



Popular posts from this blog

An Observation

Much has changed in the past few years, hell, much has changed in the past few weeks, but that’s another story... and I’ve found a little time on my hands in which to tidy things up. The world of non-functionals has never been so important and yet remains irritatingly ignored by so many - in particular by product owners who seem to think NFRs are nothing more than a tech concern. So if your fancy new product collapses when you get get too many users, is that ok? It’s fair that the engineering team should be asking “how many users are we going to get?”,   or “how many failures can we tolerate?” but the only person who can really answer those questions is the product owner.   The dumb answer to these sort of question is “lots!”, or “none!” because at that point you’ve given carte-blanche to the engineering team to over engineer... and that most likely means it’ll take a hell of a lot longer to deliver and/or cost a hell of a lot more to run. The dumb answer is also “only a couple” and “

Inter-microservice Integrity

A central issue in a microservices environment is how to maintain transactional integrity between services. The scenario is fairly simple. Service A performs some operation which persists data and at the same time raises an event or notifies service B of this action. There's a couple of failure scenarios that raise a problem. Firstly, service B could be unavailable. Does service A rollback or unpick the transaction? What if it's already been committed in A? Do you notify the service consumer of a failure and trigger what could be a cascading failure across the entire service network? Or do you accept long term inconsistency between A & B? Secondly, if service B is available but you don't commit in service A before raising the event then you've told B about something that's not committed... What happens if you then try to commit in A and find you can't? Do you now need to have compensating transactions to tell service B "oops, ignore that previous messag

Equifax Data Breach Due to Failure to Install Patches

"the Equifax data compromise was due to their failure to install the security updates provided in a timely manner." Source: MEDIA ALERT: The Apache Software Foundation Confirms Equifax Data Breach Due to Failure to Install Patches Provided for Apache® Struts™ Exploit : The Apache Software Foundation Blog As simple as that apparently. Keep up to date with patching.