Kokoen GmbH

I have never understood why using different vendors is such a big problem for many people. Each vendor is better than others for certain aspects, but no vendor is better than others for everything. At Kokoen, we usually host the applications we develop in AWS (EC2, RDS, S3), use Firebase (usually with OneSignal.com) for notifications, use Netlify for hosting certain SPAs, use Heroku to provide APIs directly from Git while we are still developing, MongoDB Cloud when we need NonSQL databases, etc..

After getting the first 400 registered users at https://tool-seo.com, we have decided to switch from the self-hosted version of MongoDB to MongoDB Atlas This decision was taken in order to reduce the time that we need for the maintenance and optimization of the Database, as well as to avoid server capacity problems as the number of users continue to grow.

#MongoDB

Back at the start of 2017, we decided to create a web-based tool for the SEO OnPage analysis of our clients' websites. We had over 2.000 websites to analyze, so we had to perform thousands of requests to get every single page from those websites, process the information and save the big amounts of data somewhere.

Very soon we realized that the initial chosen script language and database, PHP, Laravel and MySQL, was not going to be able to cope efficiently with such a task.

By that time, we were doing some experiments for other projects with a language we had recently get to know, Go , so we decided to get a try and code the crawler using it. It was fantastic, we could process much more data with way less CPU power and in less time. By using the concurrency abilites that the language has to offers, we could also do more Http requests in less time.

Unfortunately, I have no comparison numbers to show about the performance differences between Go and PHP since the difference was so clear from the beginning and that we didn't feel the need to do further comparison tests nor document it. We just switched fully to Go.

There was still a problem: despite the big amount of Data we were generating, MySQL was performing very well, but as we were adding more and more features to the software and with those features more and more different type of data to save, it was a nightmare for the database architects to structure everything correctly on the database, so it was clear what we had to do next: switch to a NoSQL database. So we switched to MongoDB, and it was also fantastic: we were expending almost zero time in thinking how to structure the Database and the performance also seemed to be better, but again, I have no comparison numbers to show due to the lack of time.

We also decided to switch the website from PHP and Laravel to JavaScript and Node.js and ExpressJS since working with the JSON Data that we were saving now in the Database would be easier.

As of now, we don't only use the tool intern but we also opened it for everyone to use for free: https://tool-seo.com