throwaway38375

Well done to your daughter! She is clearly a smart one. I wish her the very best for her future career (possibly) in computers. :)

Looks like the average connection is somewhere between 10 and 30 Mbps?

Seems enough for browsing the internet, online banking, emails, some social media, and watching videos in standard definition.

That sounds like enough for the average person. :)

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 love SQLite, so please don't think that I'm a SQLite hater, but:

I've never seen SQLite used in a setup which multiple machines connect to the same database over a network.

For example: A web application with a web server, a worker/job server, and a database server.

In these instances MySQL or PostgreSQL seem to be much better choices.

So will SQLite ever be able to "take over" in these scenarios?

Neat! This is exactly what I'm planning to do one day.

How did you find the development experience? Anything that you would change or do differently?

Also, how does Kaboom/Kaplay hold up under load with lots of sprites? I've hit a few performance problems with my game when rending lots of sprites...

Yes! Windows got it right IMO.

Ah, I see. Thank you for explaining. This is much clearer.

Good point.

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)?

I don't think you can swap bits out. When I used it things seemed baked in. Yes, mainly suited to 2D side or top down view games.

Backend:

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. :)

Very excited about this, I have the best memories of using Kaboom.