Hosting options & portability — found from sitemap — Frends

Cited by

Facts read from this source

• Deployment models Report an error

  “Choosing a Deployment Model Self-hosted Deployment PaaS Deployment Container Deployment Hybrid Deployment”

• Hybrid platform Report an error

  “At its heart, Frends is a hybrid integration platform — meaning all deployment styles are built on the same flexible foundation, and you can freely mix and match them as your needs evolve.”

• Default paas agent Report an error

  “Every Frends Tenant already comes with a PaaS Cloud Agent in the Development Environment, so you can begin building without making any infrastructure decisions upfront.”

• Selfhosted agents location Report an error

  “in self-hosted deployment the Agents reside on your own servers and computers as a service, or in your own cloud environment outside Frends cloud.”

• Selfhosted connectivity Report an error

  “In this deployment type, connections to your Frends Tenant are done through Azure Service Bus messaging.”

• Selfhosted UI unavailable Report an error

  “Even in the situation where the Frends UI would be unavailable, the Agents will continue execution without problems.”

• Selfhosted customer control Report an error

  “In this deployment model you are also in full control of the infrastructure, maintenance, updates and monitoring”

• Paas managed by support Report an error

  “the Agents will be created to Frends cloud environment by Frends Support, and the support is also then responsible for managing and maintaining your Frends execution environment.”

• Paas geo hosting Report an error

  “Depending on your subscription tier, you can control geographically where your environment is hosted, in order to keep up with legislation about data processing and storage.”

• Paas resource sharing tier Report an error

  “With higher tier you can also select how the resources for your execution environment are shared.”

• Tenant isolation Report an error

  “different Tenants cannot access each other's data in any event, even if they are processed on the same shared resources.”

• Container kubernetes Report an error

  “While it has long been possible to deploy Agents as containers in Kubernetes clusters, latest versions added support for dynamic launching of additional containerized Agents when required by allowing unspecified Agents to connect to Agent Groups at will.”

• Container onprem or cloud Report an error

  “While it does not matter if the Kubernetes cluster is located on-premise or in the cloud, it also does not matter if the containerized Agents are used with other on-premise or cloud Agents.”

• Container statefulsets Report an error

  “You may also choose whether the automatically deployed Agents are deleted from the Agent Group once the Agent goes offline, or not. This enables the usage of Kubernetes Stateful Sets”

• Hybrid mix Report an error

  “By default, Frends comes with a PaaS cloud Agent as part of the development environment on all tiers. From there, you can either install more Agents to your own server or cloud environment to create a self-hosted deployment, or request more PaaS Agents to be added to your Tenant from the Frends Support”

• High availability kubernetes Report an error

  “If your pricing tier and contract allows, setting up a Kubernetes cluster for your Agents and having them in High Availability configuration is also possible.”

• Local agent execution Report an error

  “Running a Frends Agent on your own computer is also totally viable method to run Processes locally”

• Selfhosted data sovereignty Report an error

  “Self-hosted deployment is essential when you require strict data sovereignty, compliance, or have security requirements that disallow the data being located outside your internal network or geographic location.”

• Remote subprocess servicebus Report an error

  “In case interoperability between Agents are required, for example when calling Subprocesses remotely over Agent Groups, these are also coordinated over the Service Bus messaging”

• Dotnet runtime Report an error

  “Along with .NET runtime it will handle the triggering of Processes.”

• Paas connectivity Report an error

  “Because the execution environment is in the cloud, connectivity to and from outside sources will not require any additional setup or thought, it just works.”

Scores citing this record

• The Data Protection Officer Execution, error handling & monitoring
• The Data Protection Officer Hosting options & portability
• The Data Protection Officer Pricing transparency
• The Data Protection Officer Execution, error handling & monitoring
• The Data Protection Officer Hosting options & portability
• The Data Protection Officer European sovereignty
• The Head of IT Execution, error handling & monitoring
• The Head of IT Hosting options & portability
• The Head of IT European sovereignty
• The Head of IT Pricing transparency
• The Head of IT Hosting options & portability
• The Integration Engineer Connectors, API & on-premise reach
• The Integration Engineer Hosting options & portability
• The Integration Engineer Execution, error handling & monitoring
• The Integration Engineer Hosting options & portability
• The Integration Engineer Pricing transparency
• The Operations Analyst Execution, error handling & monitoring
• The Operations Analyst Hosting options & portability
• The Operations Analyst Execution, error handling & monitoring
• The Operations Analyst Hosting options & portability
• The Process Owner Hosting options & portability
• The Process Owner Connectors, API & on-premise reach
• The Process Owner Execution, error handling & monitoring
• The Process Owner Hosting options & portability
• The Process Owner European sovereignty
• The Skeptic Execution, error handling & monitoring
• The Skeptic Hosting options & portability
• The Skeptic Execution, error handling & monitoring
• The Skeptic Hosting options & portability