Earlier this year, Google and SpringSource announced that they were co-operating on a standard set of annotations to be used for dependency injection which were proposed via JSR-330. These annotations didn't line up with those proposed for JSR-299, which generated controversy that has now been resolved, with JSR-299 adopting the JSR-330 annotations and both moving forward to be part of Java EE 6.
A new Tech Ed presentation by Simon Guest defines a set of patterns for moving applications to the cloud and discusses implementation of these patterns using Windows Azure
Erik Meijer and Wes Dyer have created the .NET Reactive Framework (Rx), the mathematical dual of LINQ to Objects, allowing programmers to use LINQ over events. Erik and Brian Beckman demonstrate that IObservable is a continuation monad.
Purpose and intent are just as important as skill in effective software development. Skill allows you to deliver value in difficult technical circumstances. Clear purpose and positive intent allow you to deliver value in difficult social and business circumstances. Kent Beck shares his design technique which involves both intent and a small set of strategies he uses when designing.
Guice, a lightweight Java dependency injection framework created by Google, recently released version 2.0. InfoQ spoke with Google Developer Team member Jesse Wilson to learn more about this release and what capabilities it adds to Guice.
ODBMS.ORG has added persistence patterns to its collection of resources for educators, students, professionals, and open source practitioners. Three pattern collections comprise the initial offering in this area. A Best Persistence Pattern Award, is planned for any pattern submitted prior to May 29, 2009.
Dependency injection has been around for a while and there are quite a few frameworks which provide such capabilities for Java applications. Recently Google and SpringSource announced a partnership related to providing dependency injection for Java.
In this interview Joseph Yoder talks about the Adaptive Object Model (AOM) architecture, a software architecture for easily adapting to changing business requirements.
Data, Context and Interaction : A New Architectural Approach by James O. Coplien and Trygve Reenskau
James O. Coplien and Trygve Reenskaug have recently introduced a new architectural approach to OOP based on Data, Context and Interaction pattern. It should allow capturing user mental model in terms of behavioral requirements, something that classic OOP fails to do. The article, that triggered many reactions and critics, provides insights into DCI using concrete examples to show its advantages.
Many discussions of whether or not developers should use or learn ASP.NET MVC has been going on in blogs, Twitter and forums the last couple of weeks. The opinions varies from not recommended to all ASP.NET developers should learn it. InfoQ have tried to summarize some of the recent activity around this topic.
In this 3-parts series of articles, David Pallmann explains how to perform grid computations on the Azure cloud computing platform. In Part 1 he presents a design pattern for using Azure for grid computing, while in Part 2 and 3 he is going to give a concrete code example.
In an article, Tim Bray, examines the feedback from the first public draft of the APIs for the Sun Cloud. He responds to feedback in the article and explores the ways to model interactions such as, creating a VM in a Cluster, in a RESTful way.
Jaroslav Tulach's latest book Practical API Design covers the topics of API design in modern software applications, what factors make a good API, and how to go about implementing API frameworks. InfoQ spoke with Jaroslav about his new book. We are also making an excerpt from the book available for our readers.
In this article Billy McCafferty presents S#arp Architecture, an ASP.NET MVC architectural framework meant to leverage current best practices in architecting ASP.NET web applications by providing a project code template which uses Domain-Driven Design techniques and has built-in support for NHibernate, Castle Windsor and SQLite.
In his new comment, IBM’s Kyle Brown examines three different common anti-patterns, or "worst practices," that can make adopting Web Services and SOA implementations more difficult than it needs to be.