Umbraco db for 500K+ members and use with mobile apps?
Hi im new to Umbraco and am really excited to learn more and start using it for my new business system (it is providing a service to members. they can create/view their account on both the umbraco website and the mobile apps.
I would like to know can the umbraco db handle 500K+ members registering with my business sufficiently? what are the member db limits? can new members be added into the umbraco db via mobile apps?
is it better or can it be done to use an external db system for members of this size and also store all their account details in it?
im working out what is the best way to approach the design for my system.
You may get some issues in the Umbraco backend members section due to sheer number of members so the tree could slow down but front end wise create / view should be fine because you are dealing with one member. On front end when working with member api make sure you are not newing up member object each time you use it just do it the once. I worked on site not too long ago where on one page the member was being created each time it was required rather than using some kind of singleton pattern.
To add new members via mobile apps you can create web api and this end point can be hit using mobile. You can also use your own membership provider and swap out the existing umbraco one if you really wanted to.
Umbraco db for 500K+ members and use with mobile apps?
Hi im new to Umbraco and am really excited to learn more and start using it for my new business system (it is providing a service to members. they can create/view their account on both the umbraco website and the mobile apps.
I would like to know can the umbraco db handle 500K+ members registering with my business sufficiently? what are the member db limits? can new members be added into the umbraco db via mobile apps?
is it better or can it be done to use an external db system for members of this size and also store all their account details in it?
im working out what is the best way to approach the design for my system.
Thank you for your help with this
Romes,
You may get some issues in the Umbraco backend members section due to sheer number of members so the tree could slow down but front end wise create / view should be fine because you are dealing with one member. On front end when working with member api make sure you are not newing up member object each time you use it just do it the once. I worked on site not too long ago where on one page the member was being created each time it was required rather than using some kind of singleton pattern.
To add new members via mobile apps you can create web api and this end point can be hit using mobile. You can also use your own membership provider and swap out the existing umbraco one if you really wanted to.
Regards
Ismail
is working on a reply...