oliveiragahenrique
I’m designing a pure functional data structure to manage banking accounts, a simplified version of it would be:
defmodule Account do
defstruct balance: 0, limit: -500
def new() do
%Account{}
end
def deposit(%Account{} = account, amount) do
new_account =
%Account{account | balance: account.balance + amount}
{:ok, new_account}
end
def withdraw(%Account{} = account, amount) do
new_balance = account.balance - amount
if new_balance >= account.limit do
new_account =
%Account{account | balance: new_balance}
{:ok, new_account}
else
{:denied, "No funds", account}
end
end
end
My question is about when should I use the response pattern of {:ok, data} for sucess and {:error, reason, unchanged_data} for failures.
This sounds like the way to go here on this problem, but if I go with this pattern I lose the feature of do something like this:
account =
Account.new()
|> Account.deposit(%{amount: 5000})
|> Account.deposit(%{amount: 3000})
|> Account.withdraw(%{amount: 1000})
I really like to design modules that could use the pipe operator like this, but how to do this when the module functions can fail?
If I just remove the :ok from the sucess response would solve the problem, but is this a good pattern?
What you guys think? How can I keep the pipe feature together with a good response check validation?
Trending in Questions
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
Hey guys,
I’ve got a huge CSV ( around 10 GB ) that needs to be processed hourly
Do you guys have any suggestions what is the best prac...
New
Hello!
Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app.
I creat...
New
I have what I’ve heard referred to as a “lookup table” in my database. This is a way of assigning codes to common values. One common lo...
New
Hello,
I’m developing a online persistent chat system (what’s app) like using elixir/dynamodb/aws for a mobile app(flutter).
The diffic...
New
What approach to take when sending live updates to “random” users Hi! I have a question, I have a little chat app, and when I create a DM...
New
I think I’ve found a small improvement I could contribute to <%= web_namespace %>.CoreComponents (installer/templates/phx_web/compo...
New
Other Trending Topics
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
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
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
There are three potential reasons for members of this forum to have a look at https://vutuv.de
You are tired or annoyed of LinkedIn.
Yo...
New
ICal is a library for interacting with iCalendar data. It parses iCalendars into typed Elixir structs via ICal.from_ics, and can prepare ...
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
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #ai
- #phoenix_html
- #elixirconf-us
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming











Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
kokolegorille
If the pipeline can break, I would use with…
bottlenecked
@rrrene has written a series of articles on data flow patterns that perhaps could help. You may want to read up on the Token-based approach for your specific use case.
oliveiragahenrique
Great tip! Gonna check it out later for sure!