Architectural decisions based on experience and .NET knowledge.

Did you know that there are at least seven different technologies/protocols which can be used for the development of distributed .NET applications? All of them have their particular advantages and disadvantages - but which one should be used for your application?

To make matters worse, each of these technologies can be used in ways which render your application instable, non-scaleable, or which provide versioning problems later on.

Ingo is quite serious about architecture. He will discuss the various approaches with your architects and developers and will work with them to create an architecture which solves not only your project's current needs but which also respects the mid to long-term goals of:

• Maintainability, versioning and re-use
• Demands on scalability, performance and security
• Cost and timeframe of development
• Corporate mid- to long-term vision for this project

No matter if you are working on a .NET to .NET application or on an XML Web Services based solution: Ingo has been there, done that - and will happily share his experience.

Location

These services are usually performed directly in your offices and will usually take a couple of days. If preferred, Ingo can also join your project team remotely and deliver architectural whitepapers and prototypes according to your needs.

Contact

Please don't hesitate to contact us to speak with us about how Ingo can help you and your projects.