Flownative Blog

Today we have made an adjustment to the automatic scaling of Beach instances. This post explains the background and explains the effects.

An instance can be automatically scaled horizontally in Beach in order to be able to react to fluctuating loads.

For this purpose, the minimum and maximum number of replicas can be defined, as well as the CPU load, which triggers scaling up if exceeded.

Settings for the automatic scaling of an instance cover auto Einstellungen für die automatische Skalierung einer Instanz

Last Friday, we had a major outage at Flownative Beach, which took around 30 customer projects offline for about an hour and a half. We would like to explain transparently what happened, how we dealt with it and what measures we are planning for the future.

This year's Neos Conference was once again a very special event. Many volunteers turned a simple conference room into a colorful event location where the Neos community celebrated the release of Neos 9 after years of development work. AI was of course a theme that also ran through many of the talks. However, the focus was on presentations about the current future possibilities of Neos.

An exciting week comes to an end for me: The Neos team met in Vienna for a crucial sprint to finalize the remaining open items for the eagerly anticipated Neos 9.0 and Flow 9.0 versions. I had the privilege of representing Flownative on-site, while Karsten, Christian, and Markus worked intensively remotely.

Responsibly sourced: The new Event Sourced Content Repository

Regular backups are made automatically for all Beach instances. If something goes really wrong, it was previously possible to quickly restore the working state via a support ticket. So that you can now do this yourself at any time of day or night, there is a new feature in the Control Panel - and it can do even more than just restore backups!

In the Control Panel, you will now find a “Backups” section where you can see all available backups:

cover auto