A pessimistic approach towards SOA seems to prevail in some blogs. But these opinions strike me by surprise. In the industries I am working for - public sector, healthcare and Defense/ public security - SOA is predominant and you will find only rare examples of tenders where SOA is not highlighted as the guiding principle for the whole architecture. SAP's CTO Vishal Sikka has already provided the community with some very helpful insights concerning these discussions.
I just want to add some points from an architect's point of view:
From my point of view it is not the SOA approach itself which should be questioned but the way how we architects sometimes work on SOA. Some of the mistakes that are listed below I have encountered during my SOA projects. Others are based on discussions with other architects and decision makers inside and outside SAP, from customers and from partners. My intention is simple: I want to help to avoid these mistakes in the future and to strengthen the SOA approach which is for me without an alternative.
The Model View ViewModel (MVVM) is an architectural pattern used in software engineering that originated from Microsoft as a specialization of the Presentation Model design pattern
Software architecture links to documentation related to:
System Architecture description
Software Architecture Review and Assessment
4+1 view model of software architecture
In a very direct way, cutting edge Ethernet technology is even starting to have a huge effect on how we view our economic outlook. The New York Stock Exchange recently tapped Juniper Networks, a large network hardware manufacturer, to upgrade their network.
Why is there this great push to run XP apps in W7 XPmode when all apps run fine in XP... Just say "no" to W7 and Vista til there is some important app that won't run in XP !