I have an application using Azure Functions and would like to add Azure SignalR. During development, myself and the other developers would like to avoid our local (potentially modified) applications talking to each other through SignalR.
Does any tool exist that would allow us to emulate / run SignalR offline for the purposes of development only?
If you're using Azure SignalR Service through the Azure portal, then no.
However, there's a free tier of the SignalR Service which you could use. Depending on the size of your dev team you could just create an instance each.
Related
Team,
I have a complete running cloud service application upgraded to latest Azure SDK version and unfortunately need to dump this into a CSP subscription. But I came to know that Azure CSP supports only the Azure Resource Manager model, the cloud service is a classic deployment model. So we cannot create a cloud service within a CSP subscription.
Is there any other alternative within Azure CSP to using "cloud service" so that we can migrate with minimal changes. Please help
Firstly, here are some good reads on Microsoft Docs to help comparing the options available and make decisions based on your requirements:
(I mean requirements like Hosting features, Service Limits, 3rd party software installation and RDP access is required or not, Network isolation to a separate VNET is required or not, Cost considerations, minimum SLA, Regions available, instant deployment and auto-scaling, state management etc.):
Azure App Service, Virtual Machines, Service Fabric, and Cloud Services comparison
Decision tree for Azure compute services (This one covers a big spectrum.. simple virtual machines, Batch, Functions, Containers, AKS, ServiceFabric)
Criteria for choosing an Azure Compute Service
Also know that when looking for alternatives, it's not uncommon to make use of multiple compute or other Azure service options by breaking up an older solution into parts at the time of such migration (for e.g. A serverless compute option like Azure Function + Service Fabric + something else if needed).
Generally speaking (and without knowing much about your application from your question currently), Azure App Service and Service Fabric could be considerations IMHO when migrating from an existing Cloud Service, but this is exactly where detailed requirements help you in decision making.
On a side note, here is a list of Azure Services available in CSP - Available Azure services in Azure CSP
I am looking for scalable hosting for an API but I am getting a little confused with Azure. Ideally I want something that means I don't have to manage OS updates and security, just deploy my API code.
Is this possible with Azure? What do I need to sign up for?
In general, you are looking for the Platform as a service offer. Check What is PaaS?. For the API deployment you should check the Azure App Services. Azure API Management is for advanced API management or when you want to expose multiple APIs using a single gateway.
I published a web api in Azure via Visual Studio. I would like to know if it is PaaS or IaaS.
When I search for the answer, I find lot of definitions about the PaaS and IaaS.
But I did not find where it is clearly defined which services found in Azure portal are PaaS and Which are IaaS?
Thanks.
With best regards,
SR
IaaS (Infrastructure as a Service):
Cloud infrastructure services, known as Infrastructure as a Service (IaaS), are made of highly scalable and automated compute resources. IaaS is fully self-service for accessing and monitoring things like compute, networking, storage, and other services, and it allows businesses to purchase resources on-demand and as-needed instead of having to buy hardware outright.
PaaS (Platform as a Service):
Cloud platform services, or Platform as a Service (PaaS), provide cloud components to certain software while being used mainly for applications. PaaS provides a framework for developers that they can build upon and use to create customized applications. All servers, storage, and networking can be managed by the enterprise or a third-party provider while the developers can maintain management of the applications.
Source: SaaS vs PaaS vs IaaS: What’s The Difference and How To Choose
In short: with IaaS you use infrastructure (mostly VMs, networking, ...) from your cloud provider that you manage yourself. With PaaS you use an abstraction layer on top of some infrastructure where you do not manage the underlying infrastructure itself. You only manage the application and its data.
If you've deployed to an App Service, you're using PaaS. If you've deployed to a VM that you manage and runs IIS, you're using IaaS.
Another interesting read: What is PaaS?
When I publish an api to azure from visual studio I see an existing app-service plan and also an option to create a new plan. The api I am going deploy will be used by the web application which was deployed using the existing service.
I have the following questions:
If I use the existing plan what would happen to the sites which are
already deployed using that plan?
Should I create new or use
existing?
Cost-wise which is the best option?
By using the same service plan to host the web app and the api, nothing will happen to the existing website besides you won't have any extra cost. The web apps will share the same resources.
If you create a new service plan for you api, you will have extra cost depending on the pricing tier you need.
The choice can depend on your scaling needs. If you need to define differents scaling plan for the api and the web app, it's a good idea to use two services plan, if not an unique service plan can be used.
I am a little confused about two new technologies receiving a lot of buzz currently;
Can somebody please explain to me what the difference (or similarities) are between Azure and .NET Services?
Are they one and the same thing?
Is Azure the Cloud OS that my .NET Services run in?
Is .NET Services a component that makes up the greater Azure vision?
Thanks
You've basically got it right that .NET Services is a component that makes up part of the Azure platform. Check out the Azure Services graphic for a visual representation of the components.
Azure is composed of the operating environment and the base services that are used to host cloud applications. It provides the base capabilities (web and worker processes) as well as the simple data storage offerings.
.NET Services are the services that many applications will use to create cloud scale applications, although originally the services were mostly geared toward enterprise development. It includes the access service and service bus.
There are also a few other services that are provided:
SQL Azure is the SQL Server for the cloud offering. It is used like a regular SQL Server instance, for the most part, but is hosted and sericed by Microsoft.
Live Services are consumer focused services that make use of many Microsoft services: Mesh, Live ID, Messenger, etc.
One thing to note is that, although these services are offered as part of the Azure platform, the .NET Services should be usable from any platform. The are REST based services that can be consumed by any application that has the ability to call REST services.
Windows Azure is a cloud services operating system that drivers the Azure Platform, which is an open platform that supports/will support multiple Microsoft and non-Microsoft languages and evironments. Azure Platform
.Net Services are a set of libraries that aid in working with the Azure cloud based infrastructure services available. .Net Services