AW: [Zope-DB] Zip-Distances: MySQL or ZopeDB?

[Gregor Melhorn]

Dear Charlie, dear Andreas,

wow, response was fast, hail to the community! :-)

I thought of using Mysql 4 on Linux for the backend - I didn't go further
into this for now, since we're planning to develop the application with
performance in mind, and when near completion we'll look for an appropriate
hard- and software backend, buying in as necessary and doing extensive
performance testing on different configurations. 

We chose Zope, since in need of performance and scalability I didn't see
anything that would scale so well as Zope and at the same time be so easy to
develop with. Do you have any suggestions on the mysql backend, too?

I'll try exUserFolder, though 12 open bugs and a version number of 0.20.1
don't make me that confident. Anyway, it seems to work for others, too...
Any suggestions on where to get documentation on this one?

Thanks for your suggestions
Gregor


-----Ursprüngliche Nachricht-----
Von: charlie at egenix.com [mailto:charlie at egenix.com] 
Gesendet: Dienstag, 19. Oktober 2004 12:39
An: Gregor Melhorn
Cc: zope-db at zope.org
Betreff: Re: [Zope-DB] Zip-Distances: MySQL or ZopeDB?

Dear Gregor,

an RDBMS is ideal for the heavy lifting on this and Zope makes it easy to 
develop with. You can use the Product exUserFolder to keep your member data 
in the RDBMS. You'll need a lot of memory for both the database and Zope. 
What MySQL backend are you intending to use?

Charlie

On 2004-10-19 at 12:16:23 [+0200], Gregor Melhorn <g.melhorn at web.de> wrote:
> Hello everyone,
> 
>  
> 
> I am rather new to zope, maybe you could help me with the following
problem:
> 
>  
> 
> I'm planning to do a dating community site in zope, with about  50 000
> members and up to 10 000 members being logged in at the same time. Search
> function is only for members, so it needs to be authenticated. Searching
for
> other people is based on distance (search for all people in 50 km distance
> etc.), and I also have a database with geodata for all zip-codes.
> 
>  
> 
> So now there's the problem: The search function of the site will be used
> very often, and every different zip-code-query will of course generate
> different results. Also a new registered user will again generate
different
> results. Searching is subclassed in different distances ("up to 50 km",
"up
> to 100 km" and so on...).
> 
>  
> 
> Regarding performance, I thought of creating a large lookup-table in mysql
> with all distances of all zip's to all the other zips and building an
> according select query for the user-list. On the other hand - outsorcing
the
> user (and therefore authentication data) will slow down the site, since
> nearly everything on site needs to be authenticated, won't it?
> 
>  
> 
> Maybe there's some combined solution to this problem - any ideas? I'm
really
> rather new to Zope, help would be really appreciated.
> 
>  
> 
> Regards
> 
>  
> 
> Gregor Melhorn
-- 
Charlie Clark
eGenix.com

Professional Python Services directly from the Source
 >>> Python/Zope Consulting and Support ...        http://www.egenix.com/
 >>> mxODBC.Zope.Database.Adapter ...             http://zope.egenix.com/
 >>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/
________________________________________________________________________

::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::