Are there limits on the number of content element CRUD transactions Umbraco can handle? I see a lot of (older) information on the number of page nodes it can serve, but nothing on transaction capacity.
Background: I'm setting up a registration system in Umbraco 8. Events, etc. will be elements based on document types as in a standard deployment. Members will complete a registration form which is posted back to Umbraco via a surface controller. I plan to use SQL Server to store content data.
What is best practice for handling this kind of situation and ensuring a performant system? Is it OK to save the registrations as content elements (e.g. a Registration document type) so they are easy to configure, list, etc.? Or should they be persisted in a custom table?
V8 Transaction Scalability
Are there limits on the number of content element CRUD transactions Umbraco can handle? I see a lot of (older) information on the number of page nodes it can serve, but nothing on transaction capacity.
Background: I'm setting up a registration system in Umbraco 8. Events, etc. will be elements based on document types as in a standard deployment. Members will complete a registration form which is posted back to Umbraco via a surface controller. I plan to use SQL Server to store content data.
What is best practice for handling this kind of situation and ensuring a performant system? Is it OK to save the registrations as content elements (e.g. a Registration document type) so they are easy to configure, list, etc.? Or should they be persisted in a custom table?
thx
is working on a reply...