Different ways of how to move from Mainframe to Microservices: Re-hostReengineer RefactorRewriteBatch job migrationData analytics enablementData-driven augmentationRe-platform with Linux and JavaRepurchaseRetireCombination of all
This presentation also shows the Cloud Data Architecture at Vanguard. Generally this is how we can build our own database for our micrsoservicew at the cloud and at the same time still use the data from DB2 mainframe on-premise as well.
Advantages using this data architecture: Each microservice reads data from its own local database.DB2 mainframe database can still be used from other Host / Cobol batches.DB scalability
Disadvantages: You cannot write to the database in case you have a network problem. There is an extension to this Cloud Data Architecture by using buffered write or asynch…
After introducing Confluence three times in three different companies I made a template which consists the best practices of how you could structure your IT Division and IT Products within your organisation. Although the three different companies have completely different domains (marketing, payment and environmental services) the stucture of the division and products are quite the same. So if you need to introduce Confluence in your company and you would like to bring the "product team" together, just take a look at WikIT42: http://bit.ly/wikit42en
Recently Manuel and I wrote an article about Low Code / No Code Platform at heise.de: http://bit.ly/LowCodeHeise. It is quite interesting to see the discussions. More than 400 discussion items. It seems that this topic is quite an important topic for developers. Most of them are against or don't trust Low Code / No Code Platform.
The Story of SAP and Lidl (or others, like Deutsche Post and co.) Or How Can You Throw 500 Millions EUR Out of Your Window...
I wrote this article based on following information:
It is hard to believe that after so many years someone still believes to be able to migrate long running and still working system with a naive project style. We have to rethink our way to product instead of project. Moving to #SAP or any other systems means building a product and its long term product team not a project with a clear start and end point.
Introducing SAP is just the same as introducing any other standard software product. Let's take a look at introducing simple #JIRA product in your software development division. You could customize JIRA workflow as complicated as you wish but you shouldn't because you cannot upgrade it later on. If you need to change or extend the process you could write a …