futureSAX: TYPO3 upgrade & dockerisation of the platform

TYPO3 is one of the most secure content management systems (CMS) on the market. To keep it that way, the system should receive regular updates and upgrades. A TYPO3 upgrade is a regularly necessary step to ensure security and performance in addition to the introduction of new functions. With the upgrade, futureSAX relies on up-to-date, legally compliant software (in accordance with the IT Security Act) that fulfils the highest security requirements. In addition, future maintenance and further development of the platform can be implemented more sustainably and therefore more cost-effectively for the client.

TYPO3 upgrade at futureSAX

In the course of the TYPO3 upgrade from version 9.5 to 11.5 at our customer futureSAX, all other components were also upgraded to a new version in addition to the core update:

• TYPO3 Extensions:
  • 21 Community Extensions
  • 26 custom extensions
• PHP version 7.3.33 to 8.1.19

Before upgrading, you should check whether the community extensions used in the project are already available, i.e. compatible, with the desired new version. If this is not the case, it is sometimes advisable to wait a little longer before upgrading for cost reasons. However, we can implement a customised solution for missing community extensions at any time in order to guarantee our customers full functionality.

A TYPO3 upgrade usually raises the TYPO3 project to a higher quality level, facilitates future development and maintenance and thus saves costs for operators in the long term. As an experienced TYPO3 agency, Netresearch not only takes care of the pure upgrade of the CMS, but also optimises other technical components of the entire web project in the same step, e.g:

Splitting the monorepo into one repo per extension

1. Modularity and reusability:
   Modular structure in which all extensions are organised in separate repositories. This promotes the reusability of code and facilitates the management of independent modules.
2. Easier management of dependencies:
   The use of multi-repos enables a clearer definition of dependencies between different modules.
3. Better testability:
   The clear separation of modules means that tests can be carried out in a more targeted and isolated manner. This makes it easier to test individual components independently of each other and improves the overall quality of the code
4. Easier collaboration:
   Multirepos can facilitate team collaboration, especially when different teams are working on different modules. Each team can concentrate fully on its own tasks without coming into conflict with changes made by other teams.

Connection of Customer Relationship Management (CRM) through own API/SDK

1. Modern solution:
   With a new SDK and an associated API extension, we were able to replace the outdated legacy code with a modern solution.
2. CRM independence:
   Should the connected CRM change in the future or should there be changes to the CRM's API, adjustments can now be made quickly and easily to maintain the full performance of the integration. A move to another CRM service provider would now also be much easier for futureSAX to implement.

Dockerisation of the futureSAX platform

futureSAX was acquired by us in 2021 and had not yet been able to benefit from the advantages of a Dockerised infrastructure. Many agencies still run the TYPO3 project directly on the server without using a Docker structure. We work on TYPO3 projects in a Docker-based structure and so there is no longer any difference for the customer between the project working in the developer's development environment and the function on the actual LIVE system.

In this way, the client is strongly decoupled from the requirements offered by their hoster. In this way, outdated PHP or database versions that are no longer supported by the hoster can be provided by us for even longer.

In the event of a very critical security vulnerability, the customer no longer has to wait for the hoster to respond, as we can, for example, automatically apply the PHP fix immediately. The application, database, web server and other components were therefore also dockerised directly as part of the upgrade.

Advantages of Dockerisation

1. Portability:
   The application can now be easily ported between different environments in which it is to be executed.
2. Isolation and independence:
   Each Docker container is self-contained and isolated from other containers as well as the host environment. This allows our developers to manage different parts of the application in separate containers without them affecting each other. This isolation also makes it easier to manage dependencies, as each application can have its own required resources and libraries.
3. Consistent development environment:
   By using Docker, developers can ensure that their development environments are consistent with production environments. This minimises problems that can be caused by different environments and makes it easier to identify errors early on in the development process.
4. Automation and Continuous Integration/Continuous Deployment (CI/CD):
   Dockerisation facilitates the automation of build, test and deployment processes, resulting in accelerated development and improved CI/CD practices.

More about CI/CD:

• Automated CI/CD pipelines for a banking infrastructure
• Nightly builds and automatic updates thanks to Docker and CI/CD

Improvements of TYPO3 v11 compared to the previous version

1. Optimised editing environment:
   An improved user interface facilitates work in the editorial system and makes it more flexible and intuitive.
2. Increased security:
   This is implemented with two-factor authentication for backend and frontend users.
3. Improved performance:
   Performance improvement through code optimisation of the TYPO3 core and renewal of frameworks and libraries used.