BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Architecture Content on InfoQ

  • Resource-Oriented Architecture: The Rest of REST

    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.

  • "SOA Governance" Revitalized

    This article by Miko Matsumura discusses why people are pursuing SOA, whether SOA is dead, what SOA Governance is, what the relationship is to SOA itself, how it differs from management, how SOA differs from integration, and why SOA and SOA Governance continue to be significant issues for the Enterprise.

  • Strategic Domain Driven Design with Context Mapping

    Many approaches to object oriented modeling tend not to scale well when the applications grow in size and complexity. Context Mapping technique can be used to manage the complexity in large software development projects. In this article, author Alberto Brandolini discusses the many sides of bounded contexts and how to use them to build a context map to support key decisions in a software project.

  • Classloader Acrobatics: Code Generation with OSGi

    Porting great infrastructure to OSGi often means solving complex classloading problems. This article is dedicated to the frameworks that face the hardest issues in this area: those that do dynamic code generation. Incidentally these are also the coolest frameworks: AOP wrappers, ORM mappers, and service proxy generators are just a few examples.

  • Wonderland Of SOA Governance

    Michael Poulin elaborates on the differences between of governance and management and tries to explore the 'wonderland' of governance in a service-oriented environment. He defines SOA Governance, explores the relationship between governance and enterprise architecture, and discusses accountability and ownership of governance efforts, and how practitioners can instrument SOA governance.

  • Web Service Contract Versioning

    Today we introduce the book “Web Service Contract Design and Versioning for SOA” by Thomas Erl, Anish Karmarkar, Priscilla Walmsley, Hugo Haas, L. Umit Yalcinalp, Canyang Kevin Liu, David Orchard, Andre Tost, James Pasley. More exactly, chapters 20, 21, and 22 of the book addressing the issues related to service contract versioning.

  • Open Cloud Will Make Business SHINE

    William El Kaim describes an Open Cloud Model based on agile principles and driven by an independent user community to define it further. He provides a sketch of a potential Cloud Operating System. He also defines the SHINE principles for transforming IT into BT (Business Technology).

  • Creating and Extending Apache Wicket Web Applications

    Apache Wicket is a powerful, light-weight component-based web application framework with strong separation of presentation and business logic. It enables you to create quality Web 2.0 applications which are easy to test, debug and support.

  • The Elephant in the Room: Using Brain Science to Enhance Working Relationships

    The new brain science (social neuroscience, positive psychology, and imaging techniques) give us tools for understanding and enhancing the ability of men and women to work together. Companies like Deloitte & Touche and IBM have seen financial results including increased retention of women by training their managers to use gender intelligence.

  • A Decade of SOA: Where are we, Where are we Going?

    SOA is 10 years old. InfoQ has gathered Jeff Andres, Eric Ballou, Dave Hollander and William El Kaim, all Enterprise Architects with a long experience in SOA, to share their perspectives on where we are and where we are heading, as part of a virtual panel. They talk about Reuse, Business/IT alignment, Governance,...

  • Building an Agile Team

    Building an agile software development team is not easy. Many managers and team leads hire technically capable people, throw some form of an agile process at the team, and hope that everything works as well as the literature says it does. This approach is not only unrealistic, but is prone to failure. This article will describe the components of a successful team and how we built this team.

  • Practices from “SOA Principles of Service Design” by Thomas Erl

    “SOA Principles of Service Design” by Thomas Erl is an encyclopedia of service design principles needed to build SOA solutions. This article contains three supporting practices taken from the book: Service Profiles, Vocabularies, and Organizational Roles.

BT