[SerCe]

I believe there is no contradiction with the definition from the linked article?

> A system is said to be real-time if the total correctness of an operation depends not only upon its logical correctness, but also upon the time in which it is performed. Real-time systems, as well as their deadlines, are classified by the consequence of missing a deadline:

> Hard – missing a deadline is a total system failure.

> Firm – infrequent deadline misses are tolerable, but may degrade the system's quality of service. The usefulness of a result is zero after its deadline.

> Soft – the usefulness of a result degrades after its deadline, thereby degrading the system's quality of service.

From what I can tell, https://pocketbase.io/ attempts to be a soft-realtime system.

[ffsm8]

Really? I couldn't really see anything wrt degraded performance from my casual glance.

To me, It looks like there are just best effort events with literally no constraints or handling for delays etc

And again, I didn't see how you'd even implement such without being on both sides of the networked connection

I guess I just have to accept that the term has lost it's meaning at this point and can be used for whatever whoever wants to use it for

[trailbase]

> I guess I just have to accept that the term has lost it's meaning at this point and can be used for whatever whoever wants to use it for

It's maybe more like you point out: realtime in the OS context vs realtime in an event processing context. The latter is certainly not defined as strictly and often just means push-based. It has been a popular moniker, e.g. in kafka-land, for a while. I'm not sure it intrinsically takes away from the OS context - it doesn't need to be a deep dish pizza situation.