Monday, February 05, 2007

* Skills of a Solution Architect

* .NET Platform expertise

    • .NET 3.0 class library
    • Windows Communication Foundation
    • Windows WorkFlow Foundation
    • Windows Presentation Foundation
    • Enterprise Library
    • SQL Server 2005
    • IIS 6.0/7.0
    • Microsoft Office SharePoint Server
    • Biztalk Server 2006
    • Enterprise Solution Patterns
    • Security & Deployment Architecture

Storage Technologies

    • SAN, NFS
    • RAID
    • SCSI
    • IP Storage

Network Technologies

    • Protocol Architecture - OSI Model
    • Switching Technologies
    • Ethernet Overview
    • Internet Protocol & Routing
    • Transport Protocol
    • Network Security

* Server Technologies

    • Server Architectures (blade servers, super dome, etc)
    • Processor families (Itanium, Sparc, etc)
    • Cluster Technologies
    • Virtualization
    • Grid Computing

* Integration Technologies

    • Enterprise Application Integration fundamentals
    • Message Exchange Patterns
    • Data Integration Patterns
    • Web Services, SOAP, WSDL
    • MSMQ concepts
    • Data Transformation concepts
    • SOA - Service Oriented Architecture

* Others

    • Business Process Management Architectures
    • Performance Engineering Concepts
    • Security and Identity Management


Other Posts


  1. Two paise:

    Personally, I dont think you need to know all of the above to be a solutions architect. An overall knowledge of whats available and enough experience (~10yrs) should let you design stuff?

    Most specifically in this world, when the skilllist is going to change everyother day, technology should not be what drives the architect, but awareness. I guess the question here is "to what level"

    I guess it would take me 25hrs a day throught the year to keep up with that updating list!

  2. 'I dont think you need to know all of the above to be a solutions architect.'

    I completely agree

  3. A very good collection and Things ToDo for any new architect. But most of the items in the list are technologies, knowing a technology can never make one a good Solution Architect one should be aware of "base and origin", "benifits and drawbacks", "competitors and alternatives" of any technology which can only take you near to an efficent Solution Architect. Sounds like a plan for the whole life yes it is so the best thing to do is.
    - Educate yourself with basic solution architecture principles from perspectives like HUI, Security, Integration, Platform dependence, Maintenence and most of all Software Requirements.
    - Always keep yourself updated with new technologies and what a technology is for and only go in depth when you are going to architecture some thing.
    This will save you your whole life to go through non ending techs.

  4. I would like to thank you for the efforts you have made in writing this article. I am hoping the same best work from you in the future as well.