Service Interface Layer Pattern

The Service Interface Layer Pattern is probably the unsung hero of patterns. I think it is one of the most important patterns, given that it should be used in practically every application you build. In this video, I talked about how I was introduced to it and where and how I use it, as well of the advantages of using this pattern.

Link to the Source Code used in this video:

Chapter Markers:
00:00 Intro
02:30 The Genesis
07:24 The Need to Decouple
08:37 Moving to a Web Application
10:06 Evolution to a Thin Client
12:58 What is a Service Interface Layer?
17:44 Examples of Service Interface Layers
18:18 Use your System Anywhere
21:24 Real World Cases
22:57 IoT Application Benefit from this Decoupling
24:45 A Lot has Evolved But the Service Interface Layer Remains
26:00 Introducing the Code
30:07 Using a Console App as a Service Interface Layer
33:23 No Bootstrapping Required
35:37 Running the Console Application
36:11 How Simple was That!
37:40 Conclusion

[hansrudolf]

For someone who only joined later, it's always interesting to hear how it was back in the days ... 👍 Great video as always Shiv!

[TheChandan]

Thank you Shiv for this video. I loved to hear about your old day's experience. Please keep on posting more videos like this.

[robertslazda]

Hey, Shiv, excellent video - I'm trying to reimplement in my project. Could you elaborate more, what happens if I have more media and services. What if I need books, songs and parties? Some of them might be connected in the bundle? Is the goal to extend the managers? Should I keep one Domain facade for each group, then split into multiple managers? Just wondering how to extend this to benefit from architecture, and how would it look like, if this system also need to handle books.

[Miggleness]

you should mention the blink html tag. that was gold back in the days

[ivanvincent]

Thanks Shiv. The quality of your diagrams and the addition of time stamps are really useful supports when watching your videos.

I have a question around architecture. I have seen implementations online using CQRS and a library like MediatR to manage communication between the service interface layer and the domain via handlers. How would you evaluate this approach versus calling a domain facade directly ?

[vishnupvNB]

Sir, where are you these days. We need you to contribute nee videos. Azure and edge computing and IoT Please

[sunilchand.]

Where should the business logic reside in this case, inside the domain facade only?

[abutahir]

I like your base voice.. you should do voice over :P