• Post Reply Bookmark Topic Watch Topic
  • New Topic

Software Piplines and SOA  RSS feed

 
Jignesh Patel
Ranch Hand
Posts: 626
Mac
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Software Piplines and SOA

As mentioned in the subject of the book, I am assuming the book is going to discuss lot towards networking like:
1. How addressing should be handled beween 2 end points?
2. How respositories should be used for finding services?
3. How messages can be secured while passing through network?


Does it also talk about managing processing through webservices?

Moreover is this book only limited for SOA discussion or it also explains about RESTFul Services?
 
Cory Isaacson
author
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
As mentioned in the subject of the book, I am assuming the book is going to discuss lot towards networking like:
1. How addressing should be handled beween 2 end points?
2. How respositories should be used for finding services?
3. How messages can be secured while passing through network?


One of our objectives with Software Pipelines was to ensure that it would work with any protocol, therefore you will see that the abstraction layer is a simple interface for writing and invoking services (either one-way or request-response). The actual protocol between the services themselves can be any method you desire. For the reference framework we support two primary methods:

Local services (where your service is invoked directly by API)
Remote services (where w built a simple protocol that encapsulates a message object)

One thing stressed in the book is that a service-oriented architecture is not limited just to Web services by any means -- much more importantly its a method of building and assembling applications, completely independent of any "wire" protocol. You could easily implement pipelines with SOAP for example, but that isn't necessarily the most efficient way to do things, especially if you are running a lot of things in parallel on a single server or across many servers. So the idea is that "where" and "how" the service runs is not so important, its the fact that it is scalable, can run in parallel, and ensure that key business transaction rules are supported.

Hope that helps.

Cory
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!