-
Legacy to service oriented architecture ( SOA ) migration
Legacy to service oriented architecture ( SOA ) migration
I would like to start a debate on the topic of migrating – Legacy – applications to SOA. Here are few thoughts to start with
Only minor changes in the code are required (I know it depends on what we mean by legacy code COBOL/4GL/Standard JAVA /C)?
What to look for in your legacy code to identify as a good candidate of being exposed as a web service (being loosely-coupled for example?)
The best way is to convert to one of platforms that support SOA such as .NET and J2EE, if that is feasible?
Any comments/thoughts are welcomed
Similar Threads
-
Replies: 2
Last Post: 04-18-2007, 02:34 AM
-
By cormac in forum ASP.NET
Replies: 0
Last Post: 06-21-2005, 11:01 AM
-
By kgoff@worldnet.att.net in forum .NET
Replies: 0
Last Post: 12-03-2002, 10:54 AM
-
By Tim Romano in forum .NET
Replies: 0
Last Post: 04-19-2001, 07:54 AM
-
By Patrick Martineau in forum VB Classic
Replies: 6
Last Post: 10-18-2000, 10:16 PM
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
Forum Rules
|
Top DevX Stories
Easy Web Services with SQL Server 2005 HTTP Endpoints
JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S.
Wed Yourself to UML with the Power of Associations
Microsoft to Add AJAX Capabilities to ASP.NET
IBM's Cloudscape Versus MySQL
|
Bookmarks