I didnt have any idea what Azure IOT is. My manager told me that IOT is a new thing and we can replace IIS with Azure IOT but I couldnt find any such information. According to many articles I read and as per my understanding, IOT is used for duplex communication between the devices and services in a cloud environment.
Can anyone explain about Azure IOT nicely? Does it replace IIS? We want to move our product from normal servers to Azure Cloud servers. Do we still need IIS or IOT is there to replace it?
As always, it depends. If your current website is a gateway to communicate with IoT devices (IoT stands for Internet of Things, think temperate sensors, light sensors or more advanced devices) then it could. Otherwise I really doubt it.
Azure IoT is a managed service that allows device provisioning, device to cloud and cloud to device communication. It does not allow for hosting user interfaces like IIS does.
The most probable thing to do is to move to Azure Web Apps, which is basically IIS as a service. (There is a lot more to it obviously!)
And you definitely need to talk to your manager. Hearing the latest buzz words without knowing enough to be able to place them in your context can do a lot of harm.
Related
I'm working on a IoT-solution that includes some physical devices where we don't control the hardware, and all communication is done via API:s. I would still like to utilize Azure IoT-hub for the messaging and management of these devices.
My idea is to create I device client and that runs in the cloud and integrates with the IoT-hub and the API:s. Is this a feasible strategy or am I on the wrong path? If, not what is the appropriate resource in azure for spinning up the clients?
If your devices are not capable of directly connecting to your Azure IoT hub then you have some alternatives. Yes theoretically you could create a device in the cloud that talks to the real device and forwards that data to your IoT hub. There are a couple of other alternatives. You could use an Azure IoT Edge Gateway. This will connect to the IoT hub and can represent multiple devices. You create an Edge Gateway module that can talk to your devices which will allow you to pass on the data for transmission to the IoT hub. It has a plug in module type of architecture. A product called the Protocol Gateway performs a similar function which might also meet your needs.
We need to develop integration between ERP (Dynamics Nav) and cloud-based telephony provider.
The provider needs to have an endpoint published and accessible from internet but for security reasons it is not possible for us to allow inbound connections to our network. I think it should be possible to solve this by hosting small application in Azure which will serve as endpoint for telephony provider and to which ERP will connect as outbound persistent connection. The app will just forward requests to ERP.
Since I'm new to Azure the question is what of azure capabilities I could use to solve the task aside from hosting actual VM with application there?
I've just implemented the same using Azure Service Bus.
The VOIP system is putting a small JSON with call details after the end of the call and I'll get the messages from the Service Bus Queue from NAV.
The code is not complicated at all the whole solution is simple and cheap!
Let me know if you want to know more (= you need the code).
Cheers!
Azure AD has the concept of an "application proxy" that will open internal applications up using a connector that runs on prem. This doesn't require inbound ports and is protected by Azure AD authentication.
It's intended more as a user-facing way to get access to Legacy applications, although I don't see why it couldn't be used for integration as well.
https://learn.microsoft.com/en-us/azure/active-directory/application-proxy-publish-azure-portal
Otherwise, you could link an Azure Site to Site VPN up and use a service like API gateway to manage connections though this is more complicated.
I have a couple of web applications deployed in Azure and I would like to move them to another subscription. The problem is that these apps are connected to the VPN gateway which cannot be moved. I suppose that if I will ask support stuff to move my applications, applications will be disconnected from the old VPN. Am I right and is there any better way to switch to the new subscription with minimal service interruption?
You have a good question. Actually, VPN gateways can be moved between subscriptions. However, the migration between subscriptions is all or nothing. If you want to migrate subscriptions, everything within that subscription will be migrated to the other.
Our support engineers will migrate everything, including VPN gateways, with minimal interruption. Please open a support ticket and our support engineers will be happy to take care of this migration for you.
Thanks,
Bridget [MSFT]
I have searched a lot on this topic but didnt get any satifactory answer.
In Windows Azure how can we consume an external (third party) Web Service from the worker roles? Is it as simple as using a web reference in the solution or is it necessary to use Azure Service Bus?
It's as simple as calling the webservice using whatever method you need (REST, SOAP, etc.). For .NET developers using .asmx or WCF SOAP services, just generate the proxy like you normally would. In this model, there is no difference between what you do onpremises when the cloud is the client.
You would look at using the ServiceBus when you are hosting your own services (as opposed to consuming them), typically behind firewalls onpremises, and you want to give secure access to them or integrate them into cloud scenarios. There are other scenarios and capabilities of course, but that is a main one. If you simply want to consume another web service, the ServiceBus has nothing to do with that.
As long as the 3rd-party web service endpoint is reachable, use it the same way you'd use it from an on-premises server. If you need to connect to a service endpoint behind someone's firewall, then you'd want to consider AppFabric Service Bus.
Just remember that you'll be paying for bandwidth out of the data center (unless the 3rd-party web service is Windows Azure homed, and in the same data center).
What is the diffence between appfabric service bus and WCF?
Is service bus is an alternate for wcf on azure?
Does service bus provide all the functionality as wcf?
when to use service bus and when to use wcf in azure application?
Please help me....
Thanks in advance
The service bus doesn't provide services themselves - instead if provides connectivity to services - e.g. routing, scalability, security, etc.
So you will normally write your services in WCF, and can then optionally provide connectivity to those services using the bus.
This article provides a good intro to the service bus - http://msdn.microsoft.com/en-us/magazine/dd569756.aspx
You don't need to move away from WCF. However, imagine your application, sitting in Windows Azure, trying to access a WCF service in your data center (or hosted somewhere). And imagine that the data center has a firewall that blocks incoming connections. Service bus offers a way for you to make service calls to that service endpoint. Essentially, the two sides each connect to an AppFabric Service Bus endpoint. At that point, they have a connection where WCF calls can be made.
The bindings are similar to what you use today. If you're using netTcpBinding, for instance, you'd now use netTcpRelayBinding, as the calls are relayed through the service bus.
The Windows Azure Platform Training Kit has a very good introductory lab to walk you through the basics of Service Bus.
ServiceBus is a way to communicate asynchronously. Asynchronous communication implies it is good for multi-machine programming due to fault tolerance and it does not block.
WCF is a programming stack used to interface with various mediums (ie. Pipes, TCP, HTTP, ServiceBus).
They serve orthogonal purposes. You can use WCF without ServiceBus and ServiceBus without WCF.