Hartley Charlton
Culturet Code Today announced that he had revised the cloud backend in a popular management app. />
Cultured Code explained that the transition to the new SWIFT-based infrastructure occurred smoothly and without any violations for users. Although the behavior of the application remains unchanged on the surface, the main service that synchronizes the lists of affairs throughout the iPhone, iPad, Mac, Apple Watch and Apple Vision Pro were completely rewritten during the year and deployed in production for more than a year. While the initial synchronization algorithms remain untouched and are based on a mathematical model capable of resolving autonomous changes and conflicts, aging technology was increasingly considered an obstacle to future development. According to the cultivated code, the problems included the growing costs of the infrastructure, the slow response time and the risks associated with the dynamic set in Python.
Apple introduced Swift in 2014; Since then, it has been widely accepted for the development of applications for iOS and MacOS, but there is a limited absorption in servers. The cultivated code began to experiment with SWIFT on the server in 2021, initially rewriting isolated components before devoting itself to a full -scale restructuring. This double processing agreement allowed engineers to check the new sale in the conditions of production. After the team was satisfied with the accuracy and performance of the SWIFT bacand, they transferred all users to the new system in early 2024. The traffic of peaks up to 500 requests per second is currently processed by the Kubernetes cluster consisting of four knots, each with two virtual processors and 8 GB of RAM. This installation has led to a more than triple reduction in calculations compared to the outdated system. The response time of synchronization has also improved significantly, and the new architecture provides a four -fold increase in the speed processing rate of synchronization requests. The application is highly valued due to its design sequence and reliable experience in synchronization in the Apple ecosystem. Learn more about the change in the full message on the Cultured Code blog or its message about the blog Apple Swift.org.
