It is exciting to see the release of MonetDB/e - congratulations. I have two questions to offer. First, has anyone begun work on an R package? As a follow-up question if not, which of MonetDB.R, MonetDBLite or DuckDB packages for R would be a better starting point? Second, could someone kindly explain the potential advantages and disadvantages of using either MonetDB/e or DuckDB, please? They both seem to come from CWI, so this is a little confusing. Sincerely, Mark. När du skickar e-post till Karolinska Institutet (KI) innebär detta att KI kommer att behandla dina personuppgifter. Här finns information om hur KI behandlar personuppgifterhttps://ki.se/medarbetare/integritetsskyddspolicy. Sending email to Karolinska Institutet (KI) will result in KI processing your personal data. You can read more about KI’s processing of personal data herehttps://ki.se/en/staff/data-protection-policy.
Hi Mark, On 16/07/2020 08:39, Mark Clements wrote:
It is exciting to see the release of MonetDB/e - congratulations.
I have two questions to offer. First, has anyone begun work on an R package? As a follow-up question if not, which of MonetDB.R, MonetDBLite or DuckDB packages for R would be a better starting point?
This pre-release does not yet contain an R-binding or R-packages. It is on our list and worked on. DuckDB is more mature at this point in time.
Second, could someone kindly explain the potential advantages and disadvantages of using either MonetDB/e or DuckDB, please? They both seem to come from CWI, so this is a little confusing.
Yes, MonetDBlite was a fork of MonetDB at CWI for embedded use of the code base of MonetDB. primarilly R. It was non-maintainable as a long term supported product and terminated. Instead, the authors of the fork decided to start from scratch again, which led to DuckDB a research prototype used in database research at CWI and has a takeup in the R-community. MonetDB/e is the continual evolution of the MonetDB code base to also be useable as an embedded database system, addressing a need in that market with all the server options. MonetDB itself is used wordwide as back-end for enterprise-grade applications. At this stage, for an end-user DuckDB does not support all the data types of SQL, JSON, lacks parallelism, SQL goodies like triggers/persistent store modules,.... and MonetDB/e does not yet support bulk-loading parquet files. So, the choice depends on your feature and performance needs. The examples show that most of the code can easily be switched as long as it based on the Python DB-API 2.0 interface. The way MonetDB/e is set up simplifies the maintenance of the server code. Feature requests are merged with the main stream of MonetDB features and handled as time permits, or users willing to support its speedup by donation of time/funds/turnkey projects. regards, Martin
Sincerely, Mark.
/När du skickar e-post till Karolinska Institutet (KI) innebär detta att KI kommer att behandla dina personuppgifter. /Här finns information om hur KI behandlar personuppgifter https://ki.se/medarbetare/integritetsskyddspolicy.
/Sending email to Karolinska Institutet (KI) will result in KI processing your personal data./ You can read more about KI’s processing of personal data here https://ki.se/en/staff/data-protection-policy.
_______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list
DuckDB is the current research prototype from CWI Database Architectures
group. You should only use it if you are not afraid of debugging.
MonetDB is still in use for research, but also on quite a few industry
deployments. It is primarily developed in MonetDB Solutions, a spinoff
company from CWI.
Both systems are quite mature, but the focus is on research for DuckDB and
innovative applications for MonetDB.
A non-official answer, hope it helps,
Arjen
_____
Please excuse brevity - sent from a mobile.
Op do 16 jul. 2020 08:44 schreef Mark Clements
It is exciting to see the release of MonetDB/e - congratulations.
I have two questions to offer. First, has anyone begun work on an R package? As a follow-up question if not, which of MonetDB.R, MonetDBLite or DuckDB packages for R would be a better starting point?
Second, could someone kindly explain the potential advantages and disadvantages of using either MonetDB/e or DuckDB, please? They both seem to come from CWI, so this is a little confusing.
Sincerely, Mark.
*När du skickar e-post till Karolinska Institutet (KI) innebär detta att KI kommer att behandla dina personuppgifter. *Här finns information om hur KI behandlar personuppgifter https://ki.se/medarbetare/integritetsskyddspolicy.
*Sending email to Karolinska Institutet (KI) will result in KI processing your personal data.* You can read more about KI’s processing of personal data here https://ki.se/en/staff/data-protection-policy. _______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list
participants (3)
-
Arjen P. de Vries -
Mark Clements -
Martin Kersten