Det kan lätt uppstå oklarheter när man disktuterar s.k. "Services" eftersom det inte är säkert att man diskuterar samma typ av "Service". Situationen förbättras inte direkt av att Services kan finnas i många olika lager (layers) samtidigt som det finns ett specifikt layer som brukar kallas Service layer, av bl.a. Martin Fowler.
Eftersom det både kan finnas t.ex. Domain layer services, Infrastructure services och "Service layer services", så är det nog bättre att använda sig av begreppet Application layer och Application layer services i stället för Service layer.
Det kan också vara bra att försöka vara tydlig med vilken typ av lager man faktiskt refererar till, t.ex. säga "Domain Service" i stället för att bara använda sig av det mer diffusa begreppet "Service".
Länk till en relaterad längre kommentar angående services:
http://www.webforum.nu/showthread.php?p=1496572#post1496572
I have added a new code example about how Scala can be used for less verbose coding, compared to Java (!), regarding (for example) not having to declare the type of Javabeans multiple times
The example also provides a JUnit example which, through a common Java interface, verifies the same behaviour for the Java implementation and the Scala implementation, even though the Scala class does not seem to define any getter/setter methods.
http://www.oo-systemutvecklare.se/scala-for-java-developers/scala-less-redundant-verbose-than-java/
I added a new example to my web pages about the programming language Scala, which is an example of how it can be used for less verbose coding, compared to Java (!), without having to create an interface with only one method (including having to create a bunch of implementations, which you have to do in Java)
Here is the start page (swedish) for my Scala pages:
http://www.oo-systemutvecklare.se/scala-for-java-utvecklare/
And here is an english page with some links:
http://www.oo-systemutvecklare.se/scala-for-java-developers/
Homepage for the book:
http://programmer.97things.oreilly.com
The article I commented:
http://programmer.97things.oreilly.com/wiki/index.php/Test_for_Required_Behavior%2C_not_Incidental_Behavior
My comments about the above article:
http://programmer.97things.oreilly.com/wiki/index.php/Talk:Test_for_Required_Behavior%2C_not_Incidental_Behavior
My contributions:
http://programmer.97things.oreilly.com/wiki/index.php/Special:Contributions/TomasJohansson
/ Tomas Johansson
Though, the book seems to be scheduled for printing in february 2010, according to statement at:
http://groups.google.com/group/97things-programmer/browse_frm/thread/ba60d1c1fd9e3e95
so, my contributions may not become included in the book, even if the decision makers would agree about my opinions there...
Homepage for the book:
http://programmer.97things.oreilly.com
The article I commented:
http://programmer.97things.oreilly.com/wiki/index.php/Thinking_in_States
My comments:
http://programmer.97things.oreilly.com/wiki/index.php/Talk:Thinking_in_States
/ Tomas Johansson
:: Next Page >>
Tomas Johansson is a Swedish developer, located in Stockholm, with a very strong interest in software development principles leading to long-term maintainable software. Some of these principles include Test-Driven Development, Domain-Driven Design, Architectural and Design patterns, SOLID Principles and GRASP patterns. Currently, my favorite programming language is Scala, but otherwise I am also generally interested in C#.NET and Java.
| Next >
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| << < | > >> | |||||
| 1 | 2 | 3 | 4 | 5 | ||
| 6 | 7 | 8 | 9 | 10 | 11 | 12 |
| 13 | 14 | 15 | 16 | 17 | 18 | 19 |
| 20 | 21 | 22 | 23 | 24 | 25 | 26 |
| 27 | 28 | 29 | 30 | 31 | ||