From Mainframes to Microservices Architecture

What if you have to replace a mainframe application processing hundreds of millions of documents per day for a government agency or health-care provider? Is it possible to choose microservices and still achieve the same stability as software that has been optimized continually over a 25-year life span? What are the factors to consider in defining the architecture to meet this challenge?

Join us as we discuss our experiences in the government and health-care industries, successfully using microservices to replace mainframe capabilities. How did we find our answers to these questions?

  • What is the domain and problem to solve? When is it best to apply a microservice pattern, and when is it best to use other architecture patterns?
  • What can we learn from how the mainframe application solved the problem?
  • Where are the seams in the system? How did we use those? What application modernization patterns did we apply where, and why?
  • What quality attributes were required? Could microservices using commodity or cloud platforms really do the job as fast and reliably as the mainframe, while introducing network communications overhead?
  • What DevOps methods and tools did we apply to be confident that the microservices would really do the job and not risk the agency or enterprise mission?

Video producer: http://www.sei.cmu.edu/saturn/

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.