J2EE Migration Strategies
| |
|
Typical Migration Strategy
|
Typical gains seen after migration |
|
Use-Cases - Detailed analysis of key use cases provides revalidation of entire business process.
|
Flushes out missing pieces as well as allows for modifications to existing processes. |
| JAAS Migration - Authentication and Authorization Layer - Migrated to ASP.NET Authentication Providers |
Simple and extremely flexible design allowing various sources of authentication (Forms, Passport etc.) as well as different roles based
mechanisms for authorization. |
|
JSP Migration - Migration to front-end ASP.NET forms corresponding to JSP forms.
|
Enhanced request processing features including asynchronous page execution, advanced caching options and tighter web-server integration (leading to significant performance gains). Rich
array of user controls built into the .NET runtime allows for advanced user interfaces - without compromising performance. |
|
Servlet Migration - Migrate to code-behind (c# or vb.net)for each migrated JSP.
|
Leverage the full power of the underlying .NET runtime in the code-behind for each ASP.NET page. |
| Entity Beans (EJBs) Migration - Migrated to .NET serviced components (Enterprise Services) |
Serviced components are much simpler to code and to manage than EJBs. They provide equivalent functionality - and better peformance (typically). |
| Session Management - Migrated to ASP.NET sessions - either in-memory or in an external database (for clustered web-servers).
|
Better session handling leads to quicker response times - and a high volume of simultaneous user-sessions.
|
|
JNDI Providers - Migrated to ADO.NET and LDAP providers |
Harness the full power of ADO.NET - leading to connection-less in-memory datasets, advanced data-caching and paging capabilities built into the framework. |
| High-Availability, Clustering - Migrated to clustered IIS servers - along with ASP.NET runtimes (and possibly clustered databases) |
Typically - better performance at a lower TPS (Transactions Per Second) cost. |
| Unit Tests, Automated Build Process - Migrated to NUnit (or MBUnit) tests in .NET, automated builds using msbuild, nant and other tools.
|
Easier maintenance of migrated application. Quicker turnaround on changes due to agile code-base. |