Professional software engineer, musician, gamer, stoic, democratic socialist

  • 2 Posts
  • 36 Comments
Joined 2 years ago
cake
Cake day: July 2nd, 2023

help-circle




  • You might be surprised to learn that there are economies of scale at play here. If you want a managed application that has light traffic, then you can pay less for serverless than you would pay for hardware + wasted hours when the hardware is powered on but serving no traffic.

    I agree that there are some companies making poor decisions about which software they run in the cloud though. “Cloud mandates” are really stupid, because they’re basically just a trap where cloud providers offer a large amount of free cloud credits to get companies dependent on their platform.



    • Has a simple backup and migration workflow. I recently had to backup and migrate a MediaWiki database. It was pretty smooth but not as simple as it could be. If your data model is spread across RDBMS and file, you need to provide a CLI tool that does the export/import.

    • Easy to run as a systemd service. This is the main criteria for whether it will be easy to create a NixOS module.

    • Has health endpoints for monitoring.

    • Has an admin web UI that surfaces important configuration info.

    • If there are external service dependencies like postgres or redis, then there needs to be a wealth of documentation on how those integrations work. Provide infrastructure as code examples! IME systemd and NixOS modules are very capable of deploying these kinds of distributed systems.