In this quick video tutorial, we will show you how to manage your account resources and applications using the Playground environments.
Before we have a more thorough look at what are environments in Napptive, we should first define them. The definition of an Environment is understood as a delimited set of resources to deploy an application. The most common examples are:
These are three environments that we can usually find in dev teams. The goal of having different environments can vary from team to team, and switching to cloud-native dev environments brings many benefits such as:
- Extra isolation for each environment
- Built-in infrastructure for monitoring, alerting, profiling, tracing, and log aggregation
- Scaling of cloud environments when you need more resources
There are many more reasons why you should switch to a modern, reliable, cloud-native experience, and. the naming around environments can be adapted to the specific needs of each user to better represent their workloads and uses cases. For example, an environment named operations or monitoring may contain applications that are used to monitor a set of resources or to deploy internal tools that support the development process. In the same way, for a consulting company, the environment name may reflect the final client. For example, deploying static webs for different clients may be done using
client-i-web as the name for the different environments so that it is clear to whom the applications are associated, and at the same time having an isolation layer between them.
If you would like to see an in-depth review of what Environments in Napptive are and how to use them, we encourage you to take a look at our expanded post.
If you want to propel your development, why not try our playground? It’s free, simply sign up and get started!