Top JAOO 2003
White
 

CONFERENCE
SPEAKERS
SCHEDULE
TUTORIALS
TRACKS
MANAGER TRACK
WORKSHOPS/BOF's

SOCIAL EVENTS
IT-RUN

EXHIBITION
SPONSORS
CONVINCE YOUR BOSS

REGISTRATION
TRAVEL
HOTELS
AARHUS FACTS

LINKS
HOME

Archives
JAOO 2006
JAOO 2005
JAOO 2004
JAOO 2002
JAOO 2001
JAOO 2000
JAOO 1999

JAOO CREW


CONTACT JAOO
JAOO Conference
Scandinavian Center
Margrethepladsen 3
DK-8000 Aarhus C
Tel.:+45 87 32 87 87
Fax: +45 87 32 87 88
VAT: 25809149
jaoo@jaoo.dk


panel
  Line  

Speaker


Clemens F. Vasters
newtelligence AG


Clemens F. Vasters is co-founder and CTO of newtelligence AG, a Germany-based developer services company focusing on XML Web services and .NET enterprise technologies. newtelligence offers developer education content production, architectural guidance, architecture and implementation reviews and offers Microsoft .NET training workshops tailored to customer's projects and existing developer skills.

Clemens has more than 15 years of experience as a developer and software architect for financial solutions for the banking industry, portal solutions and application infrastructure services. He frequently speaks at major local and international conferences throughout Europe, such as Microsoft TechEd Europe, the Microsoft Developer Days in Germany, Austria, Spain, and Slovenia and the recent Visual Studio .NET launch events in Germany and Norway.

Clemens is the author of the book "BizTalk 2000: A Beginner's Guide" (Osborne), ".NET Enterprise Services" (Hanser Germany), co-author of ".NET Crashkurs" (MS Press Germany) and is one of the MSDN Regional Directors for Germany. Furthermore, he is engaged in the development of the Microsoft .NET Developer Tools Readiness Kits' volumes as well as in the XML Web Services Architectural Guidance newtelligence authored for Microsoft. Clemens current work focuses on XML Web Services infrastructures as well as on enterprise services in the context of the .NET Framework
Picture of Clemens F. Vasters (newtelligence AG)


Presentation: "Layers, Tiers, Services and Aspects"

Monday 15:15 - 16:00, Tutorial Room

In theory, we all agree: separating presentation from business logic and business logic from storage is a widely accepted architectural principle. In the real world, though, breaking code up this way is hard to do. All sorts of practical problems arise as we try to separate infrastructure from application code and build extensible, componentized applications that provide optimal performance and reliability. Unfortunately, we know of no simple rules that eliminate this complexity: idealism is not a good advisor here. We have to take a more pragmatic approach. This session will analyze why and how we use "layers" and "tiers", shows common and proven approaches to do separating concerns in applications, some well-known, others less so. The motivating rationale and use-cases behind these "cuts" and how they may be relevant to aspects of your solutions will be shown. The presentation focuses speicifically on service- and messaging-oriented architectures and explains why asynchronous designs become more and more important in a Web services world.

Layers, Tiers, Services and Aspects - (slides)

Please notice that the slides are password protected. You should have received an e-mail containing the required username and password.


Presentation: "Service Oriented Architectures"

Monday 14:00 - 14:45, Conference Hall

Today's Web services story is about integration. Using open, standards-based, loosely coupled Web services technologies offers enterprises a flexible, affordable approach to integration. There is more to Web services than merely simplifying integration. In fact, they promise to fundamentally change the way software is made and used. Service oriented architectures are about data and contracts and very little about code. They reflect the reality that any "Technology Strategy 2008" that may be drawn up inside the ivory towers of corporate IT organizations is destined to fail. Technology strategies that aim to create pervasive technology platforms that shall be used by all and any applications inside an organization have traditionally failed and will fail even more in the future. Using a service oriented approach means to embrace the reality of heterogenicity and create integration strategies instead of technology strategies. Code is volatile, data stays.

Service Oriented Architectures - (slides)

Please notice that the slides are password protected. You should have received an e-mail containing the required username and password.
 
EOS
Oracle
SUN
SAP

Trifork EAS