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

  • Mule ESB 3.3 Release and CloudHub

    MuleSoft, the company behind Enterprise Service Bus (ESB) product Mule, recently released version 3.3 of the product. The new version's focus is to combine data integration with Mule's application integration capabilities and to deliver a solution for on-premise or cloud integration for developers. InfoQ spoke with Ross Mason and Daniel Feist about the new features and product roadmap.

  • Don't SCIM over your Data Model

    This opinion piece discusses three specific suggestions for improving the SCIM data model: 1. Both the enterprise client and cloud provider should map their internal IDs to a shared External ID, which is the only ID exposed through the API. 2. Multi-valued attributes of a resource must be converted from an array into a dictionary with unique keys. 3. 3 ways to improve the PATCH command

  • A Brave New World of Testing? An Interview with Google's James Whittaker

    Cloud Computing is creating substantial changes to the usual way of doing business. How should organizations leverage this approach to improve testing and quality assurance of software? To get an answer, author Forrest Shull spoke with James Whittaker from Google about cloud computing testing.

  • Cloud Computing Described Through The Analogy of (US) Thanksgiving Dinner

    This article explains Cloud computing using the analogy of US Thanksgiving dinner.

  • Introducing: Restful Objects

    Restful Objects is a public specification of a hypermedia API for domain object models. Version 1.0.0 of the specification has just been released and there are already two open source frameworks that implement the specification - one for the Java platform and one for .NET.

  • Book Review: Java Application Architecture

    Java Application Architecture: Modularity Patterns with Examples using OSGi is Kirk Knoernschild's seminal book on a pattern catalogue for modular systems design. Starting with an overview of the arguments for modularity, the main section in the book introduces eighteen categorised patterns for module development, and concludes with an OSGi example. InfoQ spoke to Kirk to find out more about it.

  • Key Takeaway Points and Lessons Learned from QCon New York 2012

    The first annual QCon New York brought together over 400 team leads, architects and engineering directors. This article summarizes the key takeaways from the event as blogged and tweeted by attendees.

  • Virtual Panel: NoSQL Database Patterns and Polyglot Persistence

    NoSQL database space has different databases that support different data storage patterns. InfoQ spoke with four panelists about the current state of NoSQL adoption, architecture patterns supported by different NoSQL databases, polyglot persistence and security aspects when using NoSQL databases.

  • DevOps:Evolving to Handle Disruption

    With continued concerns regarding IT’s ability to meet the demands of the business in light of disruptive influences and a changing economic landscape DevOps might hold an answer.

  • A Distributed Access Control Architecture for Cloud Computing

    Cloud computing’s multitenancy and virtualization features pose unique security and access control challenges. In this article, authors discuss a distributed architecture based on the principles from security management and software engineering to address cloud computing’s security challenges.

  • CAP Twelve Years Later: How the "Rules" Have Changed

    The CAP theorem asserts that any networked shared-data system can have only two of three desirable properties (Consistency, Availability and Partition Tolerance). In this IEEE article, author Eric Brewer discusses how designers can optimize consistency and availability by explicitly handling partitions, thereby achieving some trade-off of all three.

  • Designing and Developing Cross-Cutting Features

    Every developer has had to integrate with another system, API or component at one point or another. And, often, a business feature must span systems. If you’ve been on a project like this or have one in the pipeline then this article provides strategies to handle the change. Also, this article covers separating system boundaries and what that means for your technical design.

BT