Menu
Real-time computing has nothing to do with performance, but rather the guarantee that an event can be completed in a set amount of time. Real-time requirements have implications throughout the architecture from CPU scheduling algorithms to the operating system all the way to the application being built.
From this Miller concluded that a consistent 2-second response would be ideal. Years later this same value of 2 seconds has been used as a performance target for web-based applications. Today's real-time applications, however, require near-instantaneous responsiveness.
The description for an operating system that responds to an external event within a short and predictable time frame. Unlike a batch or time-sharing operating system, a real-time operating system provides services or control to independent ongoing physical processes.
Real-time payments (RTP) are payments that are initiated and settled nearly instantaneously.
I am having trouble deciding on whether to classify my application as 'real time' or 'near real time', or perhaps even something else.
The software receives data immediately as it is generated from the source, then based on certain rules, raises an alert when certain conditions are met. It takes the approach of checking the last 30 seconds of data every 30 seconds to see whether the criteria for a rule has been met.
Is that real time? What are the thresholds for the definitions of real time vs. near real-time?
EDIT
I think this is a duplicate of Define realtime on the web for business.
Please decide if the above thread is insufficient to answer your question.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With