Coconut Tickets WordPress to Laravel Migration – part 2
Part 2 - Strategy
I explained the motivation to migrate the Coconut Tickets event ticketing platform from WordPress to Laravel. The implementation of the ticket design tools and transactional services of Coconut Tickets are achieved with one huge WordPress plugin. Coconut Tickets regularly sells events of ten thousand tickets at a time and the Laravel application would need to do the same. Before you think we took on too much in this migration, let me also explain that having done many migrations before (with other technologies) I had a strategy in mind that would help to control the chaos of such a big technology change. The strategy could be summarized as:
A technology migration, like this, is very complicated. If the complexity becomes too much then the project turns into chaos. Therefore, the key to avoiding this is having a strategy to manage the complexity and reduce the chaos. The biggest risk in a project of this kind is getting lost in the complexity of the task, resulting in either giving up finding that the task has become a development project. This is why I thoroughly support the idea of getting something basic working as soon as possible. It also means that you don’t have to have all the answers before you start, or at least you can change your mind on the strategy if early tests don’t work. The technical spikes are very good for this, each one is a specific test that is chosen to prove a particular part of the technical strategy is working. Here are some of the technical spikes (tests) we defined at the beginning:
In the next part of this series we will look at the technical migration details and the important technical decisions that were taken.
Find out more about