Changelog
November 2, 2024
#16
Performance and flexibility remain at the top of our list. We are making it possible to: bring Noop to your existing AWS account, keep the Noop console experience fast, and run Task code in response to a successful deployment.
Contents
Performance is the Product
The Noop Console is reactive to the core. There is never a need to refresh the page to get an updated view. This has been the default on the Console since the beginning. But for involved technical reasons, which I hope will be the topic of a future blog post, the technique used to accomplish that reactivity was no longer adequate.
As our systems grew, the speed of that reactivity started to slow. We knew the longer we waited the more performance would suffer. We addressed the problem by rolling out a new approach for managing streaming state updates. The bottom line: the Noop Console continues to have blazing fast reactivity and the system that supports that reactivity will scale as we grow.
After Traffic Lifecycle Hook
Deployments are often more than just a code change. Noop has long supported lifecycle Task hooks to perform deployment procedures for non-code changes, think database migrations and cache busting. Last month we released the AfterTraffic deployment lifecycle hook. The AfterTraffic hook allows developers to run a one off job once a Deployment becomes available for traffic.
Until now, Noop supported two lifecycle Task hooks: BeforeServices (often used for migrations), and BeforeTraffic. AfterTraffic gives developers even more control over deployment-related operational processes. One notable example of what AfterTraffic might be used for is cache invalidation. A cache that is invalidated after traffic ensures the content available in the cache is generated by the code that was just deployed.
Choosing a Cloud
Enterprise customers that come to Noop are not usually looking for a new cloud. Enterprises are however looking to improve and expand their existing cloud capabilities. We have been steadily laying the groundwork to support connecting Noop to existing AWS accounts.
By bringing Noop to your own cloud, you’re able to take advantage of your existing cost management practices such as Reserved Instances, Enterprise Discount Program and the like. Apart from the cost benefits, you’re able to maintain the same data residency and network security standards.
Desktop Enhancements
Desktop releases 0.16.0 and 0.17.0 were shipped in October. These two releases enable choosing a cloud (see previous heading) and improve the overall performance of the application, while also reducing its size.