165:
155:
22:
125:, which aims to organize the services, within a service inventory, into a set of logical layers. Services that are categorized into a particular layer share functionality. This helps to reduce the conceptual overhead related to managing the service inventory, as the services belonging to the same layer address a smaller set of activities.
174:
Applying this pattern requires creating a service inventory blueprint, a list of services with associated functionality. Next, group the services into layers according to function. Adopting a common layering strategy across the enterprise facilitates reuse in other applications, because developers
145:
principle advocates designing services so that they can be composed in various ways. Both principles require that a service contain only a specific type of logic e.g., either reusable or process-specific logic. Restricting each layer to a particular functionality, simplifies the design of the
133:
Grouping services into functional layers reduces the impact of change. Most changes affect only the layer in which they're made, with few side-effects that impact other layers. This fundamentally simplifies service maintenance.
458:
32:
258:
334:
301:
274:
190:
160:
In the absence of any layers, services contain a mixture of different types of logic. This makes it difficult to manage these services.
266:
90:
186:
An alternative layering from
Bieberstein et al., involves five layers, namely enterprise, process, service, component and object.
62:
142:
69:
47:
415:
197:
138:
443:
76:
176:
379:
58:
180:
115:
119:
83:
175:
don't have as much to learn (or invent) when they join a project. One common layering uses task,
359:
340:
330:
297:
270:
262:
312:
322:
395:
245:
122:
170:
A service inventory divided into layers where each layer contains the same type of logic.
423:
259:
Service-oriented
Architecture Compass: Business Value, Planning, and Enterprise Roadmap
164:
154:
141:
principle dictates that services should be designed to maximize reuse. Similarly, the
452:
293:
209:
39:
394:
Bieberstein, Norbert; Jones, Keith; Laird, Robert G.; Mitra, Tilak (17 July 2008).
21:
285:
232:
228:
344:
364:
326:
400:
314:
Service
Oriented Device Integration - An Analysis of SOA Design Patterns
163:
153:
200:
service delivery approach facilitates the use of this pattern.
396:"Executing SOA: A Methodology for Service Modeling and Design"
15:
319:
380:"Service-Oriented Architecture and Java - Service Layer"
43:
189:The service layer pattern invokes a specific
8:
48:introducing citations to additional sources
38:Relevant discussion may be found on the
221:
416:"High-Level Perspective of the SOA RA"
358:Seshadri, Srikanth (17 January 2007).
311:Mauro, Christian; et al. (2010).
459:Service-oriented (business computing)
7:
14:
31:relies largely or entirely on a
20:
248:.Date accessed: 21 April 2010.
233:Introducing SOA Design Pattern
1:
382:. Technology. Binary Spectrum
235:. Date accessed:6 April 2010.
475:
59:"Service layer pattern"
327:10.1109/HICSS.2010.336
171:
161:
167:
157:
143:service composability
118:, applied within the
116:architectural pattern
191:service architecture
44:improve this article
444:SOA Design Patterns
290:SOA Design Patterns
257:Bieberstein. et al.
139:service reusability
120:service-orientation
172:
162:
336:978-1-4244-5509-6
321:. pp. 1–10.
303:978-0-13-613516-6
275:978-0-13-187002-4
261:.FT Press, 2005.
109:
108:
94:
466:
433:
431:
430:
411:
409:
408:
390:
388:
387:
375:
373:
372:
354:
352:
351:
307:
277:
255:
249:
242:
236:
226:
104:
101:
95:
93:
52:
24:
16:
474:
473:
469:
468:
467:
465:
464:
463:
449:
448:
440:
428:
426:
420:SOA Source Book
414:
406:
404:
393:
385:
383:
378:
370:
368:
360:"Logically SOA"
357:
349:
347:
337:
310:
304:
284:
281:
280:
256:
252:
243:
239:
227:
223:
218:
206:
169:
159:
152:
131:
123:design paradigm
105:
99:
96:
53:
51:
37:
25:
12:
11:
5:
472:
470:
462:
461:
451:
450:
447:
446:
439:
438:External links
436:
435:
434:
424:The Open Group
412:
391:
376:
355:
335:
317:. HICSS 2010.
308:
302:
279:
278:
250:
246:Service Layers
244:Wajid Khattak
237:
220:
219:
217:
214:
213:
212:
205:
202:
151:
148:
130:
127:
107:
106:
42:. Please help
28:
26:
19:
13:
10:
9:
6:
4:
3:
2:
471:
460:
457:
456:
454:
445:
442:
441:
437:
425:
421:
417:
413:
403:
402:
397:
392:
381:
377:
367:
366:
361:
356:
346:
342:
338:
332:
328:
324:
320:
316:
315:
309:
305:
299:
295:
294:Prentice Hall
291:
287:
283:
282:
276:
272:
268:
267:0-13-187002-5
264:
260:
254:
251:
247:
241:
238:
234:
230:
225:
222:
215:
211:
210:Service layer
208:
207:
203:
201:
199:
194:
192:
187:
184:
182:
178:
166:
156:
149:
147:
144:
140:
135:
128:
126:
124:
121:
117:
113:
112:Service layer
103:
92:
89:
85:
82:
78:
75:
71:
68:
64:
61: –
60:
56:
55:Find sources:
49:
45:
41:
35:
34:
33:single source
29:This article
27:
23:
18:
17:
427:. Retrieved
419:
405:. Retrieved
399:
384:. Retrieved
369:. Retrieved
363:
348:. Retrieved
318:
313:
289:
253:
240:
224:
195:
188:
185:
173:
136:
132:
111:
110:
97:
87:
80:
73:
66:
54:
30:
286:Erl, Thomas
429:2020-07-26
407:2020-07-26
386:2020-07-26
371:2020-07-26
350:2020-07-26
229:Thomas Erl
216:References
100:April 2010
70:newspapers
365:JavaWorld
345:1530-1605
168:Diagram B
158:Diagram A
146:service.
129:Rationale
40:talk page
453:Category
401:InformIT
288:(2009).
204:See also
198:top-down
181:utility
84:scholar
343:
333:
300:
273:
265:
177:entity
114:is an
86:
79:
72:
65:
57:
150:Usage
91:JSTOR
77:books
341:ISSN
331:ISBN
298:ISBN
271:ISBN
263:ISBN
196:The
179:and
137:The
63:news
323:doi
46:by
455::
422:.
418:.
398:.
362:.
339:.
329:.
296:.
292:.
269:,
193:.
183:.
432:.
410:.
389:.
374:.
353:.
325::
306:.
231:.
102:)
98:(
88:·
81:·
74:·
67:·
50:.
36:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
