The common struggle that Azure users undergo is managing their cloud estate. As the investment in the cloud grows this problem is compounded and they quickly find that the estate becomes so complex they lose sight of what it looks like and how it relates to their overall architecture. At this point, the customers come up with requests like,
1. We would prefer to view and govern all the resources under one roof.
2. It would be better to have a clear view of the cost spent on them.
3. How to avoid resource junk?
By understanding the customer needs, Serverelss360 has come up with a new feature, Resource Map.
Resource Map is a platform to visualize and govern Azure resources originating from different subscriptions at one place.
Azure resources from different resource groups can be grouped under a single scope. These Azure resources are accessed via service principal associated with the Serverless360 account.
Resource Map deals with different attributes like,
- Resources- It holds the synced Azure resources from various subscriptions and resource groups.
- Scopes- Scopes are logical containers where user can group resources from multiple subscriptions and resource groups.
- Environments-Environments are again logical containers into which the Azure resources can be grouped. For example, Development, Production and Staging are different environments under a scope.
- Logical Resource-Logical Resource is a logical entity that is used to map physical resources from different Environments of the same resource type.
- Rules- Rules will allow to auto allocate resources to scopes, logical resources and environments. It minimizes the overhead required to maintain your Resource Map.
- Cost- Graphical representation of cost spent for a specific period on a resource, resource type and environment
Why Resource Map?
Consider a scenario in which the Azure portal is set up to give a layout and deployment model where the resources are placed based on the optimal physical deployment model. This is great for the management of the physical architecture but requires significant knowledge of both Azure and your physical architecture to effectively use the Azure Portal to manage your resources. The physical view is only one of the important ways of looking at your IT estate and with Resource Map we provide a way to map your underlying complex physical architecture to a much simpler logical model of architecture. This then allows to view your estate in a new way and demystifies a lot of the challenges people have in understanding their cloud estate.
How is Resource Map different from Composite Application?
Every Serverless360 user would need an answer to this question. Composite Application is an entry point to manage and monitor the supported Azure Integration services, Resource Map facilitates governing all Azure resources by organising them under scopes and environments. Resource Map can accommodate all Azure resources to provide their cost visualization.