Check out their CFO discussing the above on YouTube, or feel free to message me if you are in Asia.
EPHEMERAL ENVIRONMENTS INSTALL
Better still, setting up the ephemeral environments with Bunnyshell for the whole team would take only a few hours, as everything runs on the existing infrastructure, without the need to install anything new. Either way, costs would be saved in the process, because the environment only ran for the necessary amount of time. Once the testing is done, the code is further pushed to production if no errors are found, or an error report is generated and sent to the developer, and the environment is shut down automatically. In this case, everytime a developer is pushing new code, an ephemeral environment is automatically launched to do all the necessary testing. It does not get more automated than that. The API development company has a fully automated CI/CD pipeline in place, where once the code is pushed, and if it passes all the tests, it is automatically served in production.
We are going to look at 2 companies today, one developing APIs (the company asked to remain anonymous, as they are currently evaluating the technology), and a second one building a customised music service in New Zealand.
Is your CI/CD automation pipeline running 24 hours, although you only need it when you push new code? Or is the developer team waiting in line because they share testing environments? Current article is looking at how ephemeral environments can be used to speed up testing on a production-like environment at a fraction of the existing cost.įor the sake of this article I am using the Bunnyshell ephemeral environments that include all the infrastructure components and the cloud native services, like lambda, serverless, virtual machines, managed databases, API gateways, as well as the applications and their dependencies, including the data.
0 kommentar(er)
