BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Enterprise Architecture Content on InfoQ

  • REST and SOAP: When Should I Use Each (or Both)?

    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.

  • A Discussion with Allard Buijze on CQRS with the Axon framework

    The Axon framework is a Java implementation of the Command and Query Responsibility Segregation. InfoQ talked with its creator, Allard Buijze, to find out more.

  • Authorizing Process Access and Execution with JBoss jBPM

    Centralized BPM deployments can greatly benefit from the ability to control access to process definitions and instances ensuring that users can use and monitor only a set of processes that they are authorized for. In this article Boris Lublinsky shows how to extend JBoss jBPM to define and support process access authorization.

  • How HTML5 Web Sockets Interact With Proxy Servers

    Peter Lubbers makes an introduction to HTML5 Web Sockets explaining how they interact with proxy servers, and what proxy configuration or updates are needed for the Web Sockets traffic to go through.

  • SOA Manifesto - 4 Months After

    It is four months since the SOA manifesto was announced; InfoQ interviewed the original author’s and in some cases pulled in their comments on the manifesto from the web to get a broad understanding of the manifesto, as well as provide insight into the goals of the participants, individually and as a whole, and provide transparency to the mechanics involved in putting together such an initiative.

  • SOA Strategy and Spline Tactics

    In this article, Michael Poulin discusses agility-to-market changes that IT can gain using a strategy oriented onto the services. Using concepts of service-orientation as the major construct of the technical product portfolio, accompanied by a techniques he calls Spline Tactics, he examines how businesses can achieve strategic agility.

  • Book Excerpt and Interview: Cloud Computing and SOA Convergence in Your Enterprise: A Step-by-Step Guide

    A new book by David Linthicum, Cloud Computing and SOA Convergence in Your Enterprise: A Step-by-Step Guide, describes how to get the enterprise ready for cloud computing by carefully modeling enterprise data, information services and processes in a service oriented manner to make the transition to providing and consuming cloud services easier.

  • Business SOA Governance

    Business SOA governance is about the long term transformation of IT to align with the business. This means establishing a clear business architecture and then creating a business SOA governance group who will ensure that vision is followed. This is a powerful group and needs to act in the same way as a judiciary. Their role is not to undertake the work but to enforce the boundaries and rules.

  • A Comparison of Spring MVC and JAX-RS

    SpringSource's Rossen Stoyanchev introduces the Spring MVC REST features available in Spring 3 and relates them to JAX-RS, highlighting the similarities and differences between the two programming models.

  • Are You a Software Architect?

    The line between development and architecture is tricky. Some say it's fake, that architecture is an extension of the design process undertaken by developers; others say it's a chasm that can only be crossed by lofty developers who believe you must abstract your abstractions and not worry about implementation details. There's a balance in the middle, but how do you move from one to the other?

  • Using ITIL V3 as a Foundation for SOA Governance

    Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. Based on their perspective, they would be correct since V2 focused more heavily on operational processes rather than service lifecycle. With ITIL V3, the focus of the framework shifted toward what can only be accurately described as service-orientation.

  • Agile and SOA, Hand in Glove?

    Agile is the hand that works in the glove. SOA is the glove, the scope is enterprise wide. Most principles of SOA and Agile are not in conflict. When they are, they keep each other sane. Agile development without a clear vision of the goals and objectives of the company is futile. SOA without a clear vision how to make it real using agile development principles is a waste of time and money.

BT