Database choice

Database choice and considerations

BlissRADIUS Embedded uses relational database to store data. Supported are:

• SQLite3 (not available for all systems, see details at download page)
• MySQL
• Postgres

SQLite is embedded database and is included in BlissRADIUS Embedded binaries where available. MySQL and Postgres require that you have database server running as separate process on same or different computer.

There are few considerations you must make in advance.

MySQL (MariaDB), Postgres or SQLite?

MySQL (MariaDB) and Postgres are similar in both performance and maintenance requirements. Administration is more complex as they are dedicated server databases.

SQLite may not be first choice for heavy production usage (eg. 10.000+ concurrent online users) but will work correctly, albeit with higher CPU usage. Maintenance is extremely simple as it is embedded database that uses single file to store data.

New/empty or existing database?

Both options are possible. Choice depends on if you plan to use same database host is using.

In both cases BlissRADIUS Embedded uses schema in such a way not to collide with existing structures. All tables and indexes created and used have name prefixed with blissembed_ . This way you can use same database eg. your WHMCS or Blesta is using.

Host's database or separate database?

Storing data with your host's database is good choice if you want easier maintenance as all data is in one place and backups cover both systems. Downside is that if your host or database is down for any reason, this will affect BlissRADIUS Embedded too - something that can be avoided.

Storing data in separate database is excellent choice for robustness and reliability. BlissRADIUS Embedded caches service data, meaning it can work correctly even if your host or hosts database is down for extended periods of time (days or weeks). Two systems are completely separated which offers great flexibility when handling crisis situations.

So, which one should I chose?

If you are using WHMCS or Blesta and don't want extra maintenance and you feel lucky (nothing will break) or confident (you know how to fix it when it does) then use existing MySQL database WHMCS or Blesta is using already.

If you are more on careful side and want extremely reliable system that will keep on working even when host is down (be it WHMCS, Blesta or something else) then go for separate SQLite or Postgres or even MySQL, but take care that database is running on different computer from host's (this is rarely achieved in practice, as it is common approach to use single, dedicated computer as database server for more than one services).

In that case, for maximal reliability and simplicity SQLite is the best choice. For setups that won't work with more than 10.000 online users, BlissRADIUS Embedded running on separate computer and using SQLite as database will keep on going through worst situations.

If you plan on using BlissRADIUS Embedded in local mode then there is no host software. Chose database type by criteria described above.

2025-03-16

Referral program is active, existing users can win bonus license time if they bring new customers in.

2025-03-02

BlissRADIUS Embedded™ 1.16 is out with new features.

2024-09-27

BlissRADIUS Embedded™ 1.15 is out with postpaid license support.

2024-09-19

We are introducing changes to payment methods. See Home page for more details.

2023-07-06

BlissRADIUS Embedded™ 1.14 is out with new features.

2022-11-18

BlissRADIUS Embedded™ 1.13 is released with new fixes and features.

2021-12-31

BlissRADIUS Embedded™ 1.12 is out with new features.

2021-06-22

Volume discount for monthly BlissRADIUS™ licenses is available now.