This month we want to share a glimpse into some of the work that goes on behind the scenes here at Canvasflow, enabling us to deliver a reliable, robust and responsive authoring platform.
Each month we highlight new features, improvements and bug fixes – but our team is also working hard in areas that may not always be visible; like our infrastructure and public API.
Application Monitoring & Logging
In 2017, we invested heavily in our monitoring and error reporting systems, used to keep things running smoothly. This provided us with more detailed application information, fine tuning of alerts and improved error reporting.
Hopefully you’ve never seen our friendly warning notifications, but if you have you can rest assure that our support team are made immediately aware and are already equipped to investigate.
These improvements – coupled with a meticulous support team – enabled us to respond to 58% of support requests in less than 15 minutes and 86% in 60 minutes or less.
We also stepped up our application logging game and added customised reporting tools. These are used by our support team and engineers to diagnose application issues even faster, enabling us to deliver super low resolution times.
Dashboard & API Uptime
In 2017 our dashboard and public API experienced uptime of 99.999% and in 2018 we’re continuing to invest in our services, making them even more resilient to handling an increasing number of requests. We’ve made our platform availability public which you can access it anytime.
Platform Optimisations & Data Caching
Platform speed is a key focus for the team and although speed has never been a reported issue, faster is always better, right?
Our latest 3.1 release included platform optimisations making Canvasflow feel faster and more responsive, especially for users outside Europe. Our initial production tests saw load time improvement of over 70%!
3.1 also saw data caching management improvements, so when a new platform update is released we can now ensure we deliver these new assets immediately, reducing the need for manual browser refreshing.
Behind the Scenes
I hope this provides a useful insight into the behind the scenes of the Canvasflow, along with a glimpse into the level of dedication and passionate contributions from every member of the Canvasflow team.
If you have benefited from the platform enhancements or have felt the platform getting faster and more robust, please let us know in the comments.