|
You are here |
akoutmos.com | ||
| | | | |
serokell.io
|
|
| | | | | Phoenix is the main web framework in the Elixir ecosystem. Learn how it works and what's special about it. | |
| | | | |
eaj.no
|
|
| | | | | Don't go looking for the one. Unless the person you're looking for is stored in a PosgreSQL database. Then you actually have to search. | |
| | | | |
blog.nootch.net
|
|
| | | | | Posts in this series Part 0 Part 1 Part 2 Part 3 Part 4 Part 5 Part 6 Part 7 Onward In the previous articles, we went over installing the tools we'll need for our API project and a small introduction to Event Sourcing, DDD and CQRS and how our library of choice, Commanded, interprets them. We aim to develop a simple Banking API that allows for: | |
| | | | |
fullstackphoenix.com
|
|
| | | In this post, I want to show you how to leverage cache in Phoenix LiveView to avoid hitting the database twice when mounting a LiveView page. The reason is that the query might potentially be expensiv | ||