Tier is a natural boundary
When talking about multi-tiered architectures, we need to remember that the tier boundary is significant. The tier boundary is where distribution happens and if you remember the “fallacies of distributed computing“, you know not to take that lightly. A tier is a physical boundary (versus, for example, an Edge in a SOA which is a logical boundary within the service). The implications...
Read MoreTidbits
From time to time I am going to post a few thoughts that come up which are longer than a tweet but shorter than a post. Software Architecture books I recently got a question from Jon : I am wanting to make the leap from senior engineer/team lead to software architect, can you recommend any good books or resources? Well, my current top 5 books for architects are Software system architecture...
Read MoreSoftware Architecture – 5 years later
I got several interesting comments to “Who needs an architect” (both here and on DZone). Some of them said I don’t get the architect “role”, some said I am looking at things from the code level and don’t see the forest for the trees, others said that this whole “agile” thing is crap (admittedly not in so many words). Another one talked about the...
Read MoreWho needs an architect anyway?
Not all projects need architects. There, I’ve said it. Not all projects need architects and I am not talking here just about trivial projects. There are cases (maybe even many cases) where you can get by with what I call “off-the-shelf” architecture – maybe with a few adjustments that any master developer (i.e. seasoned and experienced developer) can handle. For instance a...
Read More
Profiles & RSS