mmport80
I suspect many apps these days have enough memory available for many tasks.
The problem with applications is that they crash and lose memory, so you need some storage, but we have Mnesia etc.
After the recent talk about component and design etc. I started thinking about this.
Could you have a ‘Phoenix’ with an Elm / Redux like architecture and backup state every so often to disk (automagically).
Of course you could include DB reliant features, but by default state would be backed up in the background.
I suspect that would simplify things quite a bit (perhaps too much - but at least you could get up and running quickly).
Perhaps this already exist in other frameworks?
Where Next?
Trending in Discussions
Other Trending Topics
Latest Phoenix Threads
Chat & Discussions>Discussions
Latest on Elixir Forum
Sponsor Spotlight
Producing high quality Elixir screencasts since 2017.
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
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex
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.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Bringing learning, work and compliance together since 1987.
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!"
First 10 of 39 Posts
AstonJ
You might like this post from Joe Armstrong:
And the discussion that followed:
mmport80
Yeh his words have stuck with me - I remember him saying this years ago…
Databases make things tough, but we kind of accept them…
kelvinst
Well, Phoenix itself is totally dbless, just remove Ecto and
.
The automagical state backup would be a nice thing to have though!! But I would prefer it at least a little bit explicit and not embedded to a framework, a new lib for that would be really interesting.
hubertlepicki
What you are, most likely, looking for is something like Microsoft Orleans in Elixir:
There is none, I think in Elixir, but here is something in Erlang that we can possibly use: GitHub - erleans/erleans: Erlang Orleans · GitHub
I didn’t try it, and I suspect it might be in early stage. But such “framework” would allow us to avoid many design issues such as persistence etc. This should be rock-solid base to build in, that will allow us to focus on building the application and not do infrastructure tasks like saving/restoring state, which is also error-prone.
michalmuskala
In a way that’s what riak_core and now lasp are - your application is your database.
mmport80
Who needs state at all? Much of Phoenix is stateless : ) and that’s something I really like..
kelvinst
Yeah! I share your thoughts. Unfortunately, a lot of the products people value nowadays are a stateful solution to problems that could be solved by stateless ones. I keep forcing myself to find stateless solutions to the problems I have, but unfortunately I mostly fail. Sometimes I even think state is really an inevitable evil for almost every solution.
dimitarvp
IMO a lot of the RDBMS inertia also comes from the added value that SQL can bring – namely reports. Business people, legal teams and finance departments just LOVE reports.
OvermindDL1
GraphQL gives similar flexibility, without needing a database. ^.^
dimitarvp
Yeah but how will you do the various aggregations, means etc. that a professional SQL dev can do? GraphQL is just an interface; something below it has to actually create the report.