Service Layer Pattern - Could we avoid the service layer on a specific case?
        Posted  
        
            by lidermin
        on Stack Overflow
        
        See other posts from Stack Overflow
        
            or by lidermin
        
        
        
        Published on 2010-04-08T22:00:18Z
        Indexed on 
            2010/04/08
            22:13 UTC
        
        
        Read the original article
        Hit count: 336
        
design-patterns
Hi, we are trying to implement an application using the Service Layer Pattern cause our application needs to connect to other multiple applications too, and googling on the web, we found this link of a demonstrative graphic for the "right" way of apply the pattern:
martinfowler.com - Service Layer Pattern
But now we have a question: what if our system needs to implement some business logic, only for our application (like some maintenance data for the system itself) that we don't need to share with other systems. Based on this graphic:

As it seems, it will be unnecesary to implement a service layer just for that; it will be more practical to avoid the service layer, and just go from User Interface to the Business Layer (for example). What should be the right way in this case to implement the Service Layer Pattern? What do you suggest us for a scenario like the one I told you?
Thanks in advance.
© Stack Overflow or respective owner