Best Practices
  • 17 May 2022
  • 2 Minutes to read
  • Contributors
  • Dark
  • PDF

Best Practices

  • Dark
  • PDF


This article discusses the best practises that can be set up for the private hosted environment.

High Availability

Serverless360 will be in charge of monitoring and managing the customer's Azure environment. As a result, it's critical to keep the Serverless360 instance up and running at all times.

Since the private instance of Serverless360 is entirely hosted in Microsoft Azure, the resources used to host it have their own configurations to ensure high availability.

The following Azure services are responsible for the private environment of Serverless360:

  • App service
  • SQL
  • Storage account
  • Service Bus

App Service

  • Web apps and Function apps will be created as part of an App service plan to host the web application and run background tasks.

  • All Web apps and Function apps will be hosted under a single App service plan because it is a private single-tenant application. As a result, only the App Service plan must be highly available, and users can accomplish this by utilising Azure's Zone redundancy feature.

  • The Serverless360 plan will be created in the Standard tier by default. Customers must deploy a new Premium-tier plan using an ARM template to achieve Zone redundancy.

  • The template format and details are available here.

  • Once configured, Web apps and Function apps will be accessible even if an Azure zone fails.


  • All the data and configurations related to Serveless360 will be stored in an Azure SQL database.

  • Azure SQL by default comes with a restore and backup mechanism which will be available for the last 7 days and users can restore a backup at any point in time.

  • In addition to backups, a feature called Geo-replication and failover. can be used to handle Azure zone failures.

Storage account

  • The artifacts related to Serverless360 Web apps and Function apps will be stored in a Storage account as blobs and files.

  • Azure provides a geo-redundant storage tier to handle Azure region failures.
    GRS is enabled by default on the Storage account created using Serverless360. As a result, high availability will be maintained in the event of a failure.

Service Bus

  • Customers using Serverless360 BAM will have a Service Bus deployed in their Azure subscription. This is responsible for transferring unprocessed data between different services to process and store it as transactions.

  • Service Bus offers geo-recovery to handle any regional disasters.

  • Serverless360 will deploy the Service Bus namespace in the Basic tier by default; however, users can upgrade to the Premium tier to use the geo-recovery feature.

Custom Domains

  • Azure Web Apps comes with an auto-generated domain name by default, but custom domains can be created as well.

  • Two web apps will be developed for Serverless360 private hosting to deploy single-page applications and web APIs. The web app name is given a unique value that includes the customer's identity.

  • As a result, customers who use custom domain mapping should map both web apps to domains in the following format:

Default domain Custom domain
sl360-{customerid}-frontend-webapp serverless360.{customdomain}.com
sl360-{customerid}-backend-webapp api-serverless360.{customdomain}.com

Was this article helpful?

What's Next