• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (3)

1 localhost commented Trackback

Extending SOA to the backup infrastructure can pay dividends. Years ago we deployed service oriented backup software from Asigra in order to solve issues of accountability and IT resource usage within our organization. Because this software was originally developed for managed backup service providers it allows large organizations with multiple backup zones to not only consolidate large distributed backup sets but also allows your company to act as its own "internal" service provider. There are many features and special functionality in the software which makes it uniquely suited to protect remote-office/branch-office data. And do it in the manner of utility service provisioning (billing system, SLA monitoring & management, budget allocation, quotas, encryption, self-healing, web self service, etc.). The software also enables chargeback capabilities so the datacenter can function as a profitable cost center. To date, I have not seen this sort of capability available in an enterprise software package and present it here for more discussion.

2 localhost commented Permalink

Ali, I'm curious if you have any thoughts (possibly already in an article/whitepaper etc.) on brand new development and SOA. Most (if not all) of the articles I have read always focus on the reuse of several legacy systems and recomposing them into new applications. What I struggle to understand is how all the layers in your reference architecture fit if one were doing brand new development and didn't have a "legacy" system at the bottom. Are all the layers appropriate for such a system? Just curious your thoughts.


3 localhost commented Permalink

HI Gary, I was sure I posted this before, but I do not see it in the comments!

YES, these layers are very appropriate for such systems that are brand new or consist of custom soa application development.
Let me know if you need more specifics!

Add a Comment Add a Comment