I've been asked to spec out a site that will initially have approx 15k members.
These will be people who will be able to login to the frontend, edit details, fill in forms, upload images etc.
They will not have umbraco backend access and will work as normal members, albeit with a vastly expanded set of properties.
I've been reading on the forums and it seems the EXAMINE system for umbraco members doesn't work well at these numbers. As I'm expecting the number of members to expand greatly over time, should I be storing their details in a new table and writing my own login/validation stuff, or have other folks found that umbraco can handle this many using the Member class?
edit - I should point out that I was thinking of just using the Member class for the login bits, and creating a separate class/table to handle the rest of the functionality, using the Member ID as a key. I wasn't considering pouring all the functionality into the existing Member class.
How many members can umbraco 7 cope with?
Hi All
I've been asked to spec out a site that will initially have approx 15k members.
These will be people who will be able to login to the frontend, edit details, fill in forms, upload images etc.
They will not have umbraco backend access and will work as normal members, albeit with a vastly expanded set of properties.
I've been reading on the forums and it seems the EXAMINE system for umbraco members doesn't work well at these numbers. As I'm expecting the number of members to expand greatly over time, should I be storing their details in a new table and writing my own login/validation stuff, or have other folks found that umbraco can handle this many using the Member class?
edit - I should point out that I was thinking of just using the Member class for the login bits, and creating a separate class/table to handle the rest of the functionality, using the Member ID as a key. I wasn't considering pouring all the functionality into the existing Member class.
All the best
Shaun
is working on a reply...