Skip to main content

Moving Host Cobol Batches and Monolith Webapps to Cloud and Microservices

Very interesting presentation in Amazon Event "From Mainframe to Microservices - Vanguard's Move to the Cloud". Following parts can be used as Migration Patterns:

Different ways of how to move from Mainframe to Microservices:
  • Re-host
  • Reengineer 
    • Refactor
    • Rewrite
    • Batch job migration
    • Data analytics enablement
    • Data-driven augmentation
  • Re-platform with Linux and Java
  • Repurchase
  • Retire
  • Combination 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
  • 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 asynchronous write.
  • The disadvantage using buffered write is the eventual consistency of the local database.
You shoud take a look at the presentation if you need to move to cloud and you want to do it step by step with Strangler Pattern.


Xplore IT Corp said…

Hey Nice Blog!! Thanks For Sharing!!!Wonderful blog & good post.Its really helpful for me, waiting for a more new post. Keep Blogging!
dot net course training in Coimbatore
inderjeetjacki said…
Mummys Gold Casino - MapyRO
Mapyro 영주 출장샵 of 세종특별자치 출장마사지 the Gold Casino in Las Vegas. The MGM 상주 출장샵 Resorts collection includes hotel 천안 출장마사지 rooms, an auditorium, a theatre, 바카라 사이트 and a bar. Location: Strip. Distance

Popular posts from this blog

GWT Training for Java Developers with GWT Boot

I'm always a fan of " one language solution with Java to rule them all ", here are sofar my opinions about Polyglot Programming: Why "Polyglot Programming" or "Do It Yourself Programming Languages" or "Language Oriented Programming" sucks? Warum Polyglot Programming nicht praxistauglich ist Java als universelle Programmiersprache Until today nobody can excite me about Polyglot Programming. My points are getting another big support after I read the " Rise of Polyglot at Netflix " presentation which says that Polyglot is expensive , also for company in the category of Netflix. At the end of the day we need to be productive . Our applications should have a  high quality standard and the total costs  (TCO) of our software development should be manageable and low . To be able to reach this goal we have Java with Spring Boot or JakartaEE on the server-side which offers REST interfaces. So logically for user interface development