What are the best practices for configuring durable IOT Linux devices? Should I use an Overlay File System?

In the past our company used raspberry pi's for our IOT application. The problem with that was that SD cards wear out and get corrupt. We now ordered Compulab SBC's with eMMC storage running Debian. So what would be the best practices to configure durable embedded IOT devices? I would say: - Choose an SBC with eMMC storage - Make sure you have a journaling filesystem (has_journal is enabled on EXT4) - Write logs to ram to prevent wear on storage (in /etc/systemd/journald.conf Storage=volatile) - Ensure fsck runs at boot (in /etc/fstab the last field is set to 1 or 2) - Swap should be disabled (run free -> total Swap should be 0) Any more suggestions? Overlay file system ----------------- Raspbian has an option in 'raspi-config'->'Performance Options'->'Overlay File System' I asked Compulab if they would recommend also using it, but they think it is already as robust as it can be with filesystem journaling and fsck that runs at boot. Would using an Overlay File System to prevent writes to storage be worth the extra complexity of needing to reboot the device multiple times to disable it and enable it again if you ever want to update it later?