A couple weeks ago at WHDusa we introduced a our reliability and vulnerability extension for Plesk based on our VCTR service. We were excited to work with Plesk because of their expertise and large loyal customer base. However, we only got the go ahead to build the extension a few weeks before the conference and that lead to one of the amazing aspects of the release, it was written in just three weeks.
It’s always a great feeling when things come together seamlessly, and this was one of those experiences. We completed the work in two stages. The first was a prototype completed in under a week which we could use to show the Plesk folks our vision and get feedback. That took just a week. The second stage, our first production release took just two additional weeks.
Unlike other integrations we’ve worked on in the past, the Plesk integration only required a single engineer to complete (granted Stephen is a top notch senior engineer, of course). Our work went quickly because Plesk did an awesome job anticipating our needs for writing extensions.
A prime example the thought Plesk put into the extension architecture is the complete environment of tools for integration, which includes:
- A formal extension structure for packaging
- Command line utilities that are accessible through the API
- XML API
- Key value storage
- UI elements rendering
- Event handler
- Scheduled tasks
We had very little need for support because everything was easily locatable in the documentation, but the few question we did have were quickly answered by the Plesk support team. They even reviewed and provided useful comments on prototype in a day.
Plesk proved themselves a great partner while we built the extension. They’ve thought out the requirements, provided great tools and prompt thoughtful support. All in all, a great experience.