CharlesIrvine
I have a open source GenServer based library application. It currently persists data in a CubDB database. I would like to migrate from CubDB to Postgres. I have used Ecto/Postgres before with a Phoenix web app, but I’m unsure of how things will work if I’m adding Ecto/Postgres to a library app.
It would be great if I could get some general pointers on the steps that I will need to take. What will users of my library need to do to support both my libraries persistence and their own persistence needs. Will there be two databases, one for my library and a separate one for the using application?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Deploy Phoenix to your own VPS with PaaS ease: push-to-deploy, zero downtime, auto SSL, managed Postgres. 14-day free trial at potions.io
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
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex
Our Sponsors
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Producing high quality Elixir screencasts since 2017.
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 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
garrison
I think the canonical example for this is the way Oban handles migrations.
Personally I have a library which just generates migrations directly into my application (codegen), but that’s because it’s intended for my own use only
CharlesIrvine
Thanks for your help. The Oban approach makes sense. Oban makes use of the client application’s database. Now, my library app will take the same approach.
I had been thinking that my library would have it’s own database, which did seem troublesome. I do wonder, though, if there are any circumstances that might warrant this approach.
As an added bonus, I see that I have some use cases that are a perfect fit for Oban.
garrison
If you have no need for atomic transactions across your library and the user’s database, it could be useful for performance reasons to scale out to two physical database servers for a small subset of users that need to handle such load.
I think it would be fine in that case to make it the user’s problem, though - they can simply run the migrations on a different Ecto repo