Architecture Analysis Webcast 9am Friday
The International Association of Software Architects is hosting a webcast Friday, January 22, 2010 at 9am. You can register here: https://www2.gotomeeting.com/register/579164130
It will be a 1.5 hour talk about architecture, but specifically structure of an application. Here are the full details:
Architecture Analysis - Reasoning About Structure
This presentation is about fundamentals. Layering is a basic concept of IT architecture. Layers help to seperate dependencies and to decouple concerns. Most of the industry does layering in name only. It's lip service. In these slides and accompanying commentary we will explore the concepts of layering and isolation of dependencies and it's impact on the success of your architecture.
When:
Friday, January 22, 2010
9:00 AM - 10:30 AM CST
RSS
Comments
James said on 1.22.2010 at 3:56 AM
Cheers for the heads up on this :(
Bhavesh said on 1.22.2010 at 10:23 AM
Just wondering where can I get the code you have presented in this webinar.
Thanks
T said on 1.22.2010 at 10:53 AM
Jeff,
Is there a copy of the webinar content somewhere for those who missed it?
Thanks,.
Jeffrey Palermo said on 1.22.2010 at 11:16 AM
@Bhavesh,
You can get the code here: github.com/.../Chapter23
@T,
IASA will be posting the webcase on their website for members only: iasahome.org.
I will be providing this edited & produced webcast in a few weeks via www.headspring.com
John A. said on 1.22.2010 at 3:32 PM
I very much enjoyed the webinar. I had never really heard of the Onion Architecture, but it seems more intuitive, smells better. It's what you come up with following good design principles. In fact we have ended up with something more similar to it than to the traditional layered architecture.
Your blog has been great followup: http://jeffreypalermo.com/blog/the-onion-architecture-part-1/.
Thank you.
shine said on 1.24.2010 at 2:39 AM
Enjoyed the webinar and liked the Onion architecture approach (rather the thinking that drove the same). I think the DI (dependency injection) techniques (made popular by Spring etc in the java world) would help realize the same in a big way (similar to how your startup code gets the references active)