Subject | Re: [firebird-support] Using Firebird in a big web application |
---|---|
Author | Kjell Rilbe |
Post date | 2011-05-31T09:21Z |
Den 2011-05-31 09:55 skrev Albert Parés såhär:
knowledge about security in general and FB security in specific may have
something to say about it.
As for performance, I would assume it will work fine, at least if you
disable forced writes. This requires you to take steps to minimize risk
of data loss, because without forced writes, the DB may become corrupt
when the server accidentally stops, e.g. power failures or other system
crashes.
For our purposes it is sufficient that our hosting provider has
substantial spare power to protect against power loss, our server has
RAID 1 = mirrored disks to protect against single disk failures, and
nightly backups. At the minimal risk that both disks should crash or the
system would crash in any other way, it is acceptable to us to lose up
to one day's work.
If you require more protection than that, you can use replication,
loggin, disk controller battery backup (will protect against failures in
the server's power supply unit, which a regular UPS won't). You can also
configure the server to limit the amount of data that is write cached,
and for how long.
I assume you're already familiar with RAm requirements, page buffer and
page size setting, and so forth.
Kjell
--
--------------------------------------
Kjell Rilbe
DataDIA AB
E-post: kjell@...
Telefon: 08-761 06 55
Mobil: 0733-44 24 64
> In few weeks we starting developing a management web application with phpRegarding security I see no obvious problem, but others with more
> (Symphony) and us intention are use Firebird 2.5 for a database engine. We
> expect to arrive about 7000 simultaneous users with readers and writers.
> Firebird is a good choice? Is secure?
knowledge about security in general and FB security in specific may have
something to say about it.
As for performance, I would assume it will work fine, at least if you
disable forced writes. This requires you to take steps to minimize risk
of data loss, because without forced writes, the DB may become corrupt
when the server accidentally stops, e.g. power failures or other system
crashes.
For our purposes it is sufficient that our hosting provider has
substantial spare power to protect against power loss, our server has
RAID 1 = mirrored disks to protect against single disk failures, and
nightly backups. At the minimal risk that both disks should crash or the
system would crash in any other way, it is acceptable to us to lose up
to one day's work.
If you require more protection than that, you can use replication,
loggin, disk controller battery backup (will protect against failures in
the server's power supply unit, which a regular UPS won't). You can also
configure the server to limit the amount of data that is write cached,
and for how long.
I assume you're already familiar with RAm requirements, page buffer and
page size setting, and so forth.
Kjell
--
--------------------------------------
Kjell Rilbe
DataDIA AB
E-post: kjell@...
Telefon: 08-761 06 55
Mobil: 0733-44 24 64