The Architect´s Napkin

My Links

• Home
• Contact
• 
• Login

News

Archives

• December 2015 (1)
• November 2015 (1)
• July 2015 (2)
• May 2015 (3)
• April 2015 (3)
• December 2014 (1)
• November 2014 (2)
• October 2014 (1)
• September 2014 (2)
• August 2014 (4)
• June 2014 (3)
• May 2014 (2)
• March 2014 (4)
• February 2014 (2)
• January 2014 (1)
• October 2013 (1)
• September 2013 (3)
• August 2013 (5)
• May 2012 (2)
• April 2012 (1)
• December 2011 (4)
• July 2011 (1)
• June 2011 (1)
• March 2011 (2)
• January 2011 (1)
• August 2010 (3)
• July 2010 (4)
• July 2008 (1)
• June 2008 (8)

Post Categories

• Biztalk 2006 R2
• SQL
• EDI
• jquery
• WIF
• WCF

Image Galleries

• 

  April 2015 Entries

  The IODA Architecture

  The common architectural patterns are all pretty much the same. Layered architecture, MVC, Hexagonal architecture, Onion Architecture, Clean architecture… they all do two things: Define domains of responsibility Put functional dependencies in order Look at these depictions of some of the patterns: What you find are shapes (rectangles, circles) with the responsibility to produce part of the required behavior of a software. All models forsee certain responsibilities like interaction with the user, ......

  • Share This Post:
  • 
  • 
  • 
  •   Short Url: http://wblo.gs/gW4

  Posted On Wednesday, April 29, 2015 3:15 PM | Comments (10) | Filed Under [ Thinking outside of the box Software architecture ]

  Sweet Aspects

  When a module has a single responsibility that means it’s focused on producing the behavior of a single aspect. That’s how I described the Single Responsibility Principle (SRP) in my previous article. Since the SRP is so important and at the same time a bit elusive, I thought, I try to illustrate this “traits and aspects thing” a bit more. Maybe you can even develop a taste for the SRP :-) Look at this heap of sweets: Let them represent logic in your code. You know, those 5,000 lines of code in a ......

  • Share This Post:
  • 
  • 
  • 
  •   Short Url: http://wblo.gs/gVa

  Posted On Monday, April 27, 2015 8:59 PM | Comments (0) | Filed Under [ Thinking outside of the box Software architecture ]

  The Single Responsibility Principle under the microscope

  It’s equally important and mysterious: the Single Responsibility Principle (SRP). And even though its originator Robert C. Martin tried to explain it again, I feel there is something lacking. Some concreteness, some tangibility. First the definition of the SRP in Martin’s own words: “The Single Responsibility Principle (SRP) states that each software module should have one and only one reason to change.” This is more informative than Wikipedia’s tautology: “In object-oriented programming, the single ......

  • Share This Post:
  • 
  • 
  • 
  •   Short Url: http://wblo.gs/gVU

  Posted On Saturday, April 25, 2015 5:47 PM | Comments (1) | Filed Under [ Thinking outside of the box Software design ]