Although we don't want to discuss the product in too much detail here, let's take an overview of the capabilities of Serverless360. The product was first named ServiceBus360. Before capabilities for other Azure technologies were added to the product, it solely contained features to do with the operation and monitoring of Azure Service Bus queues and topics. By also bringing in security features, such as access policies and auditing, scheduled bulk-send message features, and data monitoring features, the product has become a powerful and secure choice for day-to-day use of Azure Service Bus.

The product is still in development, but Serverless360 currently has features that support the following Azure technologies. For each technology, only the most important features are mentioned:

• Service Bus: CRUD operations on queues or topics, viewing or resubmitting dead letter messages, purge messages, bulk scheduling (dead letter) messages, state-based monitoring
• Function apps: CRUD operations, state-based monitoring, viewing invocation logs
• Logic Apps: CRUD operations, running triggers or viewing trigger history, state-based monitoring
• API apps: Threshold monitoring
• Event hubs: CRUD operations, importing event hubs, creating or deleting consumer groups, state-based monitoring
• Azure relays: Managing and importing relays, state-based monitoring

We know by now that a serverless solution can comprise multiple types of many different Azure components. From a monitoring and operating perspective, it is not very efficient to use the Azure portal to operate all these different components, as these components are to be found in many different places in the portal. It would be more effective to treat these components as one application. Because of that, Serverless360 introduced the concept of composite serverless applications, which allows you to group all these different components to the same composite application.