Is there a difference between ASP.NET N-Layered / DDD architecture and a Window service software architecture? [closed]

Question

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.

Closed 9 years ago.

I am reading a lot of architecture (N-Layered and DDD) yet most of the articles are about web site architecture and develop mostly windows services.
Can the architecture be used the same way?

Answer 1

The primary goal of "layers" in software architectures are to separate concerns; your program logic should be separate from your data persistence, and from your user interface.

A Windows Service will not have a UI, but you can still gain efficiency, supportability and reduce the impact of future changes by separating your functionality logically. For example:

• Windows Service Layer: responsible for launching the service, handles defined events and exceptions - sort of analogous to the UI layer in a Web application, but obviously without UI
• Business Layer: Classes to execute your processing and encapsulate logic
• Persistence Layer: Abstracts persistence of data and state to database, xml, registry, whatever

So most of the Web architecture concepts you read about can be applied, and most of the tools can be used for Windows services as well.

Answer 2

Yes of course, except the Windows Service will likely not have much of a UI tier, if at all. Just a lightweight runnner method or so.

Answer 3

Although the services are different as they do not have a UI element to them, however there are ways to use the principles that apply in (N-Layered, DDD) i.e. development principles.

So for e.g. Services Share Schema and Contract, Not Class i.e. they are designed on Interfaces so a windows service can be a REST BASED service as well as a WCF Service but than again it can also call a repository underneath.