BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Patterns Content on InfoQ

  • Greg Young: Scheduling for Things to Happen in the Future

    Delay of message sending into the future is a very powerful pattern and is often the preferable way of dealing with temporal problems compared to batch job that will run a query on the domain model and update some aggregates, Greg Young explained at the recent DDD Exchange conference in London.

  • Clean and Representative Models are Key to Performance

    High performance systems is about clean and representative models, the code doesn't have to be ugly, obscure and hard to read, Martin Thompson stated at the recent DDD Exchange conference in London.

  • Eric Evans: Challenging the Fundamental Assumptions of DDD

    We need to constantly challenge DDD to find the weak spots, Eric Evans stated in his keynote at DDD Exchange yesterday in London when walking through and challenging his own fundamental assumptions of Domain-Driven Design.

  • Kin Lane on How API Commons Will Shape the Future of Web APIs

    InfoQ asked Kin Lane, the leading API evangelist, to share his views on open API designs and on what led him to launch the API Commons initiative with Steven Wilmott. He explains how translation and interoperability between the emerging API description languages matters, and how an open internet culture should prevent API Commons from making the same mistakes as past initiatives like UDDI.

  • SOLID Design Principles and Other Patterns Revisited For .NET

    Andras Nemes, a web developer on the .NET platform, is doing a series of blog posts on the SOLID design principles and other design patterns he has found interesting in object-oriented programming and design, currently on D in SOLID, the Dependency Inversion Principle. Earlier he has among other patterns covered Command, Builder, Visitor, Bridge and Observer.

  • Build Simplicity into a System with Simple Event-Driven Components

    Use events for interactions between small business components to bring simplicity to a system’s architecture, Russ Miles suggests in a recent presentation about simple event-driven components, as a follow-up on his talk a month earlier where he laid the architectural ground for his ideas about simplicity.

  • Amazon Provides Simple Workflow Service Recipes

    A new Amazon whitepaper provides a set of commonly used programming patterns that can be used in application's decider logic to tell SWF how to coordinate the application's work.

  • ECMAScript 5: What’s New in JavaScript Programming

    ECMAScript 5 was standardized in late 2009 but only recently has it has started showing up in browsers. It supersedes the 3rd edition, which was ratified in 1999. ECMAScript 5 is actually two languages, ES5/Default and ES5/Strict. Future versions are going to be built on top of ES5/Strict and it is recommended that the default version be avoided.

  • Notes from OOP 2011 Conference in Munich

    The OOP conference (Object Oriented Programming) was held in Munich, Germany, from 24th to 28th January 2011 with “Business Impact through Mastering Change” as its general motto. Despite of its name, the OOP represents one of the largest and long-lasting events on the general field of software engineering.

  • Implementing Partial Updates In RESTful Services

    Alex Scordellis posted an article on how the interaction of a client and a service can be modeled and designed for updating partial resources. It appears that it is easily solved if we model the resources appropriately. Often times just thinking of resources as entities that support CRUD is the problem and modeling resources as “resources” and the services they offer.

  • Parallel Programming with Microsoft .NET

    The patterns&practices team has released Parallel Programming with Microsoft .NET, a book containing guidance for writing parallel programs for .NET. In essence the book contains 6 design patterns for parallel programming accompanied by code samples.

  • SOA Anti-Principles?

    Much has been written about SOA Patterns and Anti-Patterns over the years, and while SOA Principles are well defined and documented, their Anti-Principles are typically ignored or overlooked. Steve Jones discusses the need for more effort to be put into anti-patterns and starts with a few of his own.

  • GET-only REST Integration Patterns Blur The Line Between Synchronization And Integration

    Duncan Cragg explains his idea/pattern for a purely GET based REST integration pattern, which turns out to be very similar to the vision of Microsoft's FeedSync Specification.

  • Enabling the Last Responsible Moment in Deployment

    An interesting question can be asked during a design decision: "Does this approach create a commitment" rather than "is this the right design?". A conversation on the KanbanDev Yahoo! group explores this question, different approaches to implement an effective answer, and the benefits to be reaped by this approach.

  • Article: Introduction to Data Services

    This short article by Vijay Narayanan begins with a general description of data services and why they are an integral part of any SOA architecture and then explores several aspects of data services including: a definition of need, rationale and benefits, scope, development, and consumption patterns.

BT