Architecture Recommendations

[whammer]

My development team is about to embark on the creation of a new
enterprise system, there are a few nailed down specifications imposed
by people higher up the food chain than me.
1) The database will be SQL2005
2) Most functionality will be made available over an intranet
3) An Interface needs to be exposed for communications with Mobile
Devices
4) Any dotnet code would be preferred to be in VB.Net
5) Visual Studio 2008 Team System should be made use of for project
management, source code repository etc..

I know that there are a number of different ways to approach the
architecture of this project, what I would like is the opinions of
others in terms of what they think would be likely to be a robust
architecture that will stand the test of time. i.e. is it worth
looking at WCF, WPF or are these things seen as gimmicks that will not
be around for long.

Many thanks

 

[sloan]

WCF is definately "not a gimmick".

You can check my example here.
http://sholliday.spaces.live.com/Blog/cns!A68482B9628A842A!158.entry

WCF gives you options for different scaling scenarios.

I would highly recommend Juval's book on WCF.
http://www.google.com/products?q=Juval+"Programming+WCF+Services"
There's a used copy for $8 in Virginia right now (with a damaged cover).

But it's a very good $40-$50 investment. Juval is one of the best at WCF.
www.idesign.net (or .com?) is his company's website.

...................
http://j2i.net/blogs/home/archive/2...e-wcf-development-and-embedded-databases.aspx
Just google "Mobile Devices WCF" for some other hits.

I don't do mobile development, but I think WCF is a great partner for it
based on things I've heard at user group meetings.

 

[Gregory A. Beamer]

My development team is about to embark on the creation of a new
enterprise system, there are a few nailed down specifications imposed
by people higher up the food chain than me.
1) The database will be SQL2005
2) Most functionality will be made available over an intranet
3) An Interface needs to be exposed for communications with Mobile
Devices
4) Any dotnet code would be preferred to be in VB.Net
5) Visual Studio 2008 Team System should be made use of for project
management, source code repository etc..

I know that there are a number of different ways to approach the
architecture of this project, what I would like is the opinions of
others in terms of what they think would be likely to be a robust
architecture that will stand the test of time. i.e. is it worth
looking at WCF, WPF or are these things seen as gimmicks that will not
be around for long.

Here is my two cents.

Applications are algorithms to solve business problems. This means the
logic is contained in class libraries. If you follow this rule, you can
put any faceplate on it, or even more than one.

WCF and WPF are not gimmicks. Microsoft has invested too much in them.

* WCF is Microsoft's only viable platform for SOA.
* WPF is now cemented both in VS 2008 (even more so in VS 2010 - in beta
now) and Expression. Expression 3 is out soon.


--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

Twitter: @gbworld
Blog: http://gregorybeamer.spaces.live.com

*******************************************
| Think outside the box! |
*******************************************