Want to master Clean Architecture? Go here: bit.ly/3PupkOJ Want to unlock Modular Monoliths? Go here: bit.ly/3SXlzSt Join a community of 1000+ .NET developers: www.patreon.com/milanjovanovic
If I'm not mistaken in the latest release of Aspire 9 the default service is applied automatically without the need to reference the service default project
I don't call a lot of external api's, our systems usually are called, or we call internal our internal api services. While hosting on our own servers/vps servers we have had very few issues whit availability when not using these resilience features. I know "It does not happen to me" is not perse a good reason, but I did notice that since we moved some services to the cloud we started really needing these features since "other" providers don't seem to offer "a stable solution" or an always available. This is being sold as "you can't rely on cloud services being available all the time". While when running our own servers it was not that hard to keep availability. And I know it also depends on the number of calls etc... but I feel this has become a "thing" with the advent of "could providers" Do you concur that availablility and resilience has become more needed/necessary since moving to cloud hosting?
Not cloud hosting per se, but the advent of microservices and complex distributed systems. When hosting a couple of APIs on our own, under meaningful load, we won't see errors too often. But things change when you're dealing with large scale apps. The best practices outlined here are mostly from MSFT teams that operate on global scale with millions of concurrent users.
This new Aspire app. Can you make a video on how to use Aspire for multiple deployment environments and how to deploy to different envs with settings for each app for Development, Staging and Production for examples?
I think I reused code from an older video, where I was resolving the StockService (which is scoped) and just replace it with the typed client. By default, typed clients are transient so you can resolve them in singletones.
Hello, I have a question about WebSockets. I’ve implemented it in my .NET project, and it’s working well locally. Now, I’m ready to push it to AWS Elastic Beanstalk since we already have the environment set up. Are there any specific configurations I need to adjust on Beanstalk to make sure WebSocket connections work smoothly in production? Thanks.
Want to master Clean Architecture? Go here: bit.ly/3PupkOJ
Want to unlock Modular Monoliths? Go here: bit.ly/3SXlzSt
Join a community of 1000+ .NET developers: www.patreon.com/milanjovanovic
Brilliant, love your videos, they are to the point and help me a lot. Thank you.
Glad to help!
Awesome, keep it up bro🔥🔥🔥
Thanks! Will do!
Thank you, great lesson as always
My pleasure!
Cool stuff!
Thanks
Great video!
Thanks!
If I'm not mistaken in the latest release of Aspire 9 the default service is applied automatically without the need to reference the service default project
I've had some issues with the V9 SDK, so just waiting for the .NET 9 release to test it out
Aspire 9 is compatible with .net 8
Awesome 😲
Thanks!
Good content.
Appreciated
Nice video. Is there a way to get the source code in order to improve it ?
Thanks
Here: www.patreon.com/milanjovanovic
I don't call a lot of external api's, our systems usually are called, or we call internal our internal api services. While hosting on our own servers/vps servers we have had very few issues whit availability when not using these resilience features. I know "It does not happen to me" is not perse a good reason, but I did notice that since we moved some services to the cloud we started really needing these features since "other" providers don't seem to offer "a stable solution" or an always available. This is being sold as "you can't rely on cloud services being available all the time". While when running our own servers it was not that hard to keep availability. And I know it also depends on the number of calls etc... but I feel this has become a "thing" with the advent of "could providers"
Do you concur that availablility and resilience has become more needed/necessary since moving to cloud hosting?
Not cloud hosting per se, but the advent of microservices and complex distributed systems. When hosting a couple of APIs on our own, under meaningful load, we won't see errors too often. But things change when you're dealing with large scale apps. The best practices outlined here are mostly from MSFT teams that operate on global scale with millions of concurrent users.
This new Aspire app. Can you make a video on how to use Aspire for multiple deployment environments and how to deploy to different envs with settings for each app for Development, Staging and Production for examples?
Doing a deployment video for Aspire very soon. Will tackle different ENVs later
@MilanJovanovicTech that's awesome can you do one for on premis dev ops and one for azure in the cloud please?
I'm sorry if you already explained this (or later in the video), but why do you manually resolved an instance of the StocksApiClient ?
I think I reused code from an older video, where I was resolving the StockService (which is scoped) and just replace it with the typed client. By default, typed clients are transient so you can resolve them in singletones.
I believe with Aspire, that's all built in automatically?
Yes, yes it is 👌
@@MilanJovanovicTech cool
Hello, I have a question about WebSockets. I’ve implemented it in my .NET project, and it’s working well locally. Now, I’m ready to push it to AWS Elastic Beanstalk since we already have the environment set up. Are there any specific configurations I need to adjust on Beanstalk to make sure WebSocket connections work smoothly in production? Thanks.
I think you'll need to make some config adjustments to your load balancer. Let me see if I can find some useful docs.
@@MilanJovanovicTech
Thank you wating your reply
Part 1 th-cam.com/video/DTfqqe7NgMQ/w-d-xo.html
Is it?