SOA Jump Start and Design Patterns
This session was very informative. I have been avoiding reading about SOA for whatever reason, and this was my first introduction. Actually, it didn't really seem like something that is all that new. It almost seems like they came up with a new name for what is already being done under different names. I'm probably wrong, though.
The design patterns part of this session is what was really worthwhile. Surprisingly, to me at least, was understanding finally what on earth an Interface is! Yes, IEnumerable and the other I-things in .NET. What on earth? I've heard them discussed and it hadn't done me a bit of good until today. Suddenly the light went on, and it makes me wonder: am I dense or something?
Oh, well. I already had the concept in my mind and experience, what is even more surprising. It's just that it's somewhat old knowledge to me. Anybody remember the excellent computer language Modula-2? I learned how to use it ten or more years ago, and it had a feature that resembles or is identical to the idea of Interfaces. In M2 the Interface was implemented using module pairs: Definition Modules and Implementation Modules. The definition module had no implementation code, just an interface description. You could write all your definition modules and wire them up to the main execution threads in the overall program without ever coding any implementation, and the program would compile and run (as long as you didn't try to execute functionality that had not yet been implemented). The similarity between Modula-2's and .NET's implementation of Interfaces is conceptual and not explicit, if you know what I mean, but I am suddenly wildly enthusiastic about Interfaces. Slick stuff! I've been programming .NET for a couple of years already, and it hurts to admit that I have been such a slacker on this basic functionality, but there it is.
Thanks, Paul, for straightening me out!
