Skip to main content

Home/ Coders/ Group items tagged architecture

Rss Feed Group items tagged

Fabien Cadet

Service Oriented Agony | 8th Light, 2012-02-01 by Bob Martin - 7 views

  • The structure seems obvious to system designers who have grown tired of single monolithic systems and want to break those systems up into components and services. What could be more natural than to break the system along the lines of data base managment?
  • Unfortunately this is a huge violation of the Single Responsibility Principle — or its big brother the Common Closure Principle.
  • These principles tell us to group together things that change together, and keep apart things that change for different reasons.
  • ...6 more annotations...
  • When you separate things that change for the same reasons, you have to make changes in many different places in the system.
  • So it’s a lot of work just to get anything working.
  • Moreover, when you group together things that change for different reasons, you expose the components of the system to collateral damage, thrashing, CM collisions, and a whole host of other problems.
  • So what’s the solution? First of all, I question whether the system needed to be partitioned into services.
  • Services are expensive and complicated, you should only create them if you absolutely need to. It’s always easier to live in a single process. Remember Martin Fowler’s first law of distributed objects: Don’t distribute your objects.
  • Many systems could be streamlined, and development made much faster, if the system designers paid more attention to the Single Responsibility Principle.
Fabien Cadet

« Big Ball of Mud » (aka. Spaghetti Code) , by Brian Foote and Joseph Yoder (... - 3 views

  • The class of systems that we can build at all may be larger than the class of systems we can build elegantly, at least at first.
    « While much attention has been focused on high-level software architectural patterns, what is, in effect, the de-facto standard software architecture is seldom discussed. This paper examines this most frequently deployed of software architectures: the BIG BALL OF MUD. A BIG BALL OF MUD is a casually, even haphazardly, structured system. Its organization, if one can call it that, is dictated more by expediency than design. Yet, its enduring popularity cannot merely be indicative of a general disregard for architecture. »
Fabien Cadet

Your Architecture Sucks and I Don't Care, by Ryan, 2011-01-03 | Friendly Dingo Blog - 10 views

    "Besides, who am I to say your architecture sucks? And why don't I care? Because I am your users, and I don't care what your codebase looks like, I don't care what it's called, and I don't care what language it's written in. I care that it solves my problem in the simplest and fastest way possible."
Joel Bennett

Danger in Design: Why bother with Architecture? - Less Than Dot - 0 views

    Creativity is a wonderful thing. It's also something different for each of us, which is why sometimes our perspectives on the world can produce conflicting ideas on what is the right way and the wrong way to do things. This is a very common facet of the IT world, in particular making computer software, solutions and services. We don't need architects! …Do we ?
    The Winchester Mystery House as an example of what happens when you don't have an architect...
1 - 6 of 6
Showing 20 items per page