4 ms·
I'm confused, the situation clearly called for a relational database. Almost any RDBMS would have been better than any "schemaless" db in this case. Was it just
by jorblumesea 10y ago
I'm confused, the situation clearly called for a relational database. Almost any RDBMS would have been better than any "schemaless" db in this case. Was it just to get the reactive architecture features? I'm confused why you would architect an application from the database up.
- StreamBright 10y agoActually I could do it with SQL, key-value store, and even with document stores, not to mention Erlang's Mnesia (whichever category it falls into). I think without understanding the complete picture, write patterns, read patterns, number of open connections etc. it is hard to say it is definitely SQL.
- williamstein 10y agoNothing was clear to me when I started writing the application. However, after years of running it in production, things did become much clearer, and indeed, a relational database is ideal.