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.

Isn't a "single interface for all the data" the exact opposite of splitting the apps into layers and components?

liortal
– liortal

2014-03-31 11:15:56 +00:00
Commented Mar 31, 2014 at 11:15
1

Not at all. By introducing layers you separate functionality. For example, you have a layer to directly access database (all data in database is available through that layer), then you have another layer on top of it containing all the business logic, and then another layer as a simple functional interface over the business logic, etc. This last layer is a single interface to interact with data, and it still hides several layers behind it.

superM
– superM

2014-03-31 11:27:42 +00:00
Commented Mar 31, 2014 at 11:27

Add a comment |

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 »