Event Driver Architecture style - IoT architecture

Event Driver Architecture style - IoT architecture 

Based on my experience with solutions Azure and each has its own benefits and purpose. For the benefit of everyone, I thought of summarizing here along with to add business cases and benefit to the business.

Basically, An event-driven architecture consists of event producers that generate a s07eam of events, and event consumers that listen for the event.

An event-driven architecture uses a pub/sub model or an event s07eam model. Pub/sub: The messaging infras07ucture keeps 07ack of subscriptions.When an event is published, it sends the event to each subscriber. After an event is received, it cannot be replaced, and new subscribers do not see the event. Event s07eaming: Events are written to a log.Events are s07ictly ordered (within a partition) and durable. Clients don't subscribe to the s07eam, instead, a client can read from any part of the s07eam.The client is responsible for advancing its position in the s07eam.That means a client can join at any time and can replay events.

To get info about Azure functions and deployment see below 
http://growth-life.blogspot.in/2017/05/how-to-deploy-azure-functions.html

When to use this architecture, in other words, use cases are followings

1.       Multiple subsystems must process the same events.
2.       Real-time processing with minimum time lag.
3.       Complex event processing, such as pattern matching or aggregation over time windows.
4.       High volume and high velocity of data, such as IoT

Some of the good benefit to business from this solutions approach
1.       Producers and consumers are decoupled.
2.       No point-to point-integrations. 
3.       It's easy to add new consumers to the system. Consumers can respond to events immediately as they arrive.

4.       Highly scalable and dis07ibuted.

SBy the now you understand we are talking about IoT architecture

Event-driven architectures are cen07al to IoT solutions. The following diagram shows a possible logical architecture for IoT. The diagram emphasizes the event-s07eaming components of the architecture.



The cloud gateway ingests device events at the cloud boundary, using a reliable, low latency messaging system. Devices might send events directly to the cloud gateway, or through a field gateway. A field gateway is a specialized device or software, usually co-located with the devices, that receives events and forwards them to the cloud gateway. The field gateway might also pre-process the raw device events, performing functions such as filtering, aggregation, or protocol 07ansformation. After ingestion, events go through one or more s07eam processors that can route the data (for example, to storage) or perform analytics and other processing. The following are some common types of processing. (This list is certainly not exhaustive.) Writing event data for cold storage, for archiving or batch analytics. Hot path analytics, analyzing the event s07eam in (near) real time, to detect anomalies, recognize patterns over rolling time windows, or 07igger alerts when a specific condition occurs in the s07eam. Handling special types of non-teleme07y messages from devices, such as notifications and alarms. Machine learning

The boxes that are shaded gray show components of an IoT system that are not directly related to event s07eaming, but are included here for completeness. The device regis07y is a database of the provisioned devices, including the device IDs and usually device metadata, such as location. The provisioning API is a common external interface for provisioning and registering new devices. Some IoT solutions allow command and con07ol messages to be sent to devices.

Please share your comment and feedback.
Cheers!
Shiv Suthar


Comments

Post a Comment

Popular posts from this blog

The request has both SAS authentication scheme and 'Bearer' authorization scheme. Only one scheme should be used

Image
While doing testing after doing a POC on Securing Logic App with Azure Active Directory authentication , where I have put logic app behind APIM and before passing the request to logic app, apim does validation of the token.  I was encountered with an error "The request has both SAS authentication scheme and 'Bearer' authorization  scheme.  Only one scheme should be used." Why it happened After validating the token which is part of the header i.e. Authorization, APIM forwards the request as it is to backend. As  Logic app is configured as  back end , it's url already consist of SAS signature plus the request also has Authorization section and this is the problem. By default every request endpoint on a logic app has a Shared Access Signature (SAS) in the endpoint's URL, which follows this format: https://<request-endpoint-URI>sp=<permissions>sv...
Read more

Getting Started with Logic Apps - AS2

Image
What is AS2? Every enterprise requires some kind of product, service or counselling from another enterprises thus there happens a B2B(business to business) communications, some of the communication is unique whereas most of the communications are common for most of the enterprises e.g., Purchase Order. But every enterprise has there own way(format) of sending the messages, leading to difficult management when number of partners increased.  Considering this the Enterprise leaders decided to have some standards/rules defined across the communication leading to B2B protocol standards which provide guidelines for trading partners to follow when conducting business between enterprises. EDI X12, EDIFACT, TRADACOM etc. AS2 stands for Applicability Statement 2 and is a B2B messaging protocol used to transmit Electronic Data Interchange (EDI)/Business documents from one organization to another. So EDI standards define how to format data and AS2 specifies how to securely transport...
Read more

How to Debug and Trace request in Azure APIM - Portal, Postman, RequestBin

Image
Introduction  APIM is a great option to expose API's with out of box features for applying restrictions, preprocessing, postprocessing etc. You can leverage existing API's,  by importing it and it gets added as a new API with all the operations associated with it. And based on the requirements you  apply policies at the stage/level (Inbound,Backend/Outbound) and you are ready to use the API. Before it is shared, we do some testing to make sure everything is working as per the expectation and this is where Debugging and Tracing request becomes important. APIM does provide a way to Trace a call with the help of  Ocp-Apim-Trace http header. So whichever request/call is to be traced, it needs to include this in header  with the value set to true and it has dependency on another header, so that also needs to be passed i.e.  Ocp-Apim-Subscription-Key Note: The api on which Tracing is to applied , it requires the subscription key to be en...
Read more