😉

ah you talked with my client?

Haha 🙂

we wrote a quite good plan to chop up the current mess into managable chunks that is still a monolith but with all functionality already split up in normal chunks

that would ensure the !option! to move to services (not even microservices) once that is done

Yeah, making it modular is the most important thing for maintainability IMO

true

last week I found a pdf writer in one! of the persistence layer

I did that with a huge monolith in my company. I discovered so many cross cutting concerns, impls calling other impls etc. Just that cleanup to be able to run it as separate modules was worth gold.

Haha, there you have it.

“but that is so easy and close to the database Ron, why would we not?"

I did similar stupid things, because I could, and it was convenient. When you modularize everything, then suddenly it's much harder to do stupid stuff.

Famous Last Words™️

well tomorrow we are going to relinquish all responsibility and withdraw from the architecture meetings as all decisions made there are not executed but withdrawn without any meetings

@edvin I think it has happened beyond microservices. When a new technology or pattern is all the rage, people tend to fit a square peg in a round hole just to use it.

true, I saw this graph some time ago with the cone of disappointment

Absolutely. Java EE has survived all the hype and it's still relevant.

I think cloud programming and microservices are still in the peak

I often ask people >what is running in the cloud?

There is no cloud, it is just someone else's computer.

you read my mind

allthough what netflix does comes close

There is a plugin for Chrome that replaces all occurrences of "The Cloud" with "My Butt". Useful stuff.

@edvin satire plugins FTW!

I was just about to say "someone else's computer" as well.

I think cloud decisions should be rephrased as "A) your computer B) another computer within the company C) Another computer outside the company"

a the famous “private cloud"

@thomasnield Haha, yes indeed