JKWA
Author of Advanced Functional Programming with Elixir
What it’s like to bring Ash into an existing project?
Yet another in my series on the Ash Framework.
Trending in Blog Posts
Hey folks,
I just published a post about Hologram’s funding and where the project goes next - the short version:
Curiosum as Main Spons...
New
Hi all,
In this article, I make the case for each test owning its setup.
Usually I forbid my AI agents to use the setup callbacks; I mu...
New
As I’ve leaned into AI code generation on LocalCents, the volume I ship has climbed, and my worry shifted from any single change to the l...
New
I wrote about an issue I had with a LiveView application, and how I solved the problem by debouncing updates server-side (within the Live...
New
I’ve published a new article in my Elixir learning series on dev.to exploring what happens when tagged tuples aren’t enough - the try, re...
New
This article demonstrates how to build a minimal stateful process using only Elixir’s core concurrency primitives: spawn/1, send/2, recei...
New
A recent ex_money v6 upgrade was blocked because Timex pins an old gettext. Rather than one big remove-and-rewrite PR, I used a shim: a m...
New
Other Trending Topics
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New
I just stumbled on a newly redesigned elixir-lang.org. :tada: It looks like @Software_Mansion did the work, and I think it is generally a...
New
@hugobarauna and I (Alex Koutmos) have been hard at work on writing a book on Nerves that takes you from simply blinking LEDs to building...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #performance










First 3 of 3 Posts
ghannam80
Thanks for the article and presentation of benefits of introducing Ash.
Do you see great value in bringing Ash to an existing system if the underlying database is not supported by existing data layers “Oracle in our case” ?
JKWA
Since your system is backed by Oracle, the question is whether Ash still brings enough to justify adoption. I think it does. The auth system, validation, the action pipeline, and the structure Ash brings to your domain more than pay for themselves. It is also low risk to try. Pick one slice of your domain and wire it up to your existing API. If it does not feel worth it, you can step back out easily.
If someone is starting a new Elixir project and considering Oracle for persistence, I would be cautious. You can build an Ash extension, but you will own all the quirks that come with Oracle’s closed system, including its types, pagination rules, DDL quirks, and JSON behavior. You will get no support from Oracle, and because most Elixir developers work with open-source projects, you are likely to find less community help.
ghannam80
Thank you for the thoughtful and balanced feedback — I really appreciate the clarity in how you framed both the strengths of Ash and the risks around Oracle.
Just to clarify our situation: we’re effectively locked into Oracle because many of our enterprise systems (and dependencies from other teams) are tightly coupled to it. So while we don’t prefer Oracle from a developer-experience perspective, we have to operate within that environment for now.