We humans are with habits, sometimes bad habits. I am no judge there, but as you may know or not know I am from the Netherlands. In my country we have a TV commercial which is trying to bring their product to the market with the sentence: “you are happy with what you have until […]
For a long period of time, many saw IBM i and its predecessors as old fashioned systems. The number one reason for this was the old school 5250/Green Screen user interface. Number two on that list was monolithic applications written in old school RPG language . I have some thoughts about this later in the article..
Isolation of programs (no, you don’t need containers for this. Similar functions built into IBM i since the time of AS/400)
Operating system that was aimed for multiple users at the same time (IBM i was, Windows and Linux wasn’t)
Branching instead of time sharing operating system (Unique to IBM i and why 80% of all customer are using just 1 or 2 CPU/Cores)
Highly integrated relational database into the Operating System, not an application on top of it.. (Unique to IBM i)
Single level storage… (The data is there for you, when you need it. No need to search for it..)
Openness (IBM i is one of the most open system available on the market today)
Coming back to the reasons why IBM i is seen as un-modern. To start with, 5250 (Green Screens) is not always bad. They are sometimes actually very good. Not as primary way to interact with a business application, for sure. But just like with Windows or Linux, you need something more efficient than a GUI when it comes to do things “under the hood”. And compared to windows and linux terminal, 5250 kicks ass.
Secondly, monolithic applications is not the hottest thing these days. Sure, there are some draw backs with them. But there was also a reason why they were written like that a long time ago. Performance…
The good news though is that you can migrate your monolithic into REST based web services and still stay on the platform. And if you still are stuck with old school RPG, there are convert tools out there to make the code look just like Java or .NET for example..
Sure, there is still the thing called vendor locked in choosing IBM i. But you don’t get away from that which path you choose you follow. The only thing I can promise that this vendor is one you want to be locked in with..
The good thing though, is that IBM i allows you to create smaller chunks of programs just like on any other platforms. Rest based web services works very well today.
Are you looking for content to your own presentation or article around IBM Power Systems? One issue is to find good information as source to the text. Here you can at least find some things to start with.
There is a lot of talk around different container technologies in the IT industry today. But what is this really all about? Please join us in this webinar where Patrik Gunnersten from Conoa (the leading container technologies company in the Nordics) explains containers so even your parents can understand it..
Date: January 28th
Time: 14.00 Central European Time
Agenda
What is a container and how do they differ from an traditional “monolithic” application.
How does containers affect your IT platform, organization and strategy
A short introduction to the ecosystem around containers, this is a whole new world
What is and what isn’t Kubernetes
Containers on IBM Power Systems
Questions & Answers
Speaker:
Patrik Gunnersten
Business Area Manager @Conoa AB Previous IBM Power Expert for 16 years working for IBM. Since 2017 he is an expert on Deep Learning, GPU, Containers and Open Source working for Conoa in Sweden