General opinion on architecture needed
-
Ok, this is going to be a little off-topic, but its a .NET Architectural-type question. I'm working on the architecture to my University final year project, which is based around a commercial XML Web Service providing access to high performance analytics (courtesy of a third-party database). However, it will also need to perform a number of menial housekeeping work too -- providing audit trails, reporting etc. It would be useful to have some kind of application that can effectively monitor the web-service too, i.e. current load that kind of thing. I am considering using the following design: ASP.NET Web Service <----> Windows Service <-----> Databases With the Windows Service providing access to all the gubbins that hooks the web service together. That way, an administrative application can then access the windows service to get at the reporting info. Does anyone have any opinions, or suggestions as to how this kind of thing might be done? Alternatively I'd thought about adding filters using Microsoft's recently released Web Services Enhancements pack. Adding filters for logging requests etc. All opinions would be greatly received, -- Paul "If you can keep your head when all around you have lost theirs, then you probably haven't understood the seriousness of the situation." - David Brent, from "The Office" MS Messenger: paul@oobaloo.co.uk Sonork: 100.22446
-
Ok, this is going to be a little off-topic, but its a .NET Architectural-type question. I'm working on the architecture to my University final year project, which is based around a commercial XML Web Service providing access to high performance analytics (courtesy of a third-party database). However, it will also need to perform a number of menial housekeeping work too -- providing audit trails, reporting etc. It would be useful to have some kind of application that can effectively monitor the web-service too, i.e. current load that kind of thing. I am considering using the following design: ASP.NET Web Service <----> Windows Service <-----> Databases With the Windows Service providing access to all the gubbins that hooks the web service together. That way, an administrative application can then access the windows service to get at the reporting info. Does anyone have any opinions, or suggestions as to how this kind of thing might be done? Alternatively I'd thought about adding filters using Microsoft's recently released Web Services Enhancements pack. Adding filters for logging requests etc. All opinions would be greatly received, -- Paul "If you can keep your head when all around you have lost theirs, then you probably haven't understood the seriousness of the situation." - David Brent, from "The Office" MS Messenger: paul@oobaloo.co.uk Sonork: 100.22446
Hi Paul, Having this pipeline from Web Service -> Windows Service -> Database and back forces you to write (and debug) a lot of soap and remoting stuff (from outside to the WebSvc and back, from the ASP.NET Web Service to the Windows Service (remoting) and vice versa. Consider the following approach:
Windows UI/Console client \[\*remoted\] | Windows Service | vInternet <---> ASP.NET <--> Busines Logic DLL <--> Database
^
|
Windows UI/Console client [*simple]This way you can concentrate on core functionality by developing the Busines Logic Class Library and add all kinds of connectivity afterwards. greetings, Gertjan Schuurmans Amsterdam The Netherlands