Managed Identities are cloud based Identities which are offered in SaaS model where you delegate all the Identity Management including credentials storage, security and a lot of other related aspects to cloud Provider. Cognito from AWS and Active Directory (AAD and AAD B2C) from Azure are prominent cloud provider followed by Auth0.
Security is the biggest risk of connected world and once the site get compromised, hackers try to target to capture user data to get personal private data of users including passwords and attempt privileged access to site. Kicking out the core security part (Identity) from the application, itself removes a lot of surface area that is open for attacks. Also, with this your application moves to more connected and standardized approach since this opens a whole world of Single Sign On and connected world.
Around four years ago when .Net Core was in its early stages, I wrote back a Configuration provider for .net core 1.x. This has been a long time. The package did picked up very well and there were multiple downloads and a few queries as well. Many people would never know that .net core started with json project files. But since then a lot changed and my package went obsolete.
A few days back got some time and bandwidth and wised to revise the package. This would not only update the latest package but would also help me understand what changes have been done as in framework as a whole. So, my fellow countrymen let me present you the MongoDbConfiguration Provider for .net Core (😁) /s
Read on further to get the details as I explain the “simple” steps to write a custom configuration provider for .net core 3.1.
What would happen if you need to implement two interfaces with same member names. How would you do it. This is actually an interesting question and while this seems simpler, its not actually in implementation as there are a few hidden tricks. In this video we try to cover the basic fundamentals of the Explicit Interface Implementation and also do a quick hands on how to do it.
In the modern everything is evolving very rapidly, and so is Web and standards. From SOAP to REST, standards have been shifting, but they seemed to have been stuck for a while while with the REST. Well, now again the ball is getting rolling with gRPC, the latest kid in the town. Not only it has all the latest and cool gadgets in its pocket, it is fast, really fast secure and can solve some of the typical problems that have been with since ailing the normal REST communications.
But.. There is always a but.. But, there are always two side of coin with all flexibility, there are some challenges. This is first part of the 3 article series on gRPC, what – why and how series including the handon demo. So without wasting time, lets dive in. This is a bit theoretical shit. For quick codies, you can jump to implementation in next article.
I have been struggling for some time to manage multiple GIT repos. Like me there could be multiple cases you need to manage and pull multiple GIT repos. This is the tools which can easily manage and do that. Just define it once and good to go always. Personally for me, its like a daily routine. In the morning, connect and pull all and get all repos at once, without firing pull in cd(ing) each repo and issuing git pull.
Some time back as I remember, AWS was the biggest (and probably only leading) cloud provider. But with each gone day, Azure is increasing its product base in competition to AWS. Many of these products are inspired (don’t read as copy) originally from AWS. Also, in most of the Azure products, you will find a small asterisk hidden somewhere and cost is something which is more or less equal or expensive.
Despite all these facts, slowly and gradually with a pace approaching AWS and could takeover in a few years. Well, this seems to be a little too much from a developer without understanding of deeper market dynamics, but rather this is from the heart and trouble ship that I have faced, and probably many of the other developers facing. Alert, this post contains no code, but theory.