ARCast – SQL Server Application Platform (Part 2 of 2)

The Discussion

  • User profile image

    Hello Ron,

    That was a very good Arcast  / web cast with Roger Wolter.

    I bought his book as well, it seems to me that with Service Broker some middle-ware layers could be reduced or moved closer to the database, improving performance, queuing reliability, etc.

    I found interesting that his book does not mention architects at all, just DBAs and DB developers, and it seems to me that this could become an important solution to implement many architectural patterns. I was wondering why didn't he mention architects, and also the scope of the applicability of the solution seems humbled to me, meaning that I believe it has many more applications than just what is suggested, I heard many times that it only apply to Database applications, and I do not know exactly what does  that mean. Maybe I am totally wrong, so I was wondering about your take on this, how does it relates to architecture directly and its applicability in normal solutions, not just database applications, its applicability in implementing several enterprise architectural patterns.

    On a different now, In this new Arcast web page, I also had to create a profile in order to write this message, and curiously enough the profile options only mention Solutions architect and Infrastructure architect, not Enterprise architect… ???

    When it comes to topics of Arcast, some times it will be interesting to look deep into the applicability of some patterns, like:

    - How to create application Context that is shared in a distributed environment.
    - How to utilize work flow as a visitor pattern in a distributed environment.
    - Much more on applicability of strongly typed data sets, Opinions, etc. How compatible are strongly typed datasets between 2003 and 2004, etc. I believe you are not in favor of strongly typed dataset, which are a w3c standard, but honestly the more I utilize them the more I get from them. SOA tenants and SO tenants differ a little according to some, and I believe in some instances strongly typed datasets are an excellent messaging alternative. I am interested on positive opinions about strongly typed datasets, if you can find some for me that will be great.
    - All those cool patterns that the P&P group is utilizing, like going deep into CAPs or the Object generator, maybe I am not utilizing the right terms or spelling but you know what I am refereeing too.
    - Applicability and adoption of Attributes, difficulty of adoption and understanding of new concepts like generics in c#, etc.
    - It is clear that Microsoft aims at a large base of developer types, and architecture probably takes less advantage of quick and no so clean solutions. Identifying those are also another interesting topic. In particular the case of declarative coding, strongly typed coding as oppose to quote delimited coding. I am very much against quote delimited coding because of how expensive maintenance of this is. I like having automated tools that generate types out of quote delimited data, this way any time you change the quotes, the types change as well, or fail if you don’t change them.

    I believe the work you are doing is very valuable to all of us, so thank you very much to you and Microsoft



  • User profile image

    Hi There,


    the video link is broken , does anybody know how to get the video or an audio cast




Add Your 2 Cents