Wednesday, November 01, 2006 - Posts

• Two Types of Service Architects?

  I was goinng to respond to Harry's responses made to Tomas and mine, but Tomas already responded and said everything I would have said: I agree with Tomas that I consider Service Broker a good match for applications with code only in the database, even though it supports more than code completly in the database (I made improper wording in my post indicating it did not) I agree with Tomas that there is a world of difference between "access a database" (99% of apps) vs. database-driven (see Tomas' definition). I said I tend away from these kinds of architectures these days as I see the power of domain-driven architectures (see Nilson). Obviously, there is no one architecture for every kind of problem I also don't get the whole "two types of service architects question" either and that a good architect will choose the right style for the right scenario I'd have to agree with Tomas again what Harry calls "Long running services" are really just a specific case of "Long running processes" and SSSB is too low-level for that. WF and BizTalk get me out of writing that infrastructure that is needed to be built out. But maybe I'm an idiot too and need to get hit with the clue stick as well Technorati Tags: SOA , Service Oriented Architecture , Windows Communication Foundation , Software Architecture , Windows Workflow Foundation , Microsoft Share this post: Email it! | bookmark it! | digg it! | reddit! | kick it! Read More... Posted Wednesday, November 01, 2006 10:25 PM from Sam Gentile | 0 Comments Filed under: WCF/Indigo, Software Architecture, SOA, Windows Communication Foundation, Microsoft, Blogsphere,  SOA, Service Oriented Architecture, Workflow,  Windows Workflow Foundation, BizTalk Server

• New and Notable 119

  Angus, the bulldog has so taken over the house. At least, it's made us more popular with the neighbors. Agile/Extreme Programming I always appreciate the care Jeremy Miller takes in articulating his points and his latest is no exception. In stating his Programming Manifesto , he makes reference to the infamous Agile Manifesto , I find I am in alignment with just about all his well-argued positions, particular, Unit Testing and Testability over Defensive Coding, Tracing, Debugging, and Paranoid Scoping and Explicit Code over Design Time Wizards. Read it all and come up with your own. Martin Fowler takes on PairProgrammingMisconceptions . Some are obvious but three, in my mind, are not: You have to do pair programming if you're doing an agile process Extreme Programming forces you to do Pair-Programming It's only worth pairing on complex code, rote code yields no advantage. WPF/Avalon/Windows Presentation Foundation Wow! Take a look at XamlPadX (Extended ) [via Mike ] Check out how to create Vista Gadgets using WPF A Sackful of WPF Tidbits from Tim Sneath Learning WPF WCF/Indigo/SOA/Workflow Tomas with How IMetadataExchange is Hosted WS-MTOM has been released Nicholas Allen::Advanced URL ACLing with Windows Vista Nicholas Allen::Design Pattern for Building Channel Factories and Listeners Vista Vista tips, get yer Vista Tips! Technorati Tags: SOA , Service Oriented Architecture , Windows Communication Foundation , Software Architecture , WPF , Avalon , Windows Presentation Foundation , TDD , Agile , Agile Development , Microsoft Share this post: Email it! | bookmark it! | digg it! | reddit! | kick it! Read More... Posted Wednesday, November 01, 2006 11:36 AM from Sam Gentile | 0 Comments Filed under: Windows Vista, WCF/Indigo, Software Architecture, SOA, New and Notable, Windows Communication Foundation, Agile, Microsoft, Avalon, Windows Presentation Foundation, Agile Development, Avalon/WPF, Service Oriented Architecture,  TDD,  WPF