. Advertisement .
. Advertisement .
What is the difference between a sequential program and an event-driven program?? I am learning about it. Can someone share with me your knowledge and experience?
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In my opinion, sequential program language is designed to use as scripts. Therefore, they provide an interactive environment to the programmers. Event-driven programming language provides both a rich user experience along with an efficient system for event programming. The main difference between a sequential programming and event-driven program is event-driven programs respond to user requests in the form of text, audio and video, while sequential programs do not.
It is what I have understood:
Software that responds to user requests/demands is a good candidate for event driven design. This is the norm for most GUI-based and online-based software. There is no predetermined order of operations. The user can do whatever they want (within the limits of the app).
Batch processing is where sequenceential is most common. Software that requires little to no user input. The order of operations is predetermined.
It’s not clear that there is a distinct line, as GUI-based tools can include long-running batch processes.
Two different methods to support two different needs. An event-driven approach is best for problems that are driven by events. You will want to use a “sequential” approach if you are unable to control what is happening in the world.
These two things will often be combined. The startup and shutdown of a program, as well as a main processing loop (say, a filter process in an image app), will all be largely sequential. However, its UI layer, component interactions, and event-driven UI layers will be largely sequential.