Work out Markdown\20.Introduction.md

it-p-lodz-pl / OOI.Gateway2Azure.Article

Object-Oriented Internet - reactive visualization of asynchronous data using AZURE services article

https://it-p-lodz-pl.github.io/OOI.Gateway2Azure.Article/README.html

GNU General Public License v3.0

0 stars 0 forks source link

Work out Markdown\20.Introduction.md #26

Closed mpostol closed 3 years ago

mpostol commented 3 years ago

[x] Subject - A basic matter of thought, discussion, investigation, development, etc. Describe the problem and the motivation for undertaking the effort to solve the problem.
[x] Goal What we are going to achieve - the result or achievement toward which effort is directed.
[x] Scope - What we must do to prove the goal has been achieved. Extent or range of development, view, outlook, application, operation, effectiveness, etc.
[x] PS Review
[x] convert to latex
[x] add bibligraphy
[x] Related work (if needed - Any information about available reusable deliverables related to this work.
[x] integrate with other sections.
[x] final latex text formating
[x] fnal review

mpostol commented 3 years ago

I will appreciate reviewing the text. The editable version is in .md, printable version was exported in .pdf.

Drutol commented 3 years ago

Hmm, we are talking about "real-time" aspect of M2M communication paradigm. Not sure if voip example is the best one, the transport is usually UDP in which we me lose data. It does not particularly matter in media streams but with process data depending on the volume it may matter (I guess), which in turn may make the reader more wary. It's minor issue but maybe we can find some other alternative... the prerequisite question here is:

What degree of real-time are we aiming for?

Cloud computing is bound to create latencies thus real-time turns intolow-latency at best given real-time systems perspective. Noting this tradeoff could help, because at the end of the introduction the aspect of real-time feels forgotten.

mpostol commented 3 years ago

From google we can learn:

A real-time system is a time-bound system which has well-defined, fixed time constraints. Processing must be done within the defined constraints or the system will fail. They either are event-driven or time-sharing.

If processing the voice we don't meet the defined constraints the sound will be disturbed. It is real-time. It doesn't matter what the delay is.

Drutol commented 3 years ago

I see. Defining these constraints in next sections would be a good idea then.