Re: New IEEE Language Popularity Ratings

[Paul Rubin <no.email@nospam.invalid>]

"Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> writes:
> Client is a small board that has issues with load and multiple
> connections. 

If it has a TCP stack (and hopefully a TLS stack these days), it's not
THAT small.  It can deal with pushing something every few minutes.

> but there is no guaranty that the server pulls data or ready to be
> pushed with data in time. That is how it is similar to real-time.

There might be no server connection at all (forgot to pay ISP bill).
Either the client has to store data for later retry, or has to drop data
that can't be uploaded in a reasonable amount of time.  Neither of those
is anything like realtime in the traditional sense of something like
motor control.

> It is a big deal because clients are slow, that inflicts latencies
> accumulating on the server side. Then if you start 30k threads your
> server will freeze. Then it is not really scalable because there are
> usually databases and web portal behind.

An IOT thing would usually use a simple service that doesnt send whole
bloated web pages, and with 30k connections you wouldn't use an OS
thread for each one.  Async frameworks like node.js can handle that load
easily, or lightweight processes like in Erlang can also do it.  See the
famous "C10k Problem" article from 1999 and realize how much has
happened in hardware and software since then.  Scripting languages on
today's hardware are much faster than C was on 1999 hardware.  The db
would be something like redis which can easily handle 1000s of updates
per second.  Many giant web sites are written in scripting languages:
Wikipedia (PHP), Youtube (Python), Paypal (node.js), Facebook (a
compiled version of PHP), Yelp (Python), Reddit (Python), Github (Ruby),
etc.  A usual IOT server is far more lightweight.