!"#$%&"'(#%")*"+',#&-%*"&*.#"

/)0"1('$,)'+"#'2%34*

,)0"1(5$,)+"#!%34*61.7%)%!5".

$ whoami

8 /)0"1('$,)'+"#'2%34*

8 9(77%:"#';%*-'/4,&-"'/9<

8 2(=;,#"'")0%)""#',*'>.7%)%!'2(=;,#"'?"$"1(47")*

8 @.AA;(#+!B'C,$,D'E2F%D'/0%1"

8 ,)0"1(!6,4,&-"5(#0',)0"1(5$,)+"#!%34*61.7%)%!5".''

G1,)!'H(#'*(+,I

8 2E/'J'*-"(#I

8 ?"K)%L()M!N

8 /!','!*I1"

8 O,)%H"!*,L()!

8 24"&*#.7

8 G#,&L&"

8 E2F%

8 G,:"#)!'P'4#,&L&"!

8 <Q,741"!

!"#$%&'()*+'*,&+$)-$*(+$.,#/%0+#*%1$2&3%#)4%52#$2.$%$-6-*+0$+072/)+/$76$)*-$'2082#+#*-9$*(+)&$&+1%52#-()8-$*2$+%'($2*(+&$%#/$*2$*(+$+#:)&2#0+#*$%#/$*(+$8&)#')81+-$3,)/)#3$)*-$/+-)3#$%#/$+:21,52#;<

==$>???$@AB@

Some time ago you saw an overview of a large number of architecture styles (lecture 3); today, I will focus on service oriented architectures in particular.I have a view of SOA that is not directly compatible with some of the leading research on it, you might see that today. Take your pick!

- I develop software based on service- and component technology, consult, and train.- I regularly speak on this subject.

Note: this presentation is part theory, part practical experience, part training material, and part ʻgood ideasʼ; you will note different styles for those.

Also: I am not about lots of text on slides. Pay attention, you wonʼt be able to find most of the material in the handouts.

Iʼll stick with your definition of architecture.

?"K)%L()R

!C+&:)'+=2&)+#*+/$%&'()*+'*,&+$DCE"F$)-$%$G+H)71+$-+*$2.$/+-)3#$8&)#')81+-$,-+/$/,&)#3$*(+$8(%-+-$2.$-6-*+0-$/+:+1280+#*$%#/$)#*+3&%52#$)#$'208,5#3;$"$-6-*+0$7%-+/$2#$%$CE"$%&'()*+'*,&+$I)11$8%'J%3+$.,#'52#%1)*6$%-$%$-,)*+$2.$)#*+&28+&%71+$-+&:)'+-$*(%*$'%#$7+$,-+/$I)*()#$0,1581+$-+8%&%*+$-6-*+0-$.&20$-+:+&%1$7,-)#+--$/20%)#-;<

==$K)J)8+/)%

!"$-+*$2.$'2082#+#*-$I()'($'%#$7+$)#:2J+/9$%#/$I(2-+$)#*+&.%'+$/+-'&)852#-$'%#$7+$8,71)-(+/$%#/$/)-'2:+&+/;<

==$KLM

!"$8%&%/)30$.2&$2&3%#)4)#3$%#/$,51)4)#3$/)-*&)7,*+/$'%8%7)1)5+-$*(%*$0%6$7+$,#/+&$*(+$'2#*&21$2.$/)N+&+#*$2I#+&-()8$/20%)#-;$>*$8&2:)/+-$%$,#).2&0$0+%#-$*2$2N+&9$/)-'2:+&9$)#*+&%'*$I)*($%#/$,-+$'%8%7)1)5+-$*2$8&2/,'+$/+-)&+/$+N+'*-$'2#-)-*+#*$I)*($0+%-,&%71+$8&+'2#/)52#-$%#/$+H8+'*%52#-;<

==$E"C>C$3&2,8

Itʼs hard to find a definition that is not from a vendor and includes words like ʻleverageʼ or ʻbusiness valueʼ. Still, in the end all architecture is about business value.

Wikipedia has a definition that focuses on the flexibility and reuse.

The World Wide Web consortium has a very concise definition; I like this one.

The OASIS group (Organization for the Advancement of Structured Information Standards) has a more precise definition, which alludes to using services from others. Also, it focuses on uniformity and ʻdata hidingʼ.They all have some things in common...

2E/B'&()!L*.")*!

8 9(74()")*!'+"&1,#"'!"#$%&"!',)+'+"4")+")&%"!

8 2"#$%&"!'&,)'&(7"',)+'0(S'&(74()")*!'!-(.1+'&(4"

2E/B'+I),7%&',!4"&*!

8 @")"K*!

8 T"+.&"+'&(741"Q%*I'

8 2&,1,U%1%*I'

8 V"!*,U%1%*I

8 <$(1$,U%1%*I'*-#(.0-'%!(1,L()

U")"K*!'P'&(!*!

U")"K*!'P'&(!*!

8 9(!*!

8 W,#+'*('X0"*'#%0-*Y

8 <)H(#&"7")*

8 Z(#[';%*-'+I),7%!7

SOA consists, in my view of- services: a well-defined interface which is ʻusefulʼ at some level.- components: things that provide and use services (component is deliberately vague)- dependencies: to be able to do its job, a component might need other services, or has requirements on things other than services (e.g. time of day or the presence of physical hardware)

In the ideal form, a component states what it needs to the ʻenvironmentʼ (there might be a container), and provides its services once they have been resolved.This is very simple, isnʼt it? It gets more interesting once we start worrying about deployment, which we wonʼt do today.

8 O(L$,L()

8 \!(1,L()

8 M9(4%)0';%*-'(#'&,.!%)0N'+I),7%&'&(74(!%L()

8 ](&,U.1,#I

8 2"#$%&"D'&(74()")*D'7,)+,*(#I^(4L(),1'+"4")+")&I

8 T.1"!

8 2"#$%&"!',#"'!"1HJ&()*,%)"+

8 \)*"#H,&"!',#"'+"K)"+'U"H(#"-,)+

8 <Q&1.+"+

8 ?%!&($"#I

8 E#&-"!*#,L()

8 9(77.)%&,L()'7"*-(+

!"$C+&:)'+$E&)+#*+/$"&'()*+'*,&+$)-$'208&)-+/$2.$)#/+8+#/+#*16$/+O#+/$'2082#+#*-9$8&2:)/)#3$-+&:)'+-$*(&2,3($%3&++/=,82#$)#*+&.%'+-;$M2082#+#*-$'%#$)#$*,&#$(%:+$/+8+#/+#')+-$2#$2*(+&$-+&:)'+-;<

O,)%H"!*,L()!

<)*"#4#%!"'2E/

This is the definition we will stick with. You may have noticed that I left out anything that has to do with using services from others; this is because (a) it is hard enough to use your own services well, and (b) I donʼt believe this is inherent to the style. Itʼs a benefit.

Letʼs first look at a number of manifestations.

Iʼve picked three manifestations of SOA more or less at random.

Note: We will see, SOA is not a technology, although the vendors try to show us otherwise

The first thing that comes to mind is the Enterprise market: huge systems that make the corporations work. SOA has been a buzzword here for the last, say, five years.

Image: http://www.flickr.com/photos/camknows/4712191684

8 @.!%)"!!'G#(&"!!'O(+"1%)0

8 _O>'&()K0.#,L()'($"#'"Q41%&%*'&(+"

8 9()*")*'U,!"+'#(.L)0

8 2/GD'\@OD'C@(!!'<2@D'O.1"D'2(4"#,

Z"U'2"#$%&"!

A typical manifestation of this is the Enterprise Service Bus, or ESB for short. Intended to integrate the different systems that make up the information needs of a large corporation.Consists of a Bus, with a number of adapters, connecting to services. There often is some administration components.

Web services arenʼt much more or less than ʻproviding services through HTTPʼ

Image: http://www.flickr.com/photos/jeffsmallwood/233853485/in/photostream/

September 2010, Wired ran an article ʻthe web is dead, long live the internetʼ. It shows that while usage of the web is declining, well-defined web-services are on the rise. When was the last time you used the twitter website?

Z"U'!"#$%&"!

T<2V

130 • R. T. Fielding and R. N. Taylor

Fig. 2. Process view of a REST-based architecture at one instance in time. A user agent is portrayedin the midst of three parallel interactions: a, b, and c. The interactions were not satisfied by the useragent’s client connector cache, so each request has been routed to the resource origin according to theproperties of each resource identifier and the configuration of the client connector. Request (a) hasbeen sent to a local proxy, which in turn accesses a caching gateway found by DNS lookup, whichforwards the request on to be satisfied by an origin server whose internal resources are defined byan encapsulated object request broker architecture. Request (b) is sent directly to an origin server,which is able to satisfy the request from its own cache. Request (c) is sent to a proxy that is capableof directly accessing WAIS, an information service that is separate from the Web architecture, andtranslating the WAIS response into a format recognized by the generic connector interface. Eachcomponent is only aware of the interaction with their own client or server connectors; the overallprocess topology is an artifact of our view.

the elements work together to form an architecture. All three types of view—process, connector, and data—are useful for illuminating the design principlesof REST.

5.1 Process ViewA process view of an architecture is primarily effective at eliciting the interac-tion relationships among components by revealing the path of data as it flowsthrough the system. Unfortunately, the interaction of a real system usually in-volves an extensive number of components, resulting in an overall view that isobscured by the details. Figure 2 provides a sample of the process view froma REST-based architecture at a particular instance during the processing ofthree parallel requests.

The client/server [Andrews 1991] separation of concerns simplifies compo-nent implementation, reduces the complexity of connector semantics, improvesthe effectiveness of performance tuning, and increases the scalability of pureserver components.

Since the components are connected dynamically, their arrangement andfunction for a particular application action has characteristics similar to apipe-and-filter style. Although REST components communicate via bidirec-tional streams, the processing of each direction is independent and therefore

ACM Transactions on Internet Technology, Vol. 2, No. 2, May 2002.

`2"#$%&"!

Web services have a number of incarnations. Take WS* for example.We have consumer and a producer; the latter provides a service defined by some definition in a WSDL. WSDL (Web Service Definition Language is an XML based language built on SOAP, stating what this service can do, and what it needs for that (an interface description). Using this definition, the consumer can invoke the service.Sometimes, there is a registry involves. This might contain the wsdl, and possibly is uses some naming mechanism.

This is a picture you might well recognize. It is the process view of Representational State Transfer; more and more webservices are relying on REST for their communication, phasing out the ʻheavierʼ protocols.

Microservices are a relatively new development of SOA.

Image: http://www.flickr.com/photos/gonzales2010/8632116/in/photostream/

This pattern is just common practice in object oriented development. In stead of talking to an implementation, talk to an interface.

<)*"#4#%!"'2E/Z"U'2"#$%&"!`2"#$%&"!

*-%!'1(([!'!.!4%&%(.!

\*Y!',)',U!*#,&L()

How about taking this to the extreme, and putting the interfaces closer to both the implementer and the user, leaving the ʻbindingʼ undecided. This binding is known as Dependency Injection, or Inversion of Control.Together (talking only to an interface, and using IoC), we call this microservices.

Now take a step back from that overview; donʼt we recognize this? What do the three notions we saw before have in common?The notion are rather disparate, yet they seem to fit the description nicely.

Actually, yes. We have seen components, services and dependencies as a formalism underlying other styles! I will not go into that too much now, letʼs first look at the ʻother sideʼ of the spectrum.

Letʼs try looking at it from the ground up. Every layer we add is a new level of abstraction.

Components are another axis, that have nothing to do with the patterns, but _are_ a useful mechanism. In fact, all SOA implementation I have seen have a built-in notion of components, of ʻpackagingʼ of the components. Some do a better job of separating those than others.

\!'%*'"$")','!*I1"R?"U,*,U1"5

8 2E/'%!','$"#I'U,!%&'!*I1"

8 %H'()"',*',11a

8 O,)%H"!*!',*'+%b"#")*'1"$"1!'(H',U!*#,&L()

8 2"#$%&"!',)+'&(74()")*!',#"'H#%")+!

8 2E/',!','4#"#"c.%!%*"'H(#'2,,2

EU!"#$,L()!

U#",[R

T"&,4

8 2E/',!','1(;J1"$"1'!*I1"

8 ?"K)%L()

8 2"$"#,1'7,)%H"!*,L()!

8 >%)['*('&(74()")*!

I donʼt think so. I believe itʼs a formalism that _helps_ in defining higher-level styles. Weʼll look into that a little more concretely after the break.

Z-,*Y!')"Q*R

8 E2F%

8 2"#$%&"'4,:"#)!

8 <Q,741"!

E2F%

E2F%'J'!(7"'-%!*(#I

8 <7U"++"+'41,d(#7'H(#'X-(7"'0,*";,IY

8 C9G',!'C2TJe'MfgggN

8 /'!4"&%K&,L()D')(*','*"&-)(1(0I

E2F%'J'!(7"'-%!*(#I

8 Tf'J'!(7"'L7"'%)'fggg

8 Th'J'E&*(U"#'hiif

8 C,$,'<7U"++"+'2"#$"#D'E!&,#'M2(.#&"j(#0"N

8 Tk'J'O,#&-'hiik

8 l)(4m"#K!-

8 Tn'J'/.0.!*'hiio

8 \@OD'<c.%)(Q'M<&1%4!"N

8 Tn5h'J'O,#&-'hifi

Letʼs take a look at OSGi. Weʼll go into quite some detail here.

OSGi technology is the dynamic module system

for Java™

OSGi technology is Universal Middleware.

OSGi technology provides a service-oriented, component-

based environment for developers and offers standardized

ways to manage the software lifecycle. These capabilities

greatly increase the value of a wide range of computers

and devices that use the Java™ platform.

E2F%'/11%,)&"

8 <Q4"#*'0#(.4!

8 9(#"'41,d(#7'M9G<FN

8 O(U%1"'MO<FN

8 ]"-%&1"'M]<FN

8 <)*"#4#%!"'M<<FN

8 T"!%+")L,1'MT<FN

E2F%B'&(#"'p'&(74")+%.7

!"#$%"&'($)&%*+,-./'01/'&%"2&)$.$),-$/345&%!"#$%6++$,3)&

7&+&,8&%9:%;&'8$/3%9<=>?3&%=@@A

!"#$%"&'($)&%*+,-./'0"&'($)&%1/02&34$5067&%!"#$%8++$,3)&

9&+&,:&%;<%=&':$/3%;>?85@5:-%?AAB

9(#"

!"#$%"&'($)&%*+,-./'01/'&%"2&)$.$),-$/345&%!"#$%6++$,3)&

7&+&,8&%9:%;&'8$/3%9<=>?3&%=@@A

!"#$%&"

!"#$%&'&($

!"#$%&

E2F%'j#,7";(#[

!"#"$%&'()"*$+",-&./

!"#$%&'(

!"#$%& !"#$%& !"#$%&

!"#$%&'()*+,'-

O(+.1"'>,I"#'Mf^kN

8 q)%*'(H'+"41(I7")*BU.)+1"

8 91,!!'1(,+"#'4"#'U.)+1"

8 %!(1,L()

8 U.)+1"'&1,!!4,*-

!"#$%&"#$%'()*!!

+%,'()*!!

!"#$%'-!&"#$%./0)'()*!!

12)%&,!"%/'()*!!

&"$%*/34)'()*!!

5678)%

!"#$%'-!'#!92:(4;*"#$'()*!!

!"#$%&'()!$'&("*#+!(

,-./01%*2345067'8319:;<5=1+>;,-./01%?1=;65.9:@+A+B

,-./01%C08;;D8<E9:+F:064)>;-G0+H8=

,-./01%$7GI8<5=9:;<5=1+>;+5;J6+$7GI8<5=

O(+.1"'>,I"#'Mh^kN

!"#$%&'($)*+#,-.""

/*+)*+#,-.""

!"#$%&"#$%'()*!!

+%,'()*!!

!"#$%'-!&"#$%./0)'()*!!

12)%&,!"%/'()*!!

&"$%*/34)'()*!!

5678)%

!"#$%'-!'#!92:(4;*"#$'()*!!

!"#$%&'()!$'&("*#+!(

,-./01%*2345067'8319:;<5=1+>;,-./01%?1=;65.9:@+A+B

,-./01%C08;;D8<E9:+F:064)>;-G0+H8=

,-./01%$7GI8<5=9:;<5=1+>;+5;J6+$7GI8<5=

"KD5=<%L87M8J19:;<5=1:B+N+A&3D5=<%D87M8J19:>;+.65O:P@F:OQ

O(+.1"'>,I"#'Mk^kN

!"#$%&'$(#%& '$(#%& '$(#%& '$(#%&

&)*"+,-

./*"+,-

&)*"+,-

./*"+,-

&)*"+,-

&)*"+,-

"+012*234&1$5%6718

"+012*234&1$5%6717"+012*234&1%"0691:

"+012*234&1#;671<

8 9()!%!*")&I

8 ")!.#"!'&()!*#,%)*!',#"')(*'$%(1,*"+

8 91,!!'$%!%U%1%*I

8 "Q4(#*"#!'7,I'%)&1.+"^"Q&1.+"'!4"&%K&'&1,!!"!

8 @.)+1"'H#,07")*!

8 ,'!%)01"'1(0%&,1'7(+.1"'%)'7.1L41"'4-I!%&,1'U.)+1"!

8 @.)+1"'+"4")+")&%"!'

8 /11(;!'H(#'L0-*'&(.41%)0';-")'#"c.%#"+

OSGi is Java based, and the container runs in a Java VM. The platform consists of four layers, of which we skip the Security layer here. Units of deployment are ʻBundlesʼ.

At the module layer, the software is grouped into bundles, where each bundle contains zero or more java packages and optionally some other resources or even native libraries. Some of these packages are exported, meaning they can be used by other bundles, others are private and only visible within a specific bundle. Packages that are exported by one bundle, can be imported by another. The exporter specifies a version number for a package. The importer can specify a range of versions it is compatible with. At run-time the framework will resolve such dependencies. All this allows you to keep implementations private, only exposing APIʼs.

>%H"J&I&1"'>,I"#

8 O,),0"+'1%H"'&I&1"

8 !*,*"!'H(#'",&-'U.)+1"S

8 /11(;!'.4+,*"!'(H'"Q%!L)0'U.)+1"!

8 +I),7%&,11I'%)!*,11D'!*,#*D'.4+,*"D',)+'.)%)!*,11

!"#$%&'&($

)*+,*

$-.

"-)*+((

)*+,*

)*/01-"-)*+((

"-)*+(($.

)*+,2-3

)*/00"-3

+&24$,$)/(4$.

1-"-)*+(($.

>%H"J&I&1"'<Q,741"

!"#$%&

'()*+,-./&01-2

4#($%+"+'4,&[,0"

!"#$%&

'()*+,-./&01-2

!"#$%&

>%H"J&I&1"'<Q,741"

%)!*,11'U.)+1"

>%H"J&I&1"'<Q,741"

!"#$%&

'()*+,-./&01-2

!"#$%&#"!(1$"'U.)+1"

On top of that, the life-cycle layer determines the life-cycle of individual bundles. Basically, bundles can be installed, started, stopped and uninstalled. Furthermore, an installed bundle can be updated anytime. Finally, you can uninstall a bundle if you donʼt need it anymore. The “starting” and “stopping” states have hooks for you as the bundle developer to actually make your bundle do something. By implementing the BundleActivator interface, the framework will invoke your start() and stop() methods. You will also get a BundleContext which is basically a reference to the API to talk to the container.

2"#$%&"'>,I"#

8 E2F%'H#,7";(#['4#(7(*"!'!"#$%&"'(#%")*"+'%)*"#,&L()'4,:"#)',7()0'U.)+1"!

!"#$%&"

'() !*(#"

+,-.%/0 ,/",/"

+,-.%/0

1#"2/

+,-.%/0,/"

3,45." 3,45." 3,45." 3,45."

!"#$%&"'(#)$%*"#

!"#$%&"'+",-"./"#

!"#$%&"'+"0%./#1

2-34%.5

%6/"#7&/

86*

2"#$%&"'<Q,741"

!"#$%&

'()*+,-./&01-2

4#($%+"+'4,&[,0"

4#($%+"+'!"#$%&"

2"#$%&"'<Q,741"

!"#$%&

'()*+,-./&01-2

!"#$%&

%)!*,11'U.)+1"

2"#$%&"'<Q,741"

!"#$%&

'()*+,-./&01-2

!"#$%&#"!(1$"'U.)+1"

Finally, the service layer contains a registry where services are published. Each bundle can register any number of services in the service registry. A service is registered using the fully qualified name of its interface. Furthermore, you can add any number of properties to this service. Both the name and properties can then be used again by others that query the registry.

2"#$%&"'<Q,741"

!"#$%&

'()*+,-./&01-2

!"#$%&

#"!(1$"'!"#$%&"

!"#$%"&'($)&%*+,-./'0"&'($)&%1/02&34$5067&%!"#$%8++$,3)&

9&+&,:&%;<%=&':$/3%;>?85@5:-%?AAB

E2F%'&(74")+%.7

Log

HTTP

Device Access

Configuration Admin

Preferences

Metatype

Wire AdminUser Admin

IO Connector

Initial Provisioning

UPnP™ Device

Declarative Services

Event Admin Service Tracker

XML Parser

Position

Measurement and State

Execution Environment Spec

Remote Services

Deployment Admin

Blueprint Container

!"#$%"&'($)&%*+,-./'0"&'($)&%1/02&34$5067&%!"#$%8++$,3)&

9&+&,:&%;<%=&':$/3%;>?85@5:-%?AAB

2"#$%&"'4,:"#)!

The Compendium contains a large number of more or less standard services. There are several compendiums for different markets, such as the ʻgeneralʼ market, the in-vehicle market, or enterprise.

Those services are neat, but we can do way more with it! Iʼll show a number of patterns we often see.

j,&,+"

j,&,+"

j,&,+"

j,&,+"

r\'+()Y*'&,#"s

The Facade pattern is about putting a simpler interface on a rich world.This rich world can be- an API thatʼs ʻscaryʼ (e.g. requires lots of builders),- unreliable, e.g. a network connection. In this case, we can add a notion of ʻavailabilityʼ to the service.

This also means we can put a different implementation behind the same interface.

Z-%*"U(,#+'4,:"#)

Z-%*"U(,#+'4,:"#)

r?()Y*'&,11'.!D';"Y11'&,11'I(.s

/+,4*"#'!"#$%&"!

/+,4*"#'!"#$%&"!

r>"*'7"'-"14'I(.';%*-'*-,*s

Whiteboard is about inverting registration. A typical example is an Event service: just declare yourself to be an EventListener, and the framework will handle the rest.

Adapter services are used to ʻaddʼ behavior to existing services.Suppose we have a payment service for our e-commerce system. In the basic service, we can do one payment at a time. We can put a transaction-adapter on top of this.

/!4"&*'!"#$%&"!

/!4"&*'!"#$%&"!

rV('!"#$"',)+'4#(*"&*s

],)+"#1,)+"O,).,1'9(+%)0'2*,L()

Aspect services add behavior without changing the interface.We could put an Auditing service on top of our same payment service; this allows us to log all payments, without interfering with the rest of the application, and without mixing logging logic with payment logic.As another example, we can add ʻilitiesʼ to services, without mixing them up with business logic. For instance, caching.

Vanderlande builds, amongst others, systems for handling luggage (e.g. in Schiphol, or Heathrow Terminal 5). The part weʼre interested in is the Manual Coding Station.The Manual Coding station handles bags that are ʻlostʼ, e.g. whose tag is unreadable.Interfaces with several systems in its environment, from flight control to conveyor control (PLC level).

We have a lot of systems on the network to interact with. We hid all of those services behind a service, and added state-awareness to that (which wasnʼt in the original services).

... Later on, we adapted the same system for another market.

O,).,1'9(+%)0'2*,L()

],)+"#1,)+"'O,).,1'9(+%)0

8 Z#,44%)0')"*;(#["+'!"#$%&"!',!'E2F%'!"#$%&"!

8 T".!"'&(+"',7()0'+%b"#")*'1%)"!'(H'4#(+.&*!

Jtiu

Later, we used the basics of the same system for the express parcel market.

Next case.Did you know that by the time the electricity gets into your home, to the time it charges your phone, you have lost some 60% of the energy.

Image of transformer: http://www.flickr.com/photos/mrbill/2547622226/in/photostream/Image of phone: @m4rr5

Who recognizes this? Itʼs a bridge rectifier.And what does it do? It converts AC to DC, but at loss of energy.Most devices you own actually donʼt need AC at all (perhaps only your washing machine); everything else is happy with DC.

<7U"++"+B/TO

q!"#'!(=;,#"B>%).Q

>%).Q

Moixa has a vision of putting a Home Energy System in your house, which provides your house with a DC network (USB 3.0 based). Now we have a smart hub in your home, you can control it using your mobile phone, and check your power usage.

Video: http://www.youtube.com/watch?v=IEENXnp6-Ng

So there we have it: for a greener future, we now havea box,and and ideaI have not shown it, but possible extensions for now:- solar panels,- small battery that charges during the nightand who knows what else!

Background image: http://www.flickr.com/photos/kylebaker/4511795125/

From a deployment perspective, it looks like this:- You have LED lighting and other peripherals in your home,- You connect the HES to this,- are able to control it directly using a web interface, e.g. on your phone,- and we want to be able to sync this to the internet.

The box contains- an embedded system based on an ARM processor, and- a piece of user software running linuxThe server runs linux. Or actually, we donʼt really care.

*-"'#"c.%#"7")*!

8 <7U"++"+'+"$%&"

8 >(*!'(H'*-"7a

8 9.!*(7'-,#+;,#"

8 T"7(*"'&()*#(1

8 ?,*,'&(11"&L()'P'!I)&-#()%A,L()

8 <Q*")!%U1"

E2F%

8 ?I),7%&'!I!*"7

8 9-,)0%)0'#"c.%#"7")*!

8 9-,)0%)0'*"&-)(1(0I

8 9-,)0%)0'+"41(I7")*

8 Z(#[%)0';%*-'-,#+;,#"

8 q!%)0'-,#+;,#"

8 q4+,L)0'K#7;,#"

+"$%&"'+#%$"#!

+"$%&"'+#%$"#!

Bundle-NativeCode: win32.dll; osname=WindowsXP; processor=x86 , liblinux.so; osname=linux

Working with hardware and device drivers is hard. Actually, we would just like to package these as a bundle!

Images: http://www.flickr.com/photos/squeezyboy/3300595223/http://www.ikea.com/us/en/catalog/products/50081452

Some words about Bundle-NativeCode:- package native drivers in your bundle,- let the framework decide which one to load,- use it as regular JNI.The framework can also dynamically reload your libraries, without need for stopping the JVM.

2*(#"'2"#$1"*

2*,*"'!*(#"

2*(#"'2"#$1"*

2I)&'!"#$"#

#".!"'H.)&L(),1%*I

2*,*"'!*(#"

2I)&'.L1

2I)&'.L1

2I)&'&1%")*

O(%Q,'W<2

8 W%+"'&(741"Q%*I'(H'-,#+;,#"

8 ?"41(I'!,7"'&(+"'()'$"#I'+%b"#")*'+"$%&"!

8 2E/'%!'$"#I'U,!%&

8 @,!%!'(H'(*-"#'!*I1"

8 @")"K*!

8 7(+.1,#%*ID'%!(1,L()D'#".!,U%1%*ID'1(;"#'&(741"Q%*I

8 9(!*!

8 W,#+"#'*('0"*'#%0-*D'-,#+"#'*('")H(#&"

8 j#,7";(#[!'"Q%!*'*('-"14'I(.

8 @.%1+'(*-"#'!*I1"!'()'2E/

Z-,*';,!',11'*-,*R

For instance: we have a data store that represents the state of the device. The store and many peripherals are identical for server and client; only the role in synchronization is really different.

Same thing applies to, for instance, the web ui.

Linkedin: uses distributed OSGi or scalingIBM: Websphere is built on OSGiBMW: OSGi for modular high-end entertainment systems (5 and 7 series)

You may also have noticed that I did not _really_ touch on distributed systems. This is because I believe distribution is something to be built on top of SOA, or which can have service-oriented properties. Still, SOA is not by default about networked systems, it just makes it easier.

!"#$%&"'(#%")*"+',#&-%*"&*.#"

/)0"1('$,)'+"#'2%34*

,)0"1(5$,)+"#!%34*61.7%)%!5".