I need some inputs for design suggesstions for our notes client application.
Senario : We have a notes client application where it contains 300 fields in a single form. Once in a year its a mandatory activity for all users to submit in application. The database will be open for around one month, but users will normally rush on to the database only when it on edge to close say around 3-4 days. Which will lead the database responce. and some times server will hang.
I feel that 300 fields in a single form should not cause for the database response. I feel its only a no of users which causes.
I have suggested to go for notes based web application instead of notes clint based application. But due to some mandatory IT infrastructure business strongly disagreed to go for web application.
So how do I handle this senario? Did you come accross with any such kind of circumstances?
Please provide your inputs on designing such kind of applications. Please let me know if you require any more details.
Subject: RE: Database Design Help for 30000+ users
Hi JYR,
We can not release Departmentwise, as people have spead accross from various depts to different locations. We can ask users to use only their location servers.
Considering Readers field I can use show single category in a embedded view.
How do I handle the more no of concurrent hits at a single time?
Subject: RE: Database Design Help for 30000+ users
Sanjay,
Typically, Notes Clients will have less of an impact than Web Browsers in terms of piling thousands on concurrently. That said, this type of application might be well suited to a web app where users log in and all they do is fill out a form (or find their document and edit it) and submit it.
In other words, there is no need for them to access any views. Views, especially with reader names, are typically the choking points when you have a rush of many concurrent users.
So, I’d have their document come up as quickly as possible, that is with as little user intervention as possible, and, if they need to choose from among multiple docs, definitely user embedded view with SingleCategory.
At that point, if you still feel pain, then you need to look at the form, dblookups, query/post code, etc.