Biggest advantage with AWS – EC2 service, is that you are paying for each minute of usage. So – why run instances 24/7 if you need them only for 12 hours par day ? You can just start and stop whenever you need them. Obviously we don’t want to forgot to shutdown our instance, or start when we need it. Here is a simple recipe how to automate whole task
Mailgun is well known service provider which allows you send emails via their API or just using regular SMTP servers. SMTP protocol is bit slower, but it’s so common that you can use it everywhere. Each modern application allows you define your own SMTP server to send emails. But… we love speed, SMTP from it’s nature it’s bit slower then regular API call.
Caddy is a another alternative to Apache or nginx . For me the biggest advantage is that it’s only one binary file to work with. It’s easy to run, setup and just “works”. It’s super modern – handles HTTP2 and automatic HTTPS encryption using let’s encrypt certificates. Obviously it has plenty of other features but we focus only on speed of deployment.
From many reasons I was always using SQL_CALC_FOUND_ROWS to get total number of records, when I was running limited query. Never especially thought about it, until i had some super performance issues with one of my projects. Obviously after quick profiling and googling i found people complaining about FOUND_ROWS() low performance . I was not aware how big impact it was until I tested.
From time to time we could breach max_input_vars restriction. Which basically limitation for server which allows only limited number of input server to reach out server. Usually this number is around 1000. In this short tutorial I will describe, how to easily avoid this problem.
