GDPR has been in place for years now, and we’re starting to learn more and more about how it’s going to be enforced and what it really means. The many questions people had that could only be answered by court decisions have now been answered. Over the past years, I’ve seen systems try and fail to correct implement GDPR. Here are the things I’ve learnt from court decisions and from mistakes made.
If you want to operate within the EU you need to follow the strict data privacy law, GDPR. And many of use are searching for the best GDPR compliance tools.
Some of the things you need to pay attention to with GDPR are:
I'm month two into my 6-month project to build 6 SaaS applications in 6 months. I started work on the 2nd SaaS a month ago, and it's Blether.chat - a GDPR Compliant Live Chat that integrates with Slack. How did I come up with the idea for Blether? I hate cookie consent banners so I don't want to have them on my site, but at the same time, I wanted to be able to chat with potential customers for Parthenon. Therefore I needed one that would allow me to do that without adding a cookie banner. The answer is Blether.
A few days ago I saw someone ask if Sylius was a good eCommerce system to use, which it is. And my first thought to head was "Of course because it's Symfony based." then I wondered what the options and systems built on Laravel and thought it would be interesting to list out were. So here we are. I'll go through the systems I know of for various categories for both Symfony and Laravel.
I'm currently developing a cookieless Free Live Chat SaaS - Blether.chat and as part of the development process, I decided to stress test the application and really see the difference PHP OP Cache preload made to the request per second in a real-world application. This led me down a path that resulted in me making a configuration change unrelated to the OP Cache resulting in an almost 100% increase in throughput and adding 200+ requests per second to my server's capabilities.