HN user

bradmwalker

78 karma
Posts3
Comments34
View on HN

An undersold benefit of GraphQL is minimizing JavaScript footprint on domain logic. This can be hidden in the API by precomputing many things, and client-side logic can be reduced to presentation and event handling. Hand-rolled data munging and client-side caching are n't necessary, and there's a clean separation between the browser and the backed.

Another red flag on redux: recommended practice--query JSON over HTTP (likely backed by an RDBMS), renormalize the hierarchical data, and then reshape the renormalized data before passing to components.

Try CREATE TABLE UNLOGGED with postgres. The diversity of RDBMS and SQL dialects defeats the point of integration testing the persistence layer with SQLite.

For single-node applications, I develop on a LXC setup with a base template of the distribution that will run a production VM. This combination provides maximum dev/prod parity, the benefits of lightweight virtualization for development, and a boring, battle-tested production environment. The setup and deployment is written once for the choice distribution.

What about LXC system containers? Differences between hardware and OS virtualization still exist, e.g. immutable system clock, but it's otherwise like running a regular Linux box. An init process that can simulate rebooting, mature system package management, no process isolation that's often gratuitous, etc.