undefined | Better HN

0 pointsandyjones113y ago0 comments

Elixir, Phoenix, LiveView + Postgres

Main reasons are:

- Can build entire app (with SPA-type experience on the FE) in a single codebase

- No need to build any HTTP APIs

- Periodic tasks and managing in-memory state is super easy in Elixir. Eventually you might want to stick state somewhere which survives restarts (eg redis) but for the sake of moving quickly Elixir makes this really easy

- Newer versions of Phoenix/LiveView support html components so building out UIs now feels as nice as some of the tools in the FE ecosystem

0 comments

3 comments · 2 top-level

kcartlidge3y ago· 1 in thread

I like Phoenix/LiveView so it's a nice option.

But I'd probably choose Blazor over it as every one of those bullet points also apply to it, it's C# (with which I'm very familiar), and if it takes off there are masses of devs available in most markets as opposed to handfuls currently for Elixir/Phoenix.

Coupled with something like DO droplets and SQLite/Postgres.

pcthrowaway3y ago

I have no experience with either (though I have perused some Elixir docs a while ago). I'd much rather jump into a Phoenix/Elixir project though, just based on what I've heard and know about it.

I wouldn't apply to a C# job, I have no interest in it.

I think the only disadvantage is really that Elixir devs would be newer to Elixir. But I think the applicant pool would skew towards having broader experience.

danieka3y ago

Depending on your use case you could consider using SQLite. For example storing auth info in a central database and then having one database per customer.

j / k navigate · click thread line to collapse