Skip to content

why services

Jump to bottom Edit New page
nicholasdelrio edited this page Oct 18, 2012 · 4 revisions

The visualization pipelines constructed by VisKo are composed of Web services. This page describes the implications of this service oriented approach as well as some benefits.

Implications of a Service Oriented Architecture (SOA)

Most visualization toolkits such as Visualization Toolkit (VTK), Generic Mapping Tools (GMT), and NCAR Command Language (NCL) are standalone sets of libraries or executables that by default are not available as Web services.

The means that if you want to register a specific functionality from one of the aforementioned toolkits, it is up to you to write the service code that wraps the toolkit functionality and exposes it as a Web service. In some cases, this means that your service must invoke an executable, as is the case with GMT that is available only as a set of binary executables.

Benefits of SOA

  • language independent invocations
  • lower software development and management costs
  • scalability that may not be possible on a single machine
Add a custom footer
Add a custom sidebar
Clone this wiki locally