Sometimes we need millions, I mean gigabytes of test data, which are really close to the data we are using later for our new data application. There is a need for it because you want to test the performance of your stack, and you want to omit using real data because of data privacy and licence restrictions. Thankfully, there is a group of developers out there that have created a create tool called faker. Or should I say created a concept? Because it is implemented in various programming languages.
In this article, we will try out the faker implementations in…
Years ago, we’ve developed applications locally, install all requirements locally and when we think we’re done, it’s time to deploy. Which meant we’d to install all dependencies on the remote server and copy the application files to the server. We’ve used FTP, SFTP or rsync for that.
With version control systems like GIT, you can easily create tags and add some metadata, like release notes to it. Some of the biggest SaaS providers even give us an API to get access to this data, to work with it and for instance, place it on our an interface. But Docker has currently nothing equal to this, making providing adequate release notes a challenge. Of course, you can create tags, but there is currently (summer 2019) no way to add text and other additional data.
This article will scribble four ideas on how we’re approaching this problem to enable…
But which one should be the first? We have some experiences with Section, Amazon CloudFront and custom configured Varnish instances. But now it’s time to revalidate it! Let’s see what’s on the market and find the best CDN for Applications like Magento stores, headless Vue.js applications and other like TYPO3 CMS.
At first, let’s take a look at our essentials. Let’s focus on the things we really need. The things we can’t live without.