Agostinho1965

Agostinho1965

Hey everyone — I’m putting together a practical, code-first book on building production-ready business applications with Phoenix LiveView + Ash Framework + PostgreSQL. Rather than covering Ash’s API top to bottom, it’s built around one project: a multi-tenant business platform (tenants, customers, suppliers, orders, payments) with the working repo as part of the product.

Genuinely curious what this community thinks — is this the right angle, and what would make it a must-buy rather than a nice-to-have for you?

Showing Posts 1 to 8

FlyingNoodle

FlyingNoodle

I personally would find it interesting to have a book that focuses on a singular topic but in greater detail.

I don’t need 5 books that write to-do lists.

The meaty parts of ash are the policies, how you write custom changes and calculations, how to design your resources and relationships, etc. etc.

Those are the thinking parts that you can’t outsource to an LLM.

udoschneider

udoschneider

Count me in as a buyer :slight_smile:

I’m building an app like that right now; from my (currently limited) experience, things like authentication, RBAC, archival, paper trail, and AI are challenging. Using Ash packages makes it easier, but you still have to integrate all these parts in a meaningful way.

AndyL

AndyL

I would buy

dimitarvp

dimitarvp

Yep, I would buy it.

hyperoceanic

hyperoceanic

I’d probably buy it. I’ve got the Le/Daniel book already and it was enough to get started. What would swing it for me would be material covering why and how to scale an Ash-based system to multiple servers. If it had some aspects of building non-Liveview front-ends, so much the better.

webofbits

webofbits

Love the idea of a book covering a single project. The one technical book I loved the most, which I learned Ruby on Rails, was The Ruby on Rails Tutorial by Michael Hartl. It walk us from tests to implementation chapter by chapter.

ghannam80

ghannam80

I am with most of the replies in this thread plus it would be great to have maybe a chapter how to create an Ash extension.

Also if a certain chapter or appendix how we can use Ash with databases that does not have an Ash data layer like Oracle as we still have many legacy and enterprise apps with Oracle databases.

manhvu

manhvu

IMO, the LiveView + Ash + Postgres stack is a very good place to start. For me, I think adding more details on how to optimize and extend LiveView and Ash is what I really care about. I missed this kind of information in the standard docs and some of the books I’ve read.

— All posts loaded —

Where Next? Top

Trending in RFCs Top

Agostinho1965
Hey everyone — I’m putting together a practical, code-first book on building production-ready business applications with Phoenix LiveView...
New
tallakt
Hi I was working on an old idea of a “Soft PLC” written on top of Elixir. It was too much work but with the advent of better AI I though...
New

Other Trending Topics Top

GenericJam
Edit: 2026 May 15 - This post is archived. Mob is alive!! Main docs: mob v0.7.11 — Documentation A bit of explanation for the slightly c...
New
garrison
Hobbes is a low-level distributed database for the Elixir programming language. Hobbes provides a simple, safe, and scalable storage lay...
New
budgie
A little off-topic, but I feel like people here have a good head on their shoulders. I used to be quite good at making software. Was luc...
New
KristerV
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
mudasobwa
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
mcass19
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews