And a month that I'm developing a platform that must support up to 1,000 users performing database transactions in the same second ( even on the same tables may interact 100 users at a time within one second ) .

But the system supports this?

Because the evidence we are making locally with two users connected we find only problems related to database transaction , which generate committ error.

the project is

http://95.226.31.180/payplatform.html

username : test
password : test

> http://95.226.31.180/payplatform.html
>
> username : test
> password : test

And now?

Do you expect us to click every button and guess what could be wrong?

If you need help, you have to be much more specific.

Uli

no I would like to know if anyone has developed a platform with features that I listed and managed without problems or had to use some tricks and if such

Probably from what I understand are the transactions that create problems . So I wonder , but to interact with the database in writing is required to use transactions ?




Uli Becker wrote:

> http://95.226.31.180/payplatform.html
>
> username : test
> password : test

And now?

Do you expect us to click every button and guess what could be wrong?

If you need help, you have to be much more specific.

Uli

On 10/7/2015 1:08 AM, Pasquale wrote:
> no I would like to know if anyone has developed a platform with features that I listed and managed without problems or had to use some tricks and if such
> Probably from what I understand are the transactions that create problems . So I wonder , but to interact with the database in writing is required to use transactions ?

No - nothing with that number of users/activity and response time needs.

If you need to handle that many users in that kind of time (millisecond
response) then you really need to architect the back-end first.

I think you really need to be clear what you mean by transactions and
problems - there can be back-end database transactions and of course
there are EWB dataset transactions. However the 2 are completely
different things.

(I'm simplifying significantly here but ) EWB transaction is essentially
a change detection system for EWB to know when to send the dataset
changes to back-end server.

Hence there is no interaction with the back until you call the final
commit and all the code runs inside the client browser - so it will
scale just fine to the numbers you need.

Once the change is sent back to the server is where everything has to
happen on same (or few) back-end servers (and related databases etc) so
you need to make sure its as optimized as possible for the speeds you're
looking for and that there is no locking of any kind etc.

Without knowing more about what you're trying to accomplish it's hard to
be more specific.

Raul

Pasquale,

<< Because the evidence we are making locally with two users connected we find only problems related to database transaction , which generate committ error. >>

Please don't keep re-posting the same issue.  I'm still looking into your commit issue, and should have an answer for you soon.

Tim Young
Elevate Software
www.elevatesoft.com