If 2 users in SF try to insert accounts at the same time(assume it) considering we didn't bulkified our code in helper classes.
Now we know, whenever users try to use such functionalities from SF UI it'll create separate transactions for them but our Apex triggers will consider both the transactions as single(and concurrently) and will operate the logic correct?
I mean what issues this Scenario can cause and what is happening behind the scenes?
If 2 users in SF try to insert accounts at the same time(assume it) considering we didn't bulkified our code in helper classes.
Each user have its own transaction, thus this will run two parallel transaction.
Apex triggers will consider both the transactions as single(and concurrently) and will operate the logic correct?
No, it will be two different transaction, both running the same trigger. One unaware of the other.
The only way (on the SFDC platform) two different users' "update events" will be considered as a single SFDC transaction is if
where Trigger T subscribes to Platform Event E
If the two publications occur close enough in time, then it is possible, though not guaranteed, that a single SFDC transaction that executes trigger T will bulk both events (E(0) and E(1).
Of course, to the end user, the platform events execute asynchronously to the original transaction(s) that published the event(s).
