This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/nextepc@lists.osmocom.org/.
Romeu Medeiros medeiros at medeiros.eng.brHello Harald, the main reason to use another database is just the preference, I use PostgreSQL for more than 10 years and the node/mongo has a different approach. I will try to begin this week. Thanks Romeu Medeiros On Sat, Sep 7, 2019 at 7:48 AM Harald Welte <laforge at gnumonks.org> wrote: > > hi Romeu, > > On Fri, Sep 06, 2019 at 10:39:54PM -0300, Romeu Medeiros wrote: > > Let me ask something, only the HSS need the database connection? > > The PCRF also uses mongodb, which I had to find out "the hard way" when writing > my osmo_dia2gsup translator to use osmo-hlr with nextepc. > > May I ask for your motivation to use a different database? I'm personally > also not convinced of the mongodb + nodejs approach of nextepc-hssd. No > disrespect to Sukchan here, it's mainly a question of different taste / > preference. > > Given the excellent built-in Diameter support in Erlang/OTP, if I was to > implement a "real" HSS for larger/realistic public networks, I would probably > recommend to do it in Erlang, using mnesia as database backend. > > For smaller, more embedded "network in a box" systems, something more > self-contained like a C program with sqlite3 seems like a good idea. > This is what we did in osmo-hlr. > > Regards, > Harald > -- > - Harald Welte <laforge at gnumonks.org> http://laforge.gnumonks.org/ > ============================================================================ > "Privacy in residential applications is a desirable marketing option." > (ETSI EN 300 175-7 Ch. A6)