Flownative Blog

Flownative is not a web agency taking a lead on typical projects like creating new Neos websites. We usually work well in the background providing guidance, code and knowledge. But Flownative Beach is a project, we did take a lead on – we invested more than 3.000 hours of thinking and coding before we opened our platform to the broad public.

So, this year, we thought: why not hand in Beach for the Neos Award?

The technical side of the Neos release process is a wild mixture of automated and manual tasks. Some areas are properly documented and some are just known to the elders of the tribe. In fact, I was probably the one, who has a broad overview of the process and tools… until this week.

Beach is great for keeping your client in the loop about the progress of her project. Since everything is automated, it's easy to deploy a new feature – even if it's just a new button – as soon as it is ready. And because you want to launch a bunch of features at once, your are not deploying to production yet, but use a dedicated staging instance.

As promised by the PHP release team, PHP 7.3.0 was released on schedule as a nice present for St Nicolas' Day. I have been testing the release candidates with Neos and Flow during the last couple of weeks. How did it go?

What’s New In PHP 7.3?

It is a false assumption that, just by moving an application to the cloud, it will run faster. While it is much easier to scale an application there, effects from a weak application architecture, massive amounts of database queries or unoptimized storage usage can actually make things slower. When you run your whole application, including database server, key value store and storage, on a single machine, you won't notice many of the performance issues which surface in scalable environments.