QCon SF Keynote: Techie VC's Talk About Trends & Opportunities
Kevin Efrusy and Salil Deshpande talk about what makes a business successful or not, presenting three actual cases they have been involved with: Hyperic, G2One, SpringSource.
Tracking change and innovation in the enterprise software development community
Posted by Miko Matsumura on Aug 15, 2006
Stefan Tilkov on his blog has produced a useful roll call of REST vs SOAP/WS style bloggers
When designing SOA, it's important to consider appropriate architectural style--and themes from REST or from the Web Services community may be applicable depending on the requirement set. It's incumbent on architects to understand the advantages and disadvantages of both styles to better apply the techniques. This list of bloggers is very useful as a tool for exploring these styles. In particular, if you see yourself in one of these camps, it may be useful to peruse the "other" camp's blogs to gain an understanding of the benefits of such approaches.
Web Services/WS-* supporters (10)
REST supporters (15)
Supporting both (15)
Free $40 SOA Demystified Book Offer
Comparing WebLogic, WebSphere, Oracle, and Open Source Application Servers
Intel® SOA Expressway Performance Comparison to IBM® DataPower XI50
The XACML Enabled Gateway -- The entrance to a New SOA Ecosystem
As for sticking to one approach and standard, if REST had come first and done all the leg work around policy and security then that would be great too. But things like 802.11x and the US phone networks surely teach us that its much better to agree on a standard than have lots of twisty standards all different (which was what I blogged about a while back).
IT is too obsessed with the next best thing, rather than just making do and using what is "good enough". We are the Golgafrinchans never getting anywhere because we argue what colour the wheel should be. Technical discussions like SOAP v REST add nothing to the debate as to how IT will better deliver business solutions that are maintainable, flexible and most importantly look like the business rather than a series of techy acronymns.
It could be interesting to build a list of REST-ian books and SOAP books. Or at least non SOAP books. I find Dirk Krafzig's Enterprise SOA: Service-Oriented Architecture Best Practices a non SOAP book, on the other hand Thomas Erl's Service-Oriented Architecture: Concepts, Technology, and Design is too SOAPy to my taste.
Javier
Kevin Efrusy and Salil Deshpande talk about what makes a business successful or not, presenting three actual cases they have been involved with: Hyperic, G2One, SpringSource.
InfoQ talks to Mark Fisher, project lead for the Spring Integration project, about the framework.
Peter Lubbers explains in this article how HTML5 Web Sockets interact with proxy servers, and what proxy configuration or updates are needed for the Web Sockets traffic to go through.
Neal Ford shows what ThoughtWorks learned from scaling Rails development: infrastructure, testing, messaging, optimization, performance.
Stuart Halloway discusses Clojure and functional programing on the JVM in depth, and touches on the uses of a number of other modern JVM languages including JRuby, Groovy, Scala and Haskell.
Oren Teich and Blake Mizerany talk about the technology behind Heroku and the benefits of the new add-on system.
Chris Riley presents security issues threatening service based systems, examining security threats, presenting measures to reduce the risks, and mentioning available security frameworks.
This talk investigates technical issues encountered when moving to an Agile process.
2 comments
Watch Thread Reply