From ae9fd264d74795d48c1f48b327f63caaf849e09a Mon Sep 17 00:00:00 2001 From: "Yann Esposito (Yogsototh)" Date: Sat, 20 Mar 2021 09:48:12 +0100 Subject: [PATCH] journal/2021-03-14--13-00-04Z--the_service_pattern.org --- journal/2021-03-14--13-00-04Z--the_service_pattern.org | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/journal/2021-03-14--13-00-04Z--the_service_pattern.org b/journal/2021-03-14--13-00-04Z--the_service_pattern.org index 2a2b2794..17a010e1 100644 --- a/journal/2021-03-14--13-00-04Z--the_service_pattern.org +++ b/journal/2021-03-14--13-00-04Z--the_service_pattern.org @@ -126,4 +126,11 @@ Architecture while moving a component. The service pattern should be easy to grasp with a few concrete examples. -Imagine you need to +Imagine you want to design an interface to manage your users. +The API you want to provide might be a very minimal CRUD-like one. + +- =create-user= +- =read-user= +- =update-user= +- =delete-user= +- =search-users=