PDA

View Full Version : IoT = Internet of Things --- Antwerpen wordt een hyperintelligente ‘City of Things’


Nr.10
10 mei 2017, 02:39
Antwerpen wordt een hyperintelligente ‘City of Things’ (http://www.ondernemeninantwerpen.be/nieuws/antwerpen-wordt-een-hyperintelligente-%E2%80%98city-things%E2%80%99)
8 mei 2015
Hoe gaat men tewerk? Welke data wordt er verzameld? Wie levert de data? Hoe gebeurt dat? Waar komt de data terecht?

Het Verzet
10 mei 2017, 13:57
Waar ik soms voor vrees ivm IoT is dat er zoveel fabrikanten plots hun toestellen aan het net gaan hangen die eigenlijk totaal geen kaas hebben gegeten van security. Met de alomgekende botnets als gevolg.

Eduard Khil
10 mei 2017, 18:32
Waar ik soms voor vrees ivm IoT is dat er zoveel fabrikanten plots hun toestellen aan het net gaan hangen die eigenlijk totaal geen kaas hebben gegeten van security. Met de alomgekende botnets als gevolg.

is nu al zo.

Eduard Khil
10 mei 2017, 20:53
IoT
Internet of Trolls :lol:

Vlad
20 mei 2017, 06:51
Stuurders en bestuurden.

Vlad
20 mei 2017, 06:51
Stuurders en bestuurden.

Nr.10
5 juni 2017, 23:27
Hoeveel sensoren zitten er in een smartphone?
De sensoren verzamelen data.
Met die data kan aan IoT gebouwd worden.

Nr.10
14 juni 2017, 00:39
GPS tracks your location.
Proximity Sensor turns the screen off when you hold it to your face.
Ambient Light Sensor automatically adjusts brightness.
Accelerometer senses movement and orientation.
Barometer measures pressure.
Temperature Sensor measures the temperature.
Humidity Sensor measures the humidity.
Magnetic Sensor measures the magnetic field.
Gesture Sensor senses your hands to navigate.
Infrared Sensor turns the phone into a remote control.
Eye Tracker pauses video when you look away.
NFC (Near Field Communication) shares data by touching two phones and also enables mobile payments.
Dual Cameras are available; one on the front and one on the back of the phone. Both cameras can record simultaneously in the Samsung Galaxy S6.
Dual Microphones are used in the phone; one microphone for voice and the other to listen to the ambient noise and create anti-noise using the noise-cancelling system.

Nr.10
14 juni 2017, 00:47
So far, phones usually had a CPU with a single core. With the launch of Samsung Galaxy S6, we are entering a new era of smartphone computing. The Samsung Galaxy S6 has an Octa-core processor (8 cores). Why does a smartphone need so much power? When a home computer can do everything with a slower processor (and single core), why does a smartphone need a faster processor (with 8 cores)? The Samsung Galaxy S6 has the following components that a home computer or even a basic business computer does not have: [de 14 sensoren, zie hierboven] These sensors constantly gather large amounts of data and need constant processing. A CPU must have multiple cores to compute all this data simultaneously. The CPU assigns tasks to different cores, keeping a single core from overheating. Less heat is generated and hence, less power is consumed. With battery technology not evolving as fast as CPUs, manufacturers don’t have a choice but to make CPUs that are more efficient in terms of power consumption and heat emission. BRON (https://digitaldimensionoftechnology.com/tag/why-does-a-smartphone-need-eight-cores/) 15 mrt 2015
8 cores
14 sensoren
grote hoeveelheden data
tegengaan van oververhitting
zo laag mogelijke energieconsumptie

Nr.10
16 juni 2017, 00:14
Welke infrastructuur, en vooral architectuur is er nodig om aan IoT te werken?
Miljoenen toestellen dienen verbonden te worden.
Ieder toestel gaat in real-time data verzenden.
Deze data dient een aantal bewerkingen te ondergaan:

importeren
verwerken
opslaan
analyseren
presenteren
toepassen

De IoT infrastructuur, beter: architectuur, kan niet anders georganiseerd worden dan via de cloud.
Als het via de cloud passeert komen de grote alomtegenwoordige alle opetende leveranciers al vlug in zicht.

Om te lezen:
Internet Of Things: New Architecture Needed (http://www.informationweek.com/big-data/hardware-architectures/internet-of-things-new-architecture-needed/a/d-id/1278882)
26 jun 2014
Het artikel is van drie jaar geleden. Opgelet, in dit domein een eeuwigheid, razendsnel gaat het.

Nr.10
22 juni 2017, 01:44
In navolging van bovenstaande post, om te lezen:
Big Data and IoT Lambda Architecture (https://www.opsgility.com/blog/2016/11/07/big-data-and-iot-lambda-architecture/)
7 nov 2016
Wikipedia definieert de Lambda architectuur als volgt:
Lambda architecture
is a data-processing architecture
designed to handle massive quantities of data
by taking advantage of both
batch- and stream-processing methods.

Nr.10
23 juni 2017, 00:27
De Lambda architectuur werd in 2013
ontworpen door Nathan Marz, gebaseerd op z'n ervaringen
met gedistribueerde big data verwerking bij Twitter.
Historisch belangrijk, deze Lambda architectuur.

In de stream-laag:

is lage latency vereist,
er wordt gewerkt met bijvoorbeeld Apache Storm,
en de output verdwijnt in een NoSQL database


In de batch-laag:

beheert de master dataset,
er wordt gewerkt met bijvoorbeeld Apache Hadoop,
en de output verdwijnt in read-only database


In de serving-laag:

wordt de output van beide voorgaande lagen bediend
voor queries uit te voeren
de output wordt gestockeerd op bijvoorbeeld Apache Hbase

De gebruiker is zich niet bewust van deze verschillende lagen.
Lambda Architecture: Low Latency Data in a Batch Processing World (https://www.blue-granite.com/blog/lambda-architecture-low-latency-data-in-a-batch-processing-world)
28 sep 2015

Nr.10
27 juni 2017, 00:44
Questioning the Lambda Architecture (https://www.oreilly.com/ideas/questioning-the-lambda-architecture)
Jay Kreps
2 jul 2014
Kreps stelt de Kappa architectuur voor.
Jay Kreps, op dat ogenblik werkzaam bij LinkedIn.
Ligt mede aan de basis van verschillende open source projecten.
Waaronder Apache Kafka, ook afkomstig van LinkedIn, hetwelke in 2011 naar de open source gemeenschap gebracht werd.
Apache Kafka is zeer belangrijke technologie voor de behandeling van data-stream.
Jay Kreps verliet ondertussen LinkedIn om Apache Kafka commerciëel te ondersteunen bij Confluent.
Kappa Architecture is a simplification of Lambda Architecture.
A Kappa Architecture system is like a Lambda Architecture system
with the batch processing system removed. To replace batch processing,
data is simply fed through the streaming system quickly.
BRON (http://milinda.pathirage.org/kappa-architecture.com/)

Nr.10
27 juni 2017, 01:14
Running at Google Scale With the Zeta Architecture (http://www.dbta.com/BigDataQuarterly/Articles/Running-at-Google-Scale-With-the-Zeta-Architecture-104043.aspx)
19 mei 2015
Een derde architectuur die op de proppen kwam is de Zeta architectuur, afkomstig van Google. Voor iedere organisatie die gebouwd wordt met big data en real-time in gedachte.

Nr.10
16 september 2017, 23:44
Zeta = 7 plugbare componenten. Zeer theoretisch. BRON
(https://www.linkedin.com/pulse/zeta-architecture-whats-name-jim-scott?articleId=6067686062011015168)
Distributed File System:
Utilizing a shared distributed file system,
all applications will be able to read and write
to a common location which enables
simplification of the rest of the architecture.
Real-time Data Storage:
This supports the need for
high-speed business applications
through the use of real-time databases.
Pluggable Compute Model / Execution Engine:
Different groups within a business
have different needs and requirements
for meeting the demands put upon them
at any given time, which requires the support
of potentially different engines and models
to meet the needs of the business.
Deployment / Container Management System:
The need for having a standardized approach
for deploying software are important
and all resource consumers
should be able to be isolated and deployed
in a standard way.
Solution Architecture:
This focuses on solving a particular business problem.
There may be one or more applications built
to deliver the complete solution.
These solution architectures generally encompass
a higher level interaction
amongst common algorithms or libraries,
software components and business workflows.
All too often solution architectures
are folded into enterprise architectures,
but there is a clear separation with the Zeta Architecture.
Enterprise Applications:
In the past these applications
would drive the rest of the architecture.
However, in this new model there is a shift.
The rest of the architecture
now simplifies these applications
by delivering the components necessary
to realize all of the business goals
we are defining for this architecture.
Dynamic and Global Resource Management:
Allows dynamic allocation of resources
to enable the business
to easily accommodate
for whatever task
is the most important today.

Nr.10
16 september 2017, 23:45
Van de Griekse letter Zeta, de zesde letter uit het Griekse alfabet.

Nr.10
16 september 2017, 23:53
Een stukje uitleg over de hexagoon:
The location of the components in the hexagon were chosen with good reason as well.
The distributed file system sits at the bottom as everything is built on top it.

The compute model / execution engine and the real-time data storage are effectively
married to the distributed file system
as that is where the data will reside whether the data is moving in, or out.

The enterprise applications were placed sitting on top of the solution architecture
and the deployment / container management system
because they are the support for the enterprise applications
and define how the enterprise applications will work.

Lastly, the resource management touches everything
and thusly sits in the center of the diagram.