Many of our customers face the same challenge. They deal with server-side infrastructure that needs to be migrated to something supportable such as a TomEE or Tomcat, but finding the time to fit a risky migration into a busy production schedule can be a real challenge. Just deciding to migrate to a new technology isn’t enough, you have to figure out a realistic path that involves the least amount of disruption to your business. Tomitribe can help you identify the most efficient route for your migration; we’ve walked this particular trail a million times and we can help you anticipate the obstacles and minimize any surprises.
Whether you are considering an immediate switch to TomEE or a more gradual migration toward a new technology stack, Tomitribe can help. Our experts have experience in the following areas:
- Assessing Migration Effort Required
- Preparing an Application for Migration
- Implementing a Migration to TomEE or Tomcat
- Migrating Development Environments to Keep Your Developers Productive
- Migrating Build and Release Scripts to Work with New Technology
- Migrating Production Environments to Minimize Downtime
- Measuring Application Performance Before and After a Migration
- Post-migration Personnel Support including Documentation and On-site Training Services
One Does Not Simply Upgrade a Critical Application
Just like you wouldn’t dive into a pool until you knew how deep it was, you shouldn’t commit your department’s resources to an upgrade until you understand exactly how much effort is involved and what the risks are. Our consultants understand that an assessment is more than just looking at some architecture diagrams and talking about new technologies. Our assessment process is a hands-on effort to measure your codebase and figure out if there are any obstacles to a successful migration as well as opportunities for greater efficiency.
Only Migrate What You Use
One example of an opportunity for greater efficiency is the identification of unused code. We work with large codebases with thousands (or tens of thousands) of classes. Applications at this scale often contain a decade’s worth of code written by a team that has long since moved on to other problems. Tomitribe’s migration specialists sometimes suggest running several diagnostic procedures in production to help identify any code in your project that may be unused. Cutting down on the size of code being migrated to a new platform and only migrating applications that are actively used is a common-sense step that can save real time and effort.
Our consultants understand that a complex migration can often involve a set of preparatory steps on your current stack. Instead of just throwing your application on a new application server, it often makes sense to upgrade in place and address known compatibility issues on your current stack to minimize the amount of effort and downtime required for a migration effort. For example, if you are using popular frameworks it will often make sense to upgrade your existing systems to the latest versions of these components before moving to a new application server.
What We’re Not: All or Nothing
Other server-side application infrastructure vendors may push you to adopt an entire suite of related tools. Tomitribe is not one of those companies that wants to lead you into a walled garden of lock-in and limited choice. On the contrary, we’re convinced that the strength of Java EE is standardization and choice and our Prime Directive is to support the needs of the customer with the technologies we’ve developed. If this means moving your architecture, piecemeal, to Tomcat 7 within an existing application server or migrating select portions of your technology stack to use the parts of TomEE that make sense for you, we’re ready.
A few of our customers ask us to help them migrate portions of an architecture to TomEE-related technologies running on other application servers. While we often convert these customers to TomEE users once they understand the benefits of our software, we’re not that overbearing vendor that is trying to sell you the whole package. Don’t get us wrong, we think TomEE’s the right choice for your architecture, but we’re not going to push our technology for technology’s sake. We’re going to assess your application and your architecture objectively and come up with targeted recommendations for how we can use our knowledge of both Tomcat and TomEE to improve your applications and architectures.