For many software modernization projects, it’s all about learning to love, lift, and shift. No, wait. It’s all about learning to love lift and shift. The basic idea behind lift and shift is to modernize how an existing application is packaged and deployed. Because it’s not about rewriting the application itself, lift and shift is typically quick to implement.
Modern development environments rely on containers for packaging and deployment. A modern environment also uses a continuous integration / continuous deployment (CI/CD) system that automatically builds, tests, and deploys an application whenever its source code changes.
Continue reading “Modernize your application deployment with Lift and Shift”
[In case you aren’t following the Red Hat JBoss Middleware blog, we are reposting this article on developers.redhat.com.]
Red Hat Application Migration Toolkit (RHAMT) 4.1.0 has been released, and with it a new feature that I’d like to highlight in this article—Technology Reports.
If you’re not familiar with RHAMT, check out my previous article that introduces RHAMT and describes how you can use it to help with migration existing applications to a modern application platform by analyzing your code base.
This new feature in RHAMT provides an aggregate listing of the technologies used, grouped by function, for the analyzed applications. It shows how the technologies are distributed. After analysis has been performed, using this report hundreds of applications can be quickly compared. In addition, the size, number of libraries, and story point totals of each application are displayed, allowing you to quickly determine each application’s type from a single report, for example:
Continue reading “Announcing Red Hat Application Migration Toolkit 4.1.0: Now with technical reports”
Christian Posta, Chief Architect at Red Hat, presented the story of a fictitious company1 moving a monolithic application to microservices.
When considering risk, we think we know the bad things that can happen and the probabilities of those bad things actually happening. Christian defines a monolith as a large application developed over many years by different teams that delivers proven business value while being very difficult to update and maintain. Its architecture, elegant at one point, has eroded over time. That makes it difficult to assess the risk of migrating a monolith.
Continue reading “Red Hat Summit: Lowering the risk of monolith to microservices”