“something as a service”
We are now mostly familiar with what the concept of a service is in terms of computing software. Software services have and continue to have an enormous impact on modern software architecture and development methods. But what of other aspects of computing technology? are they excluded from being considered and subsequently managed and interacted with as services.
A key underlying concept of sense is to define and interact with internal and external computing units as services. That means that within sense we have a small set of tried and tested architectural approaches that can be applied to many other aspects of computing technology. To start with, all internal components and modules of sense itself expose themselves as sense services - meaning we can apply the same SLA driven benefits to sense‘s internal components as to user business services. But what about interactions with external services, resources or appliances?
sense considers all interactions with computer based assets and resources as a series of services! This means whether you are dealing with a Java program, a web service, a human task, a piece of hardware, a VM, a router, or even sense itself, sense will view and manage the interaction with the asset as a service. This permits sense, to use a tested and consistent set of development and management principles to build, manage and operate any cloud based solution where sense is involved. This consistency provides for reduced development time, managed end-to-end operations, and guaranteed SLA achievement across your entire applications and infrastructure portfolio. This is independent of whether you choose to operate your own private cloud on any mix of existing infrastructure, involve internal or external Virtualization solutions or decide to move operation into an internet based cloud. You get the same capabilities and SLA driven benefits whatever you choose to mange with sense.
In technical terms, services deployed to sense adhere to an interface and packaging metaphor to which we add runtime SLA driven behaviors. For external services; services not deployed into sense itself such as your existing web services or EJBs, or for external computing resources like a VM, or a router, or a cloud server, sense allows the implementation of a feeling to act as the intermediator to the external asset. So to sense a service deployed internally or a feeling to an external resource have the same management and SLA driven behaviors. It is this approach that offers gives us the general “something as a service” tag and allows sense to add business driven SLA behaviors to many more types of computing asset and resource than other cloud based architectures.


