Tracking change and innovation in the enterprise software development community
Plan-driven dev
Environments and
Agile tutorials at the
Better Software
Conference & Expo!
Create REST
-enabled Web Apps
with Project Zero
from IBM.
Introducing the
SpringSource
Application Platform:
Next-gen Java
AppServer
Rule your SOA
with CentraSite
standards-based
registry/repository
Terracotta:
Scale your
Apps w/ease
Offload the DB:
Learn More!
Since Linus Torvalds presentation at Google about git in May 2007, the adoption and interest for Distributed Version Control Systems has been constantly rising. We will introduce the concept of Distributed Version Control, see when to use it, why it can be better, and have a look at three actors in the area: git, Mercurial and Bazaar.
As it gets more and more difficult to adapt software to new demands, the temptation to rebuild it in order to update the architecture grows stronger. For this risky undertaking it is essential to choose the right strategy. Several authors provide insights into advantages and disadvantages of different possible options in terms of cost, technical complexity and potential commercial risk.
As organizations continue to grow their IT investments (bought, borrowed, or built) and concepts like Business Process Management and Service Oriented Architecture become more common, the role of Enterprise Architecture (EA) has become more common. Recently, several people in the EA community have spoken about its current state.
Windows workflow is an excellent framework for implementing business processes. One thing that is missing in it is direct support for human activities. Several approaches to solving this problem exist, but they are not generic enough for general usage. In this article we will define one of the approaches to a completely generic implementation of human activities in WF.
There is no silver bullet. We know it, but don't act like it. Your language, tool or process is better, right? Jay Fields says: "It depends". The right choices varies with context, people, and more. This article touches upon how a lot of things must impact a choice; learning culture, skill levels, teamwork, incomplete information, metrics - and context.
During OOPSLA 2007, InfoQ interviewed Markus Voelter asking him about creating software architecture documentation. Many people mention UML when they are asked about software design documentation, but Markus has a different take on that. He thinks that we should be using models which can be processed with tools which can validate or invalidate them.
In an interview at OOPSLA, Dave Thomas talks about the reasons for the rise of Java, what's behind Web 2.0, MDA and SOA, the rise of dynamic languages and the opportunities that he sees in the web as a platform.
In this presentation from QCon London, William Soo and Meeraj Kunnumpurath discuss the Voca transaction processing system architecture, the previous Mainframe-based architecture, architectural challenges and requirements, the new Spring and J2EE-based architecture, upcoming challenges for Voca, and technologies to watch for in the future.
Security is all about trade-offs you make with your always limited resources, often a problem when designing a system or an after-thought. Only a few have the expertise to design good security and most development teams have no security expert. This talk focuses on Security Patterns for designing security in architectures, such as Role-based Access Control, Single Access Point, and Front Door.
Composite Software offers a new level of granularity when compared to SaaS (Software as a Service). Composite Software is about enabling "right-sourcing", i.e. move (or keep) arbitrary small or large elements of functionality wherever it is the most cost effective to operate them, not just entire systems. Economically, "right-sourcing" is far more efficient than "outsourcing" and SaaS. The goal of this book is start by understanding today’s software construction processes and technologies and explore why and how it should be evolved to support core composition mechanisms.
Domain Driven Design is a vision and approach for designing a domain model that reflects a deep understanding of the business domain. This book is a short, quickly-readable summary and introduction to the fundamentals of DDD; it does not introduce any new concepts; it attempts to concisely summarize the essence of what DDD is, drawing mostly Eric Evans' book, as well other sources since published such as Jimmy Nilsson's Applying Domain Driven Design, and various DDD discussion forums.
