|
It's not my favourite way of spelling it, neighbour. Knowing how to apply grammar rules takes some labour, but I try to find some humour in it.
|
|
|
|
|
#008AD8[^]
You're welcome!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
|
|
|
Azure is not really something you learn, but a bunch of services/hardware that you rent from MS. I've been using Azure services since 2015 to host lob web apps for multiple clients. You may think that it's the same as a webhost but the difference is that the resources you are renting are scalable, both up and out.
One type of Azure service that I am using is a Server 2016 VM hosting multiple customer lob web applications. In the beginning, we rented a total of 4 webapp (.Net btw) slots and 2 sql databases for <$100 a month. When we needed to add more apps, the decision was made to get another domain name and tie it to an Azure VM. It's handling half a dozen customer web apps nicely, and can likely double capacity before I even think about moving up a tier. It's super nice when I need to troubleshoot something for a customer...just rdc in and fix the problem.
They used to give you a 30 day free trial. One word of advice if you decide you need anything Azure...check out the deep discounts you get for annual reservations.
"Go forth into the source" - Neal Morse
"Hope is contagious"
|
|
|
|
|
Thanks for the info. It's interesting you mention hosting because I'm going to be setting up a Web API for an app I'm working on for a client. I was just going to host it in IIS on their server. How/why would using Azure be better?
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
Kevin Marois wrote: Web API for an app I'm working on for a client. I was just going to host it in IIS on their server. How/why would using Azure be better? In that case you could use just an Azure function. Azure Functions Overview | Microsoft Docs[^]
Instead of you setting up IIS, the function just works. Under the hood it might be running IIS or something else (probably IIS though) and could be running on a linux OS or windows. The point is, all you care about is that code, not the infrastructure. But you can still scale up and out as needed.
|
|
|
|
|
Thanks. Good to know!
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
Kevin Marois wrote: How/why would using Azure be better?
If you have easy access to the client's server (for setup/maintenance/troubleshooting) such as through VPN, Azure may not be beneficial or preferable. Also, if this is a one-off or the data source is on-premise, I wouldn't consider Azure.
Consider though if you wanted to offer your software as a service to other clients through your own customized domain name? Another benefit is that you are not subject to upgrade/replacement cycles of your clients. Also, it puts you in control of recurring revenue...no pay, no play.
"Go forth into the source" - Neal Morse
"Hope is contagious"
|
|
|
|
|
kmoorevs wrote: If you have easy access to the client's server (for setup/maintenance/troubleshooting) such as through VPN, Azure may not be beneficial or preferable. Also, if this is a one-off or the data source is on-premise, I wouldn't consider Azure.
Both are true in this case
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
kmoorevs wrote: it puts you in control of recurring revenue...no pay, no play
Well, Microsoft could say the same to you.
|
|
|
|
|
I think the Caribbean is azure; or is it the Mediterranean?
|
|
|
|
|
Maybe this Azure FAQ Part 1[^] article is a start. There may be many others at CP as well. I think @Sander Rossel, wrote a book on Azure if my memory serves.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Kevin Marois wrote: should I care? Yes!
Look at Azure (in its simplest form) as a rich collection of cloud technologies that you can easily use to enhance an existing app without having to re-invent the wheel or having to build out a large amount of server-side infrastructure. I've been spending a lot of time (and having a lot of fun) learning the basics of function apps, cloud TTS, send grid, cloud storage (standard SQL server plus blob storage) and much more. What blows my mind is how easy it is to get started with a specific aspect of Azure that's of interest to you. And this doesn't even begin to touch the slew of AI related functionality (ML, sentiment analysis, image recognition, etc.) that's also available for use.
I Azure!
/ravi
|
|
|
|
|
Thanks!
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
|
Thanks!
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
As other said... Sander Rossel wrote some books about Azure for Syncfusion Succintly PDF-Series... (you need registration though)
Some messages below is the "Sound of the Week"[^]
Take a look into the signature, the links are there.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Thanks!
Unfortunately, I don't think any of my books explain just what Azure is.
All of them assume some Azure knowledge already.
That said, the introduction to Azure Serverless Succinctly about sums it up and gives some examples of Azure services I think.
The other chapters and examples should be easy to follow, but focus purely on the serverless aspect.
|
|
|
|
|
Azure is amongst the clouds, high up in the sky, unreachable for Windows Desktop persons like me.
|
|
|
|
|
I am with you on the Desktops thing!
ed
|
|
|
|
|
Just a competitor to AWS, but with Microsoft's notorious desire to make things more complex.
Note: AWS is also complex, but I find it easier to piece it together.
Bond
Keep all things as simple as possible, but no simpler. -said someone, somewhere
|
|
|
|
|
Azure is Microsoft's Cloud Services, which are similar to the Amazon Web Services product or AWS.
Everyone is rushing to post new data and applications in the Cloud because it is cool and allows corporations to cut costs by not hosting their own server infrastructure for both databases and web applications.
However, from a military science perspective, which is borne out by quite a bit of reporting in the mainstream press as well as security analysts, Cloud Services are simply big, juicy targets that have very large attack surfaces. And since, by the reporting of a recent survey, approximately 87% of all businesses surveyed really don't put much of an emphasis on security, Cloud Services are subsequently begging to be attacked; and they are being breached on a regular basis.
Cloud Services are an attempt to centralize corporate data centers on third-party infrastructure to make it look like companies are saving money. However, if such a service is breached, most of the companies on them can be easily fu... fuc... f***... f***ed...
Using Cloud Services is like bunching your Army together in one mass formation so the enemy can toss a few missiles at it and destroy most of your army in one attack.
And since most corporations are simply stupid bureaucracies with even dumber leadership, they all go like lemmings to the same place everyone else is going so as not to be last on line for the big surprise...
Steve Naidamast
Sr. Software Engineer
Black Falcon Software, Inc.
blackfalconsoftware@outlook.com
|
|
|
|
|
short answer: no.
while we technically have Azure at my workplace, my only use for it is AD auth for various web apps. I don't put apps or services up there at all, it doesn't make logical sense for how we run.
I miss the days of being solely a Windows developer, and I don't see everything moving to the "cloud" so you should be fine as long as there are reasons to have desktop apps.
35 years, wow. you got me beat by about 12 years.
|
|
|
|