Architects Zone - Architectural Design Patterns & Best Practices

SOA and the XML Factor: Designing Service-Oriented Solutions with Extreme XML Compatibility

Kalali — Mon, 06 Jul 2009 12:06:54 +0000

Interfaces of all kinds are subject to change. When we make a change to the operations or data offered by a service contract, this change will have an impact the consumers of the interface. In the world of SOA and service-orientation, attention to interface - or service contract - versioning is paramount because the average service-oriented enterprise ends up establishing many more dependencies...

Intuition, Performance, and Scale

driveawedge — Thu, 02 Jul 2009 09:52:37 +0000

Intuition is a double-edged sword. A blessing and a curse as it were. Intuition is knowing something with a reasonable sense of certainty without any justification for why you know it. It's this inability to clearly explain yourself when acting on intuition that is frustrating to you and those around you. Sometimes people will just trust your instincts but other times they will challenge you....

Three Forms of RESTEasy Client

sduskis — Wed, 01 Jul 2009 15:15:31 +0000

RESTEasy comes in three forms of client APIs: JAX-RS annotated Interface proxying Lower level fluid HTTP API ClientRequestFactory - generates #1 and #2, and has a get template method The ClientRequestFactory encapsulates RESTEasy client's most interest feature: client interceptors. Those interceptors come in three flavors:

CRUD is bad for REST

arnonrgo — Tue, 30 Jun 2009 09:11:20 +0000

In one of my previous posts (Rest: good, bad and ugly), I made a passing comment, about how I think using CRUD in RESTful service is a bad practice. I received a few comments / questions asking why do I say that – so what’s wrong with CRUD and REST? On the surface, it seems like a very good fit (both technically and architecturally), however scratch that surface, and you’d see that it...

SOA Pattern of the Week (#7): Policy Centralization

Kalali — Mon, 29 Jun 2009 09:46:13 +0000

Thomas Erl (SOASchool.com) and Herbjorn Wilhelmsen, (Objectware), bring you the seventh SOA Pattern of the Week, a series comprised of original content and insights provided to you courtesy of the authors and contributors of the SOAPatterns.org community site and the book “SOA Design Patterns." Masoud Kalali

Agile Architecture Requires Modularity

kirkk — Wed, 24 Jun 2009 10:43:56 +0000

A few weeks ago, I presented my view of agile architecture, and followed that up with a post on DZone that presented two aspects of agile architecture. A process aspect, which is temporal, and a structural aspect. Here, I embellish.References Reference: Agile Architecture Requires Modularity ...

Getting Started with Parallel Programming

HFadeel — Tue, 23 Jun 2009 13:25:34 +0000

Multi-core computers have shifted the burden of software performance from chip designers to software architects and developers. In order to gain the full benefits of this new hardware, we need to parallelize our code. The goal of this article is to introduce you to parallelism, its different types and to help you understand when to parallelize your code - and when not to. We will also examine...

The Reason SOA Isn’t Delivering Sustainable Software

jpmorgenthal — Mon, 22 Jun 2009 09:32:31 +0000

Wow, to read the positive reviews of SOA and what it’s doing for the IT industry, one would be likely to believe that there’s serious transformation occurring because of this architectural approach. Well, the truth is, implementing an SOA design such that real loose-coupling is achieved and that a service does not share a common bond with any other service down to its roots in persistence and...

A Look Inside Google App Engine for Java

nbharti78 — Thu, 18 Jun 2009 12:56:35 +0000

In this presentation, recorded at the recent Google I/O Conference, Martin Fowler and Rebecca Parsons of ThoughtWorks describe some of the applications they've developed for Google App Engine, including implementation of other languages, such as JRuby, on top of the App Engine for Java implementation. ...

What Drives SOA, Business or IT?

Kalali — Tue, 16 Jun 2009 10:04:03 +0000

Much like the chicken and egg dilemma, in the SOA industry, there is often a debate over which should come first -- business needs or technology needs. That largely depends on the problem you are trying to solve and whether it is a tactical or strategic solution that is desired. Today's businesses are seeking real solutions to real problems and the IT group is tasked with coming up with creative...

Tech Chat - Craig Walls on Spring Dynamic Modules

kirkk — Tue, 16 Jun 2009 06:58:18 +0000

Craig Walls is author of the recently published DZone Refcard, "Getting Started with Spring-DM", as well as previous Refcardz on Spring, such as "Spring Configuration" and "Spring Annotations". Kirk Knoernschild

The Role of Caching in Large Scale Architecture

gregrluck — Mon, 15 Jun 2009 10:39:42 +0000

Pre-Internet, lots of systems were built without caches. The need to scale has led to the widespread deployment of caching. Most of the open source caching projects grew out of internal efforts to solve performance problems for specific web sites. Ehcache, the most widely deployed Java cache, was originally developed at Wotif.com. And Memcached was developed for LiveJournal.com. ...

Java Modularity - OSGi and Project Jigsaw

kirkk — Fri, 12 Jun 2009 14:41:49 +0000

I’ve had some time to reflect on the sessions pertaining to Java modularity that I attended at JavaOne. This topic can be pretty confusing, so let’s take some time to clarify a few things. The JSRs Initially, there were three primary JSRs surrounding Java modularity - JSR 277, JSR 294, and JSR 291. Descriptions follow:References Reference: ...

With M (Oslo), is Microsoft on the path to reinventing RDF?

vambenepe — Fri, 12 Jun 2009 14:11:42 +0000

I have given up, at least for now, on understanding what Microsoft wants Oslo (and more specifically the “M” part) to be. I used to pull my hair reading inconsistent articles and interviews about what M tries to be (graphical programming! DSL! IT models! generic parser! application components! workflow! SOA framework! generic data layer! SQL/T-SQL for dummies! JSON replacement! all of the...

UML failed so here we have AML (Arbitrary Modeling Language)

nealford — Thu, 11 Jun 2009 13:30:13 +0000

UML is a failure. It failed for several reasons. Mainly, it failed because it falls into the cracks between technical people (developers, architects) and non-technical people (business analysts, project managers, etc). UML is too technical for non-technical people, and not technical enough for technical people. By this, I mean that it isn't really technical enough to do serious work on design by...