Recursyv is a cloud hosted integration platform. Built on a message bus paradigm it provides a truly reliable, scalable and flexible solution for synchronising data between apps and platforms.
Resilience from the Ground Up
The message bus architecture and data polling approach on which the service is built provide a basis for ensuring data resiliency. If failures occur either retrieving or sending data, then the architecture is designed to ensure data delivery is successful.
Connectivity and data integrity issues are all dealt with in an appropriate and resilient manner to provide information is delivered reliably and accurately to the destination.
Recursyv operates proactive monitoring which informs us if there are issues with the service. Our engineers are immediately notified of any errors and these are quickly analysed.
Where issues will result in operational interruptions to syncing data, Recursyv will inform you about the interruption as well as what we are doing to minimise impact and restore service.
In some cases we are even able to advise you about potential data or connectivity problems within your application before you know about them.
Security at its Core
Recursyv is deployed within Microsoft’s Azure cloud. Azure meets a broad range of international and industry-specific compliance standards, such as ISO 27001, HIPAA, FedRAMP, SOC 1 and SOC 2, as well as country-specific standards, such as Australia IRAP, UK G-Cloud and Singapore MTCS.
Recursyv does not retain data beyond the time when it is in transit. Data in transit is encrypted using a 256-bit encryption algorithm, with the encryption keys being unique to each integration tenant.
Configuration data is stored behind firewalls ensuring only a restricted set of IP addresses can access it. Configuration data is also encrypted using an industry standard 256-bit encryption algorithm and a different encryption key set to those used for data in transit.
Data Residency as Required
Recursyv is deployed in a number of geographies across the world, from the Americas to Australia. The service can be configured on a customer by customer basis to constrain all data to a particular geography (in order to meet regulatory requirements for example) or to allow cross geography processing to provide a greater level of redundancy.
Flexibility by Design
Applications and their data change and evolve over time, and the services around them need to do the same. Recursyv is designed such that data transformations and mappings are achieved using no-code configuration meaning that they can be changed quickly and easily as your application estate changes.
The message bus architecture also allows for a natural disconnect between applications allowing them to change relatively independently of one another. This prevents customers needing to commission large change projects to resolve complex data dependency problems between platforms.
Recursyv uses dynamic connector plugins to talk to platform APIs. Connectors can be used out of the box, modified or created from scratch in order to meet almost any requirement or to connect to any end point.
Connectors are built on a foundation designed to support common SaaS API protocols, including RESTful, SOAP, RDMS and ODMS which means that creating a connector is a quick process. Data formats are interchangeable (between JSON, XML etc.) allowing us to easily sync data between different platform stacks and environments.
Custom connectors can be written quickly to either connect to bespoke applications or to perform very specific operations or processes as required.
Foundation connectors have been built for common protocols, allowing us to quickly connect thousands of well-known applications. When we build new application connectors, this is where we start.
Platform connectors are built and ready to be deployed to connect to popular industry platforms.
Microsoft SQL Server