DB, no DB. Uncle Bob has much to say about that:
And:
gwww
smedegaard
@gwww Great articles!
Like really liked the “6 Commandments of Architecture”
-
Woe is the architect who prematurely decides on a database, and then finds that flat files would have been sufficient.
-
Woe is the architect who prematurely decides upon a web-server, only to find that all the team really needed was a simple socket interface. -
Woe is the team whose architects prematurely impose a framework upon them, only to find that the framework provides powers they don’t need and adds constraints they can’t live with. -
Blessed is the team whose architects have provided the means by which all these decisions can be deferred until there is enough information to make them. -
Blessed is the team whose architects have so isolated them from slow and resource hungry IO devices and frameworks that they can create fast and lightweight test environments. -
Blessed is the team whose architects care about what really matters, and defer those things that don’t.
5
smedegaard
@easco, have you by any chance read Functional Web Development with Elixir, OTP, and Phoenix by @lance?
As far as I can see the approach in the book does exactly what @sasajuric “warns about” in To spawn, or not to spawn?
Would anyone like to comment on that?
I’m now at the point where I’d like to implement my homebrewing app as a Elixir-only app first and only when that is done I’ll decide on persistance and web interface.
But I’m still having difficulties modeling the buisness logic and I feel like I’m getting conflicting advice 
0
LostKobrakai
This is addressed here and in the few following posts: Functional Web Development with Elixir, OTP, and Phoenix (Pragprog) - #60 by mjadczak
2
smedegaard
@LostKobrakai, thanks
@redrapids
Lance and I are working with some great reviewers to make sure we address this feedback. We’re going to shift the approach for the two chapters in question, the chapter on modeling and the chapter on wrapping the result in OTP.
As a popular book in the community, we want to make sure that the guidance we give is sound.
This sounds fantastic! Now We just have to wait for the changes 
1
easco
Yes I did read it and. I noticed that. As others pointed out there was a thread of discussion on the topic.
I’m a homebrewer myself perhaps if you posted some details of your model folks could help you place bits and pieces.
0
andre1sk
I think it’s good to have some perspective outside of some fairly exotic scenarios you really do want a database. You are very unlikely to be able to have a performant alternative at reasonable cost outside of fairly niche scenarios.
0
smedegaard
@andre1sk
I think it’s good to have some perspective outside of some fairly exotic scenarios you really do want a database. You are very unlikely to be able to have a performant alternative at reasonable cost outside of fairly niche scenarios.
Yeah, that’s what I was thinking. And really still think. But I would love to be proven wrong.
And I think that the point of “you don’t need a database. Databases are not your friends”-vibe is more a “Don’t design a database and put an application on top of it. Design your app and use whatever presistance makes sense for the app. If any”
– as far as I’ve gathered anyways
1