Q : What makes Sentinet stand out from other SOA Management offerings?
A: There are actually quite some differentiators. First of all, Sentinet is the only product in SOA Governance and API Management space that is built upon the full Microsoft stack. It is mostly beneficial to organizations that either entirely standardize on a Microsoft stack when it comes to build and operate their services and APIs, or those organizations that use a mix of Microsoft and non-Microsoft service applications and want to integrate them to the fullest extent possible.
Sentinet is also a unified on-premises, cloud and hybrid solution. It is the same product that customers can operate on-premises within their private data centers, in the cloud, or distribute parts of the product between cloud and on-premises in a hybrid scenario. At the same time, Sentinet can manage customer services and APIs that also can be either on-premises, in the cloud and in hybrid environments.
Another differentiator is that Sentinet is highly extensible through standard and simple Microsoft .NET interfaces. Customers can easily add their own specific service behaviors with minimum development effort and integrate these behaviors in the product run-time and User Interface.
Sentinet’s own User Interface is another differentiator where it provides easy to use, highly interactive and yet functionally powerful means to configure and operate complex SOA services and REST API solutions.
Q : In the virtualization context, could you shed some light on the Sentinet tracking mechanism and how big is its impact on the virtual service turnaround time?
A: Sentinet is designed to be lightweight and reliable, it processes messages with the minimum average overhead of 5 to 10ms per message, and all the monitoring and business messages tracking information is delivered to the Sentinet Repository asynchronously, which means that the business transactions are not slowed down at the expense of the Sentinet infrastructure.
Q: How does the APIs lifecycle management work and how a modification is applied at runtime?
A: The services are transitioned through multiple stages and modifications during their life-cycle. Sentinet users apply these changes using the Sentinet Administrative Console, a rich browser-based application. All changes are tracked for Auditing purposes. Changes that affect the actual runtime environments are delivered remotely to the Sentinet runtime components. For example, a Sentinet user can instruct remote Sentinet Node runtime to open new service endpoint and configure it with specific security policies, access control and monitoring attributes.
Q: How do you identify the new product features? From the customers feedback, from your R&D team, from a comparision with the competitors, or what else?
A: All of the above, where customer feedback is the most important source of information for us. We also rely on the past experience of our own engineers and architects who have built large-scale enterprise solutions that have processed billions of commercial transactions up to date.
Q: The Sentinet 4.0 release is coming. Could you tell us something about the new features you’re going to release?
A: There are multiple areas where we extend Sentinet’s capabilities. Some of them are full change audit and change notifications, registering and managing services starting from data schemas (we call it schema first services), graphical services and applications dependency tracking and impact analysis, and highly extensible graphically designed messages Processing Pipeline that will be shipped with a number of built-in message processing and transformation components. As always, we are making our messages Processing Pipeline to be highly extensible through incredibly easy to use .NET interfaces.
Thanks Andrew for answering. We wish you and the Nevatech team the best on the future releases.
For more information on Sentinet and the Codit offering around Sentinet, please visit our Solutions pages.
Massimo
Subscribe to our RSS feed