Geek asks and answers

Creating an enterprise application without a service level

There are so many tutorials that teach us to use, for example, ORM directly with the database, but in real life I can’t remember a big project that worked directly with the database, not with services, so the number of these tutorials seems strange to me. Directly connected applications have real advantages in the speed of data transfers between the database and the application, and they do not have limitations in functionality that appear due to service levels (for example, you can take the Entity infrastructure and WCF data services (which uses the same data model object)). On the other hand, the solution to services is more secure and flexible, which is why I (and I think that many other programmers) usually choose it to create large applications with some common business logic ... BUT!Sometimes losing in speed up to 10 times! It's just sad, the application is becoming less responsive than it could be. Therefore, I want to ask a question: can you share your experience in creating enterprise applications without a web services layer and when is it a good choice?

+2
source share
1 answer

Enterprise application! = N-tier application. This means that you can write an enterprise application without creating a separate physical mid-tier (business logic). Creating a separate middle tier should always be part of the requirements, because it is a lot of extra complexity = a lot of extra cost.

Common requirements for a particular mid-level are:

  • Security - sometimes the web server is located in the DMZ, and the middle tier should be on a secure network.
  • Repeatability - you want to use the middle tier in more than one application, this also leads to the SOA requirement.
  • - , . , . .

, , , - .

+6

More articles:


All Articles