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.
Rule your SOA
with CentraSite
standards-based
registry/repository
Terracotta:
Scale your
Apps w/ease
Offload the DB:
Learn More!
Introducing the
SpringSource
Application Platform:
Next-gen Java
AppServer
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.
O’Reilly has published the third edition of the C# 3.0 Cookbook bestseller. The book has been updated for C# 3.0 and the .NET 3.5 platform. It contains more than 250 recipes for problems programmers encounter every day.
Steve Yegge touched a nerve in the development community when he argued that keeping the code size to an absolute minimum is the most important thing when developing software. In his view, you may have to sacrifice some design patterns and avoid refactoring at times just to keep the lines of code down. And if your problem is large enough - you may have to switch to another programming language.
Martin Fowler unveiled some details about his upcoming book on DSLs through his Work In Progress gateway. In the draft of its introductory part, Fowler gives an example of a Domain Specific Language case and provides some new insights on DSLs, their implementation and use.
Business intelligence (BI) and service-oriented architecture (SOA) have conflicting principles and needs. SOA promotes hiding the data inside the services while BI needs that very data if we want to get meaningful predictions and alerts. This article will show you how you can combine SOA with EDA to solve the BI/SOA conflict and maybe even enhance your SOA.
The majority of today's SOA design techniques are centered around definition of services. They use service-oriented decomposition, based on the business processes, enterprise business/functional model, required long term architectural goals and reuse of the existing enterprise functionality. This article takes a more data centric approach...
In this interview from QCon San Francisco 2007, Cédric Beust discusses designing and architecting for testability, problems that hinder testability, test-driven development, the "Next Generation Testing" book, performance testing recipes, and testing small, medium and large codebases.
Ramnivas Laddad talks about domain aspects, how aspects fit in the design phase, how to model aspects in UML, how to enforce policies with Aspects, how he used Aspects to diagnose production problems including touch threading problems, and using aspects to simplify design pattern implementation.
An Ajax application can go for several hours without leaving the original page. In this talk, Dave Crane explores ways to apply design patterns to the client tier, and how the use of patterns compares with the server-side. He examines the tension between maintaining server-control and delegating control to the client, and looks at the pros and cons of each architecture with real-world examples.
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.
Java Transaction Design Strategies shows how to design an effective transaction management strategy using the transaction models provided by Java-based frameworks such as EJB and Spring. Local, programmatic, declarative, and XA models are explained; the book concludes with a set of design patterns show how to effecitvely use these models.
