In this interview, Ryan discusses the components of the Salesforce.com architecture and how they achieve scale. They discuss the different cloud service models and the viewpoint of Salesforce as well as the history of their APIs including Force.com and their decision to move from SOAP API to a Rest-based API.
In late December 2011, Microsoft announced the pre-release of a set of services labeled Windows Azure Service Bus EAI Labs. These enhancements to the existing Windows Azure Service Bus make it easier to connect (cloud) applications through the use of message routing rules, protocol bridging, message transformation services and connectivity to on-premises line of business systems.
A recent paper published by researchers in Germany reveals multiple security vulnerabilities in Amazon Web Services (AWS) and Eucalyptus's SOAP and web interfaces. The flaws are related to architectural choices which impacts multiple users and the overall cloud security.
Web developers today have a myriad of technologies they can choose from; for example, the two approaches for interfacing to the web with web services, namely SOAP and REST. Both approaches work, both have advantages and disadvantages to interfacing to web services, but it is up to the web developer to make the decision of which approach may be best for each particular case.
In this first article in the Resource-Oriented Architecture series, Brian Sletten discusses the REST architecture style, the history of SOA, SOAP and WS-*, the Semantic Web, URLs as identifiers, URIs and URNs, freedom of form, logically-connected late-binding systems, HATEOAS, and the impact of the Semantic Web upon software systems.
Jason Macy explains what are the security threats targeting SOA implementations, the basic requirements for security testing and SOA gateway, attack examples and countermeasures to protect against SQL Injection, DoS, XSD Mutation, and Identity type of attacks.
Stefan Tilkov makes a case for using REST in an enterprise SOA solution showing how to implement tricky features like encapsulation, transactions, stateful communication, reliable messaging, notifications, and security. He also offers advice on how to convince the management to use REST and how to implement it at the enterprise level, including mixing it with WS* when mandatory.
Stefan Tilkov discusses REST (Representational State Transfer) and RESTful web services based upon work he has done for clients of his consultancy. Stefan talks about the shortcomings of the WS-* specs and says he sees little need for WS-* web services any more. Stefan also talks about how web development frameworks are beginning to map to the RESTful model, and the concept of REST and security.
In this interview from QCon San Francisco 2009, Don Box discusses the history of SOAP, XML, XML Schema, RELAX NG, SOAP and WSDL, REPL, opinions on REST, REST at Microsoft, coexistence of REST and WS-*, the M programming language, M and DSLs, M versus XML/XML Schema, Data as XML, and future plans for M and data modeling at Microsoft.
This book argues that for SOA to succeed we must move our thoughts away from the implementation technologies and towards the "what" of the business. Using a straight-forward, pictorially driven, methodology the book explains who to discover what the business services really are and how to construct an overall business service architecture.
