The Cloud and Cloud Architecture Explained - Computer Stuff They Didn't Teach You #15 

Amazon said 'lol'

Yeah, you should check your documentation more... Barnes and Noble doesn't have any cloud services! What are you talking about ???

Aw, thanks!

Serverless is awesome. I use it at work for API stuff a lot, and once you get your head around it it's fantastic. That said, it doesn't do everything, and we have lots of applications running in everything from on-prem application servers, to containers, to serverless, and queues, all interacting. Integration is fun.

Thanks! I am trying

It depends. What he is talking about here is a sort of abstracted virtual machine where you don't have to worry about the operating system and can deploy virtual appliances (in the form of application servers) that have been predefined. In this case, rather than having a virtual machine that you then need to install say IIS on, then configure it, add your site, perhaps some routing rules if you run more than one site, etc. You instead abstract away the OS and just say I want to run an IIS based website and Azure sets up the virtual machine with the appropriate software stack to do so. It might do that with a container technology, but you don't really care exactly *how* you get a webserver, just that you want one. This is slightly different to I want a website and don't really care where it's run, and then the service provider can move that application container where they want as long as it meets the service goals.

Good idea

My VS solution that writes several GB of binaries would love that. Trying to use 3rd party ones makes me wish it was a supported feature in Windows, even if it was limited to Pro and Enterprise or sold in the store for an additional fee.

$20 is pretty amazing. I don’t think Azure can ever beat that

@@shanselman Yes, I do understand that it's not possible for Azure to compete with the normal or budget web hotels out there in terms of price, but let's say I were to set up 5 .NET Core/5 projects on Azure, with 5 MS SQL-databases and domains. Would one App Service in Windows-environment (or should it be Linux?) suffice? You didn't talk much about IIS (or Kestrel) in this video, I assume all of that would be taken care of so that a .NET Core App would run the same on either OS/environment?

Sorry this is off-topic, Hi Scott I have signed into google that I don't like doing to let you know that your stream on Python and Linux for Windows - Scott Hanselman || PyCon Africa 2020 Sep 8, 2020 you want to watch it back a lot of the time you are seeing did you see? and no we didn't, your screen was not sharing with us, the lady was just going along with you so I presume she could see what we couldn't, I am a big fan of yours I am just saying this to inform you in case you did not know thanks, Matt.

@@mattselllars8640 you mean this one? Was the issue live? I see everything here ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-yb8EWmvFIXw.html

I ask myself that weekly. Thanks for the comment!

Email me first name at last name and I’ll find one.

44 t20

don't know if this help stackoverflow.com/questions/7092553/turn-a-simple-c-sharp-dll-into-a-com-interop-component

@@ewdlop1 thank a lot! i'll check it

Scott, you made it so simple! brilliant video! Many Thanks, for sharing your knowledge

Was just a joke, my friend! I can say whatever I want. :)

Not sure which web apps you're talking about, but in terms of Scott's website essentially what he's talking about is an abstracted IIS, for example. How it is deployed is irrelevant, just that you have a website hosting platform that you can put a site on and configure to do certain things, and Azure deploys that how they see fit on the abstracted virtual machine that you also don't see. Office 365 is a webapp, Facebook is a webapp, a virtual desktop isn't really, it's more like a managed service, or Infrastructure as a Service - you can run whatever apps you like on a windows desktop environment, but the OS itself is abstracted and patches etc managed by Azure, for example. Think more like the old mainframe/thin client infrastructure, except delivered virtually over the network to any client you may have available at the time. Containers are generally more for non-gui type apps - you can containerise user applications, but generally you would containerise something like a game server, or a piece of support software like a database server that a user app might talk to. We use this in development all the time, so we can spin up mock supporting services for the piece of software we are currently working on. Containerisation is just a nice way of saying bundling the software with all the dependencies it needs to run, and sandboxing it so it can't talk to anything it's not allowed to (you can open ports and things, but generally it's sandboxed). You still need to define the setup within that container, what you need and how it gets installed. It can't see anything outside the container, unless you explicitly map part of your filesystem into it, or a shared network filesystem, for example. In your example, the adobe container would need to have your project mapped into it on some sort of filestore, it can't generally access your local filesystem. What that allows you to do is run this piece of software anywhere you like, on any container infrastructure, on a dev machine, or a cloud server, or under a kubernetes that might decide it needs 10 of them for the load. That container does just one thing, it's the infrastructure around it that ties things together to fulfil a purpose. Serverless goes one step further - you don't care how or where a piece of code runs, only that it does. It might be in a container (probably is), but it's not on a specific vm or anything, the service provider decides how they manage that. You just have an API exposed to the web, and a piece of code that does something when it's called, and perhaps some configuration to allow it to talk to the hosted database server you also spun up that you don't care how or where it runs, just that it does. The database server is more like an application as a service, you don't have access to the VM it's running on, just access to a database. My experience is with AWS (and proxmox) so terms might be slightly different but does basically the same thing.

@@morosis82 WOW Matthew, thanks so much for the detailed explanation, i kind of got that a virtual desktop deployed over a network wasn't the same as a cloud solution, when you talk about facebook as an app are you talking about the phone app? If so then that's easy! I guess i haven't had much exposure to command line tools like databases etc, anyway thanks, gives me a lot of food for thought to get this stuff down, cheers!

@@bluesdog88 NO worries, have been on a bit of a journey recently myself, gone from full java backend monolithic system programmer to AWS cloud serverless in the last year or so. Virtual desktops can live in the cloud too, not just a local network, Amazon Workspaces is one example. Haven't used it, but looking at setting something up on my homelab to do something similar when I'm away from work/home. Facebook is a web application in that you don't store anything locally, all of your interactions are via a browser (or a phone app, but honestly mostly that's just a thin veneer over a web component). They're different from a traditional web page in that they are dynamic and you don't really go from page to page but open dialogs and transition states - react is the language used for their UI, and I've been using that at work also. And databases aren't command line tools anymore. Things like RDS and DynamoDB in AWS are cloud based DB's where you don't even need to know the host, the system, just the schema you want to load and how to poke at it. Takes about 10 mins to set up and get some lambda's behind an api gateway poking at it if you want to prototype things, all through a fairly convenient web form configuration (assuming you're down with that lingo, might take longer if you have to learn what lambda, api gw and dynamo are ;)

@@morosis82 Nice! The whole realm of IT is so vast it's easy to get overwhelmed sometimes ;)

Yay!

Super popular ;)

BNWS, everyone knows BNWS ;>)