Because you can set up a rudimentary queueing system in MySQL/PostgreSQL very quickly these days. And it scales really well for small to medium sized applications!
I maintain a web application with a few hundred daily users and with the following table I have never had any problems:
CREATE TABLE `jobs` (
`id` BIGINT NOT NULL AUTO_INCREMENT,
`queue` VARCHAR NOT NULL,
`payload` JSON NOT NULL,
`created_at` DATETIME NOT NULL,
PRIMARY KEY `id`,
INDEX `queue`
);
Using MySQL's LOCK and UNLOCK I can ensure the same job doesn't get picked up twice.
All in all, it's a very simple solution. And simple is better!
Worked at a place where the lead engineer was adamant a graph database was the solution. After two years of trying to get it launched, the project failed spectacularly.
Another team got given the rewrite and build it in six months using MySQL.
I should clarify that I see the value of encryption at rest for something like an employee laptop, which could be left at a bar (while powered off) by accident.
I just don't get the value of it for always online servers.
This might sound like a stupid question, but I'll ask anyway:
What benefit does encryption at rest solve for something which is never intended to actually rest?
For example, a MySQL database powering a web application is expected to be alive and responding to requests 24/7. It's never really intended to be at rest.
So what benefit does encryption at rest bring? Won't a hacker be attempting to take data when it's online (and therefore not resting)?
Stick with the LAMP/LEMP stack. It's not perfect, but if you're moving from WordPress (which uses the LAMP/LEMP stack) then sticking with it will make the move less painful.
In terms of a framework. Laravel is a good idea for RAD, although Symfony is a fine choice too!
---
Frontend:
Assuming is has to be a SPA: Use whatever you know best. React, Vue, or Angular are fine. Laravel seems to prefer Vue slighty?
If you can get away with SSR: Use a templating system. Assuming you're using PHP, you could use Blade (for Laravel) or Twig (for Symfony).
---
In terms of hosting and deploying, use one big VM for as long as possible. It's not better, but it's simpler... and I'd say you've got a lot on your plate!
---
But to answer your original question:
If you stick with LAMP/LEMP and a framework, there is so much documentation (and so many guides) that you will be able to figure out what to do. :)
Allows you to run a Raspberry Pi Zero from 8 AA batteries!
I can't remember where I'm getting this figure from, but I think it accommodates for about 3 days of runtime (obviously dependant on what you're doing with your Pi!).
You might need to use StuffIt to uncompress the SIT files. But when booting Infinite Mac there's an option to include common applications, of which StuffIt is one.