REST - Application layer or Service layer?

Question

I am writing web application which exposes REST interface and web socket for clients. This project interacts with underlying database. The UI layer and overall business logic is handled as separate project. Now I wanted to apply layers in this web application.

I have split my web application as,

1. Service layer (Exposes REST and Websocket)
2. Domain layer (Handling web application's Business logic)
3. Persistance layer (DB access)

Is this separation right? or Should i consider REST as application layer? Is application layer a.k.a service layer? Which is more meaningful here?

Is this just about naming components? Otherwise, why not follow something established, like DDD? — ernest_k, Jul 23 '18 at 04:56
It is about physical and logical separation. Is application layer a.k.a service layer? Which is more meaningful here — Malini Kennady, Jul 23 '18 at 04:58

score 2 · Accepted Answer · answered Jul 23 '18 at 08:52

The REST interface belongs in the same layer as the UI. It is a way of interacting with your app, just doesn’t have a user interface. I like to put the API in a separate project from the UI so it can be deployed separately and scaled separately. Ideally the UI would use the API for its data access.

With that said, asking this question implies you are designing your own architecture pattern, which is not a good idea. Much bigger brains that mine have attacked and solved this problems many times so you should pick one and use it. The one I find most flexible is the Onion Architecture (https://dzone.com/articles/onion-architecture-is-interesting), which fits well with DDD or Active Record. In the Onion Architecture, though, things are split between interface and implementation in a way that takes some getting used to so if you decide to migrate that way give yourself a little extra time to get accustomed to it. Once you do, you will be happy with the flexibility.

REST - Application layer or Service layer?

1 Answers1