A heartfelt welcome to the Wechsler Consulting Cloud Campus section!
This is our news, training, information and workshop area. In here, we want to help you through the information jungle around Cloud technologies. We also want to keep things as easy and understandable as possible and are currently joining forces to get more and valuable content onto our Campus.
If you have something interesting, you would like us to shed some light on, just let us know, by dropping a comment or sending an email at: info(at)wechsler-consulting.de .
Nevertheless, test the filter in your development environment, before rolling it out in production. It should normally not have any negative effects, if you are using the endpoints in a standard way, but one only ever knows after trying it out. 🙂
The Wechsler Consulting Cloud News – December 2020 – episode provides insights on the newest Azure IOT Central features, the latest additions of virtual network private endpoints for Azure Automation and IOTHub as well as the release of Event Hubs on Azure Stack, which all have reached global availability (GA) this month.
Focus Topic of this month are Azure Digital Twins. A new platform service providing sophisticated querying and management capabilities for comprehensive IOT solutions. All backed by great infrastructure and Tool support.
All the best to all our colleagues and friends out there! Our thoughts are with You and Your families, stay safe and healthy! We are looking forward to work, talk, create, innovate and have fun with You in 2021!
Azure Digital Twins are the virtual counterparts of systems, sensors or even complete factories in the real world. The Digital-Twin concept has already around for a time and I have used it in several customer projects, to get a as-good-as real-time view on the state of complex systems. It comes with the additional benefit of having historical data, e.g. to follow up on errors, or predict the future with the help of machine learning algorithms. In addition, the ability to simulate and test possible future situations or different development scenarios with a close-to-reality model, cannot be overrated!
While these custom implementations are working great, it must be admitted that there is significant effort necessary to reach this goal. Due to this, I consider Azure Digital Twins as the arrival of a game changing platform service for future IOT solutions. Azure Digital Twins save a lot of development effort, are very good integrated with other Azure IOT offerings such as IOTHub, IOT Central and build on IOT Plug & Play. This is taking the fast lane ! It is a powerful combination of services, which are going to revolutionize the way IOT solutions will be built in the coming years. The good development story behind Twins is supported by great tools for visualizing and reporting. This is something often neglected by standard IOT approaches. Any neglection in this area is dangerous, because capable reporting and querying functionality is essential to run, maintain and evolve your solutions in field.
I predict the Azure Digital Twins will be seen quite often in upcoming solutions. 🙂
The Wechsler Consulting Cloud News – November 2020 – episode talks about renewable energy in Azure data centers in Sweden, the newest feature in Azure IOT and very helpful addition to create Azure Active Directory B2C custom user journeys, which are intended to solve one of the major pain point of this service.
Highlight and Focus Topic of this month is Microsoft Pluton. A new hard- and software security solution derived from Xbox and Azure Sphere now entering the PC stage.
IOT Central is Microsoft’s low code, low effort, ease of use approach into the world of embedded projects. This is quite a demanding challenge, because real world problems tend to be complex and what can you do to make these simple in a tool? Well, normally you start with defining an environment, to get rid at least of some of the parameters and thus reducing complexity. This is a valid approach, but for a tool/service vendor it carries the danger that the overlap of your defined environment to common real-world use cases of customers, is not large enough, or, as a worst case, even not existing. Azure IOT Central, in the beginning, felt a bit like: great base features, but not enough to cover a complete project spectrum of demands. Therefore, to me it was good for samples or a quick POC for a project. However, the IOT Central team kept improving steadily and so the product is getting more serious as we speak.
The newest update provides some very interesting features, like jobs that can be execute on devices (very important for device management), webhook improvements looking at identity management, device templates to support IOT Plug & Play as well as improvements on the dashboard.
At least for me enough new stuff to justify a closer and serious re-visiting look into IOT Central!
… or, globally available (GA), as Microsoft tends to say. Technically, this is absolutely great news, because the newest version of the Microsoft development runtime brings a lot of new features, fixes and performance improvements. It also cleans out a lot of the past architectural wanderings, the .NET platform has undergone in the recent years. A really good summary of the new features and changes can be found in the .NET Core documentation.
Nevertheless, I always stand in wonder, how the marketing guys find the most confusing names for new products. Must be a contest. With .NET 5.0, this is hilarious! It is not .NET (well classic!), but based on Core, while the ASP .NET and Entity Framework parts keep “Core” in their names and, by the way, it does not replace .NET Standard. I give 10 out of 10 obfuscation points…..
But nevertheless, developers, this is a great runtime and SDK release, so lets get over the naming accidents. As always! 😉
The Wechsler Consulting Cloud News – October 2020 – episode sheds light on new and very promising features in Azure Active Directory (Continuous Access Evaluation), Event Grid integration of Key Vault and App Services Private Endpoints, all of which are great assets in creating modern, scalable and efficient Cloud solutions.
Focus Topic this month is Tiny ML, a completely new approach using ML models on small embedded devices, bringing intelligence closer to places where things are happening. This can turn into nothing less than a game changer in the IOT industry!
In nearly every IOT project I had the opportunity to work in, time series data played a very important role. The problem for this type of data is that it normally comes in larger volumes and is therefore not always great to handle. This is especially true in projects, where you have to cope with small storage on devices and no central data store, which makes it very hard, if nearly impossible to get a global view on the behavior of these solutions in time. One could work with thresholds and alerts, but this approach never gives you the chance to detect trends and get “ahead of the wave” to react better, faster and more precise to certain events. Some of the industrial communication standards, such as OPC UA and SCADA, try to tackle this issue by providing historic data functionality in their communication layers, but this is just a single aspect of a comprehensive data solution.
Cloud architectures are able to help in this case, if you have the chance to collect time series data either centrally, or on the edge. A very valuable asset in Azure and in this context is Time Series Insights. It is a cloud service allowing you to handle query, transform visualize and correlate your different data streams into comprehensive views and insights. There are also connectors into reporting tools such as Power BI available. Using the M365 infrastructure Power Automation or Azure Logic Apps and Functions, serverless integration into corporate business process and control processes is also not a problem.
Bandwidth terror through an abundance of chatty sensors!
For example, in a manufacturing building, network traffic would go through the roof, if “everything” would be directly connected to the Internet (although, it is the Internet of Things) and, of course, it would be a security nightmare, too. Well, let us leave the latter topic aside for a moment and stick to the traffic requirements. The Cloud promise was, connect everything to the Internet and in the Cloud, magically, everything gets done! While this is not false in a lot of scenarios, it is not always true! Depending on solution use cases in focus, there are quite a few scenarios where distributed smart architectures have significant benefits over a centralistic approach. In these cases devices on the “Edge” come into play. They are gateway devices running pre-processing logic and providing storage capabilities to handle part of the overall system workload on-premise, on the edge to the Internet. By doing this, enable the transformation of raw events into higher quality events, such as e.g. the reporting of temperature sensors only, if set limits are exceeded. The higher quality events are passed into the Cloud solution and are handled there to trigger related business logic. Benefits of this design include
Significant lower traffic on central system
Better manageability / monitoring and security of data flow
Robustness against network outages (at least in some of the scenarios)
but, it comes with challenges, as well, such as:
Handling of business logic on the edge
Device management of IOT devices as well as edge devices
This needs to be taken into consideration!
However, if you are a vendor creating Cloud solutions experiencing a lot of data ingress, sooner or later you end up installing Edge devices to sort out raw events spamming your backend. You will buy devices and or talk to the customer to install these devices in the on-premise data-center. The drawback with this approach is that it adds a lot of upfront cost to your solution. Edge devices might be quite capable, full-fledged and therefore expensive servers that a customer may also want to include into his system management to keep them patched and secure. This triggers often time consuming approval processes to get things into place. All of this may kill your project or POC before it even has started!
So, is there a smarter way to approach this issue? As you may have guessed from the title of the post, there is. Microsoft is extending its Cloud-native rent-my-system approach to edge hardware and software. In this case the system of interest is called Azure Stack Edge (fka Azure Data Box Edge – Microsoft likes the renaming game, as we know). There is a very informative IOT Show episode on this solution, still using the old name.
Benefits of the Cloud-rental approach are that the Stack Edge devices are managed centrally via an Azure service. The service allows the installation and management of Azure IOT edge modules taken over the responsibility for the distributed logic in the system. Looking at IOT devices, it is especially interesting that these devices can be connected to a local (Edge) instance of IOTHub and also be managed from there, which gives you the best of both worlds: The devices are safe behind the firewall, but still accessible via the Edge gateway for administrative purposes! Microsoft operates the Edge devices as an appliance, which means it takes over responsibility for any OS (Stack Edge is running on Linux) or runtime patches. IOT Edge modules deployed can be available building blocks from Microsoft or 3rd party vendors, as well be self-developed Edge modules suiting the implemented solution.
This is really powerful, because it leaves solution developers the flexibility to draw existing commercial building blocks e.g. for AI or highspeed processing from Azure Marketplace and focus on the business needs of the solution.
If a customer needs a test at their location, the rental model is not to beat. Just ship your devices and a pre-configured Edge device and a POC can be up and running in minutes, not costing a fortune and hardware. If not suiting, it can be stopped any time with out wasting more costs and energy.
Looks like a quite innovative, efficient and modern approach to me! 🙂