Interesting Subject post....

Java Consultants...

Great Post on "RoR" Technology.....

Java Web Development Company...

There's definitely something to be said for Resource Oriented Architecture in terms of simplicity but let's move on and start discussing not how simplistic it is when pitted against Service Oriented Architecture but how useful it is. Take a look at the names just to get the basic idea. One is based on what you're trying to provide whether you have it or not and the other is based on what you have, whether that's what your users are looking for or not. It all comes down to basic common sense. Sure ROA may be easier for many programmers to use but does that say more about SOA or about the programmers who need a different program? I think it says more about the latter. After all, just because it's easier to use does NOT mean that it's the correct choice for a programmer. You just need to learn how to use the better systems instead of lowering yourself into a pit by continuously searching for easier to use programs.

As the web continues to gain a well-deserved recognition for being the most prudent choice for a de facto computing platform, the issue of its API is becoming very critical. In this presentation, Alex Bunardzic will argue that Ruby on Rails might be the most optimal API for programming the web. He bases his convictions on the fact that Rails is built upon the Resource-Oriented Architecture (ROA) which has REST as its underpinning. Not only has that architecture emerged as a publicly vetted standard, it's also notable for its radical simplicity (introducing the unbelievably simple inventory of only four verbs!) Compared to the astronomically complex inventory of countless verbs that Service=Oriented Architecture (SOA) demands, ROA is proving to be much easier to program, especially when using Rails.

As the web continues to gain a well-deserved recognition for being the most prudent choice for a de facto computing platform, the issue of its API is becoming very critical. In this presentation, Alex Bunardzic will argue that Ruby on Rails might be the most optimal API for programming the web. He bases his convictions on the fact that Rails is built upon the Resource-Oriented Architecture (ROA) which has REST as its underpinning. Not only has that architecture emerged as a publicly vetted standard, it's also notable for its radical simplicity (introducing the unbelievably simple inventory of only four verbs!) Compared to the astronomically complex inventory of countless verbs that Service=Oriented Architecture (SOA) demands, ROA is proving to be much easier to program, especially when using Rails.

As the web continues to gain a well-deserved recognition for being the most prudent choice for a de facto computing platform, the issue of its API is becoming very critical. In this presentation, Alex Bunardzic will argue that Ruby on Rails might be the most optimal API for programming the web. He bases his convictions on the fact that Rails is built upon the Resource-Oriented Architecture (ROA) which has REST as its underpinning. Not only has that architecture emerged as a publicly vetted standard, it's also notable for its radical simplicity (introducing the unbelievably simple inventory of only four verbs!) Compared to the astronomically complex inventory of countless verbs that Service=Oriented Architecture (SOA) demands, ROA is proving to be much easier to program, especially when using Rails.