3 ms·
Changing the language isn't a big deal. You can always go SOA. In fact, even if you stick with the same language and are doing a rewrite, SOA is probably the ri
by andrewvc 13y ago
Changing the language isn't a big deal. You can always go SOA. In fact, even if you stick with the same language and are doing a rewrite, SOA is probably the right answer.
If the original system is THAT bad, the language isn't the problem, it's the architecture, and you should probably refactor it into multiple components which could potentially be multiple different languages.
- jksmith 13y agoThat's my thoughts. Get away from app and more into portal. What still befuddles programmers on large projects is that they still think from the whole front to the whole back and vice versa. MVC hasn't helped this one bit.
- millstone 13y agoIs this train of thought meant to be specific to server-side apps? An example of a large rewrite was the classic Netscape browser engine (to Gecko), and I'm having trouble picturing how a browser engine could use a SOA.
- jksmith 13y agoThat's an interesting example because existence of a thick client allows for SOA on everything else. The browser is the last thick application.
- anvandare 13y agoCorrect me if I'm wrong but isn't SOA just the Unix Philosophy with a focus on networked computers?
- jksmith 13y agoSOA is just the general engineering pattern for providing services to anything that can consume them. The internet is fully realized if all endpoints can both produce and consume services.