Battling new technologies with old operation teams

Nowadays, I could see the same pattern on several customers I interact with. All companies and all managers wants to be on the technology wave, they want to use the same cool technologies they could read on the specialised news. The world is talking about containers, ok, I want containers in my architecture. The world is talking about Streaming Analytics, ok I’d like it.

Don’t get me wrong, I think that’s great and cool, the idea to innovate is the only way to keep growing and to move forward, but the problem comes on the daily basis.

“Who is going to manage that platform?” — This is a common question I usually ask to my customers.
“No problem”, they say. “We have an Operation Team we use to manage all our products from our architecture. “

And here the problem begins, if you try to explain how to manage a new platform to an old operation team, who is the not that never has hear some of this sentences?:

* This is too complicated.
* On my previous product everything was more stable, and I only need to follow this procedure.
* A lot of knowledge is needed to manage this product/platform.
* How do you expect that I learn all these only to manage this platform?

In my experience, the operation teams never has been very skilled or experienced. Usually the companies to keep a low rate for this teams try to keep the low skilled profiles and the new joiners on this teams. This wasn’t a problem when you need to manage a J2EE Server or product from the nineties when you only have a monologic application, but how is possible to keep that approach with the new platforms?

The new platforms are complex. That’s a reality. No, the new platforms from this specific vendors are complex, no. Everything done today is complex because it has to be. Because there is no “easy way” to meet all the requirements a company has. So, you need to live with that. T

he same way you don’t use your old mechanic from the sixties to fix your Telsa S model, or you don’t use your typewriter fixer to fix your new MacBook Pro, you shouldn’t use your old operation team to manage the new platforms.

You need new people or maybe not, but at least you need skilled people, people that know the platform, people with deep knowledge. Probably the members that you are not going to need are the low-skilled because todays the kind of work they performed nowadays is done by scripts and automated approaches. You cannot fight today with yesterday’s tool.




PSG Senior Architect at TIBCO Software with a focus on Cloud Development, Event Processing and Enterprise Integration

Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Alex Vazquez

Alex Vazquez

PSG Senior Architect at TIBCO Software with a focus on Cloud Development, Event Processing and Enterprise Integration

More from Medium

A Disposable Local Test Environment is Essential for DevOps / SysAdmin

This week in DevOps #52 — GitOps Issue #34

Cloud-Native Journey Part 3: Distribution and Rollout

👨🏼‍🔬 > 🥷🏼 | UpSkillin’ the Dev in DevOps