Service-Oriented Architecture

CORE360 is entirely based on SOA concepts and has been architected to allow for deployment in any number of configurations to support existing SOA-based environments. CORE360’s architecture is loosely coupled with the underlying programming languages and operating systems which the framework is developed on. This provides standardized interfaces and isolated business processes packaged into individual CORE360 modules that can communicate with each other over the SOA protocols and network.

All aspects of the business processes are distributed and shared as needed by CORE360 as per accepted SOA concepts:

  • Service Encapsulation—All data access, manipulation, query, data injection and other services are consolidated as web services and other access protocols under a loosely coupled SOA architecture.
  • Service Loose Coupling—CORE360 services and APIs maintain a relationship that minimizes dependencies and requires that they maintain a minimal awareness of each other.
  • Service Contract—CORE360 services and APIs adhere to a communications strict agreement as defined collectively by one or more service description documents.
  • Service Abstraction—Services hide all logic from the outside world beyond that which is described in the service contract.
  • Service Reusability—CORE360 internal and policy based logic is divided into services with the intention of promoting reuse.
  • Service Composability—Collections of services can be coordinated and assembled to form composite services.
  • Service Autonomy—Services have complete control over the logic they encapsulate.
  • Service Discoverability—Web services are designed with WSDL to be outwardly descriptive so that they can be found and accessed via available discovery mechanisms.

Some of the specific implementation examples of SOA architecture within CORE360 are:

  • CORE360 user and document data structures are stored centrally and distributed as needed to each module within the context of the business process that module is performing. 
  • High use of meta-data is intended to describe not only the characteristics of the services, but also the data that drives them.
  • High use of XML as a descriptive container is standard within CORE360 and ensures high level of interoperability between services and business processes.
  • Extensive use of WSDL and SOAP for loosely coupled web services enable consumption per business process as needed.
  • Highly customizable levels of authentication and authorization policy allow for secure consumption of services over the entire organization.