Subject | Embedded server |
---|---|
Author | avner_liat |
Post date | 2006-03-13T10:49:06Z |
Hi,
I'm new to this database and trying to decide what will be the best
usage of the database in my case.
I have an exisiting client server architecture and I want to use the
firebird in the server side only.
I support in my server multiple clients which can update the database
concurrently by sending application specific commands.
This is why I want to open concurrent multiple database "transactions"
and do for each client its work in a dedicated transaction.
Since the only process which access the database is the server I was
thinking of using the embedded option.
My questions are:
1. Is using the embedded server option will give better performance
(because no networking and round loops are involved)?
2. Will hosting the database in my process will require less resources
than running the SuperServer?
Are there any other issues I should consider?
Thanks in advance,
Avner
I'm new to this database and trying to decide what will be the best
usage of the database in my case.
I have an exisiting client server architecture and I want to use the
firebird in the server side only.
I support in my server multiple clients which can update the database
concurrently by sending application specific commands.
This is why I want to open concurrent multiple database "transactions"
and do for each client its work in a dedicated transaction.
Since the only process which access the database is the server I was
thinking of using the embedded option.
My questions are:
1. Is using the embedded server option will give better performance
(because no networking and round loops are involved)?
2. Will hosting the database in my process will require less resources
than running the SuperServer?
Are there any other issues I should consider?
Thanks in advance,
Avner