cultvoid

This is not an example of "WHEN Not to do Microservices". It is a perfect demonstration of "HOW not to do Microservices".

The design of the Istio control plane is a dog's breakfast. And because they've screwed up royally with it, they're now loudly proclaiming that it's the fault of microservices and a sudden lurch to a monolith is now the way to go.

This is the kind of thing you can do with a version 0.x. You could get away with doing it with an "Istio 2", but a massive breaking change to an architecture is not OK to do on a version 1.5.

The Istio website gave no warning of this, there's no obvious roadmap published. I'm beginning to think the Istio team are a bunch of amateurs who like fiddling with new toys but don't really care that their software is being used in production environments.

Is Istio safe to use on production systems? As of this announcement, no.

Some famous runner who's name I can't remember and probably didn't exist anyway once said "I can't run 200 miles. But I can run 1 mile - 200 times".

Start from page 1 and iterate from there.

Be careful what you wish for. I have one. Go for dinner with them, they would charge you for the time spent eating the delicious dinner, and afterwards they would write you a letter stating the dinner was delicious. Together with a bill for the letter. Plus a surcharge for providing the "laugh at events of the day" service.

If it is The Hut Group behind this, then they have a track record of this kind of cock up (re the Zavvi article http://www.bbc.co.uk/news/technology-25330615).

You're not a mug, you've an honest person treated badly by an incompetent company.

You would be a mug if you dealt with them again ;-)

Don't be surprised if you haven't heard the end of it. They might well lose the item and then attack you again. If that happens, do not waste any more time or money on them.

Have you kept a record of the courier delivery? Like a collection receipt?

If not, write them a letter, send by recorded delivery, and state that the item was collected and that this is the end of the matter.

They're almost certainly incompetent rather than malicious, so if there's another screw up you can refer them to the letter and then ignore any further correspondence.

£60 is a hell of a lot of money to buy nothing. He doesn't need to do any of that, just arrange to return the item and if Nintendo (or The Hut Group, which is sounds like) screw up the collection, it's their problem. Just keep records of all correspondence.

Don't be daft. Leave it up. As long as the article is truthful, what's the problem? Their appalling treatment of an honest customer should be exposed.

I do think you're totally overthinking this. They made the initial mistake, they need to correct it and at their expense.

They can't do anything to you. Make a "best effort" to return the item and no more. Keep a log of all your correspondence. Don't waste any more than a minimal amount of time on this, certainly don't take days off work etc to wait for couriers.

You overestimate my abilities! I mindfully create a horribly coupled mass of Spaghetti. But it's not anaemic spaghetti ;-)

Exactly this. If you're working on a system with any need of serialization (eg to/from JSon), or presentation on some kind of view tier, or storage in a database, then the frameworks make get/set pairs inevitable, even if you fight tooth and nail not to have them.

(Of course you could avoid the frameworks, but try telling your project managers that).

Behavior based object design, as well as being an endangered species, probably never existed very much in the first place.

I wonder if Java's popularity was partly due to people being able to appear to do OO whilst actually implementing "code acting on data" systems. You got the warm OO glow without the hard work of doing any behavior driven design.

This is correct. JavaBeans were a bad solution to a problem. It was Swing (or was it AWT then?) that needed it first, so that tool builders could allow widgets to have their properties customised. So the vile JavaBean conventions took hold.

I only quibble on the "mindlessly" part. I will never add a get/set in a class if it isn't needed. But invariably, in a Java project, some library somewhere insists that I have them. So eventually I find I've reluctantly added them.

Sometimes you can get away with leaving them private, sometimes not. It's a pain in the neck and like many things in Java, it should have been sorted out years ago.

Indeed. Paid advertising has been a busted flush for many years now.

I'm still not sure the theoretical consultants you've listed would be "good" as such. They'll just have a massive budget they can use to blow the competition away.

I'll rephrase it as: The "good ones" would be working in a completely different field where their talent actually provides some value to the world.

In my experience, hiring a marketing/adwords contractor is the very easiest way to transfer cash out of your business and into somebody else's business, with no discernible value gained.

I'm sure there are some hotshot marketing/adwords contractors out there...and unicorns probably exist also.