Hi Helen, Many thanks for clarifying..
Geoff --- In firebird-support@yahoogroups.com, Helen Borrie <helebor@...> wrote: > > At 11:23 p.m. 16/06/2013, you wrote: > >Hi, > > > >I'm considering using Firebird for my database applications. > > > >My applications are not large and certainly cater for (usually!) around 10 > >users on a LAN. > > > >I use a single database and it is usually accessed by users their own > >individual instances of my application. > > > >Can I use Firebird Embedded for this, or should I use the full client server > >version? If the full client/server, which version Classic, SuperClassic or > >Superserver? > > Well, the beautiful thing is, you don't have to decide that until you have a > real environment to deploy to. These are not "different versions" of > Firebird but different execution models of the same database engine, that > allow you to deploy the same software to sites varying from a single user in > an attic to thousands of users in an enterprise in the way that best suits > your data volume, hardware resources and network availability. > > With "10 users on a LAN" it doesn't make any sense to consider deploying 10 > stand-alone installations - unless, for some absurd reason, every employee > has to maintain his or her own database. That sounds like a management > nightmare. > > Firebird is designed to make one database accessible to everyone on a > network, as clients. Embedded is good when you have one and only one client: > the "attic" user or as the back-end to a managed client layer such as a > web-application. For two or more clients, you're looking at a client/server > deployment. > > > Helen Borrie, Support Consultant, IBPhoenix (Pacific) > Author of "The Firebird Book" and "The Firebird Book Second Edition" > http://www.firebird-books.net > __________________________________________________________________ >
