Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

2

Interestingly, Martin Fowler advocates against the same interface for local and remote invocation, arguing that the huge performance difference in remote invocation forces a more coarse grained interface.

psr
– psr

2012-08-29 22:41:13 +00:00
Commented Aug 29, 2012 at 22:41
I didn't quite understand your paragraph With CRM, Sales and Inventory there will be a lot of CRUD-type use cases of which there is almost always a one-to-one correspondence with Service Layer operations - if it's all about multiple UIs so how do the CRUD get in here? And if I wouldn't need multiple UIs even though the CRUD goes well with services I would still not make a service layer, if I understood correctly, and I really I hope I did because I prefer to keep things simple (service layer is a mess to my inexperienced opinion)

BornToCode
– BornToCode

2012-09-04 21:10:49 +00:00
Commented Sep 4, 2012 at 21:10
4

In those cases it's rare that there would be only one client that can take advantage of it. If you only had one UI I can think of two reasons that you may still want the service layer: security and reusability. A typical enterprise setup would have the UI app available to external clients, and your service layer only available in the network. So the web server delagates the work to a locked down portion of your network. In the sales example you could have re-use if you take sales from your web site and expand to eBay or Amazon. Now you have one UI, yet multiple clients.

Phil Patterson
– Phil Patterson

2012-09-04 22:16:02 +00:00
Commented Sep 4, 2012 at 22:16
5

Just to add to the comment from @PhilPatterson. Multiple clients don't just have to be UI based. Think web services or libraries - they can also be clients. Your front end UI might use the service layer as well as the software services you package and let someone else use.

Deco
– Deco

2012-09-05 02:02:01 +00:00
Commented Sep 5, 2012 at 2:02
can you provide an example of a Service Layer?

user962206
– user962206

2013-03-26 10:31:20 +00:00
Commented Mar 26, 2013 at 10:31

| Show 2 more comments

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »