bdubaut
Hi everyone, in an effort to understand GenServers and Registry, I put together a small URL shortener service, without a database. Each “link” is registered using Registry, with the shortcode as a key to find the process. I am aware that this probably would not be a suitable approach for a production system, but it was fun to mess around with GenServer and Registry.
https://github.com/bdubaut/shortex
I would love some feedback on it:
- what is good
- what is bad
- if my tests are relevant
This actually made me think about how your architecture changes when you bring in OTP patterns in your app design from the start, especially with persistence strategies. If you can store state inside a process, then how do you decide when to persist? What data to persist? I can definitely see a CQRS/ES type of architecture, with the event stores inside a DB, and having the read models in-memory as processes. Would this be a valid approach?
Thanks
Where Next?
Trending in Discussions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Producing high quality Elixir screencasts since 2017.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Bringing learning, work and compliance together since 1987.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
petecorey
Cool stuff!
My latest application uses an Event Sourcing/Memory Image approach, and I’ve had nothing but pleasant experiences with it.
In my experience, people’s instinctual response to Memory Images (keeping the application’s entire working state in memory) is vehement rejection, but in reality I’ve found it to be a really elegant solution to a lot of hard problems.
It opens up worlds of flexibility for managing read models (that can be reshaped, regenerated, and refactored on the fly), and makes conflict resolution fairly simple when compared to other solutions that rely on complicated consensus algorithms between distributed nodes.
One quick thing I noticed in your project is that there might be a race condition when generating new short codes for links. What would happen if two people simultaneously try to generate a new shortened link, and
generate_shortcodereturns the sameshortcodefor each? The first caller to reachLink.start_linkwould succeed, but the second call toLink.start_linkwould fail because the name is taken, right?Instead of doing your
Registry.lookupingenerate_shortcodeto detect used codes, you might want to listen for:already_startedfailures fromLink.start_linkinstead.That being said, the problem I described is very unlikely to happen in the real world. Just something to think about. Distributed systems are hard.
Good work!
bdubaut
Thanks a lot for the feedback