Our customers are often asking questions about the Nouvola product infrastructure and how it works. Since there are several recurring questions, we wanted to share the answers with all our readers.
Is the solution cloud-provider specific?
Nouvola DiveCloud is completely cloud agnostic. The application being tested can reside with any cloud provider. Additionally, it can be on a private cloud or a public cloud, it can be over multiple providers or multiple platforms. DiveCloud is looking at the application as a user would do, and therefore does not require any knowledge of the system internals.
Is the solution stack specific - i.e. Java, Ruby etc.?
Because Nouvola DiveCloud is generating (virtual) users launching http traffic or sending Restful API calls, it does not need to know about the internals of the application being tested, including stack specifications.
Is there anything to install in order to use solution?
Nouvola DiveCloud is a pure SaaS solution, and therefore does not require any installation. Just log in into the system to create and run your tests. There is nothing to install, nothing to set up and nothing to provision.
Note: If used together with Nouvola DiveData (Nouvola’s Predictive Performance Analytics tool), it is expected that a monitoring agent is installed with the application to collect data white performance tests are running. However, this module is optional and not required to create and run performance tests.
Are you located on a specific datacenter?
Our solution is distributed over all AWS regions, and can therefore generate users from each of them. This allows for more realistic scenarios, where users can come from different parts of the world. Since AWS keeps adding regions (like the one just recently announced for South Korea), we’ll continue to expand to AWS regions, as well as to other cloud providers.
When running a test, is the traffic real or simulated?
The traffic generated during the test is real, but the users generating it are virtual. The traffic is often based on recordings of user scenarios (called Sessions in DiveCloud terminology). This is meant to provide scenarios that closely resemble real-world traffic to enable meaningful test results. It is possible to have different types of sessions combined together in a single test, and to have different virtual users generating the traffic. This is often the case in real life, where users accessing an application can be grouped in different types of user behaviors. DiveCloud can also randomize some of the data generated in order to avoid triggering caching mechanisms.