The Future With AMQP
Matthew Arrott considers that messaging is at the heart of distributed computing transforming the network into a destination through process choreography and cooperation.
Matthew Arrott considers that messaging is at the heart of distributed computing transforming the network into a destination through process choreography and cooperation.
In a recent and provocative article for SD Times David Rubinstein emphasizes his opinion that while SOA has gained a lot of momentum as an architectural principle, it might be dead as a term. He quotes analyst Jason Bloomberg, who considers SOA as a bad word. In his opinion, SOA as a technology has already died due to Cloud Computing and the intrinsic complexity of Web services.
Microsoft recently announced RTM release of WCF Data Services 5.0 – this includes several new features to support OData v3 such as Vocabularies, Actions, new Spatial Primitives and several updates to OData libraries.
Jason Bloomberg of ZapThink claimed that cloud-based Business Process Management (BPM) software will be disruptive to those traditional BPM engines that cannot easily move to a cloud delivery model. Instead of describing the value proposition of BPM-in-the-cloud, Bloomberg’s article focused primarily on his assertion that REST-based services are a necessity for any cloudy BPM engine to work.
Article “Purpose Case Management” describes a Case Management method that overarches BPM and Adaptive Case Management. Author reviews several modern movements such as Unstructured BPM, Social BPM, Dynamic BPM, and ACM. The article concludes with a generic method that allows switching between BPM and ACM depending on which one of them is more efficient in an execution context at certain moment.

"Service Design Patterns" catalogs design patterns that cover the entire lifecycle of web services. This book is the latest addition to the Martin Fowler signature series which also contains a section on consumer driven contracts contributed by Ian Robinson. InfoQ talked to Rob Daigneau, the author of the book, regarding various topics related to the core idea behind "Service Design Patterns".

In this IEEE article, authors Stephen Yau and Ho An talk about application development using service-oriented architecture and cloud computing technologies. They also discuss application development challenges like security in a multi-tenant environment, quality-of-service monitoring, and mobile computing.
Sid Anand presents the architecture set in place at LinkedIn and the data infrastructure running Java and Scala apps on top of Oracle, Voldemort, DataBus and Kafka.

Martin Thompson and Michael Barker explain how Intel x86_64 processors and their memory model work along with low-level techniques that help creating lock-free software.

In this interview done by InfoQ's Srini Penchikala, Oleg Zhurakousky talks about the cloud architectures with messaging as the core part of the cloud solutions. He also discusses the Spring Integration and other Spring projects like Spring Roo and Cloud Foundry.
Bob Ippolito talks about building web services with the Erlang-based MochiWeb and the differences to the Yaws web server, the strengths of Erlang and Python, and more.

This is the first edition of what is expected to become a recurring series on InfoQ. The idea behind this minibook is that a number of InfoQ articles and interviews which deal with a particular topic (in this case, REpresentational State Transfer, or REST) are combined together to provide a detailed exploration suitable for both beginners and advanced practitioners.

Composite Software offers a new level of granularity when compared to SaaS (Software as a Service). Composite Software is about enabling "right-sourcing", i.e. move (or keep) arbitrary small or large elements of functionality wherever it is the most cost effective to operate them, not just entire systems. Economically, "right-sourcing" is far more efficient than "outsourcing" and SaaS. The goal of this book is start by understanding today’s software construction processes and technologies and explore why and how it should be evolved to support core composition mechanisms.

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.