In this post we shall see how you can build Continuous Integration Pipelines for your PlantUML diagrams. If you are into any sort of designing or development, you most probably know about PlantUML which is one of the best UML Designing tool. The main power lies in the fact that it provides Diagram as a Code for all types of design and diagramming needs. This “As-A-Code” culture is lot prominent these days, due to multiple reason, primarily being ease of use and management with Infra and devops.
But there is a problem as well. The diagrams needs to be manually updated, since the source is NOT a diagram, but a code. But what if you can have a pipeline that automatically generates all your images from the diagram sources. A little tricky but we shall see in this post how you can do so.
EF Core is one of the most powerful ORM platform (called platform for a reason) that provide wonderful abstractions and means to call and connect databases with the application. With years of practice and experience I have seen multiple developers doing the same mistakes again and again. I am planning and trying up this course in a hope to cover all those and provide a most comprehensive and detailed course that covers the targets from industry production ready and enterprise applications along with some less-documented features in EF Core which are very handy.
The detailed course shall be available over youtube and and source code would be available at Github.
So this would be new set blog post and my videos on LetsDoCoding. In this particular post we shall be discussing shortly a very simplistic and bare minimum Solution Design for URL Expander and Shortner Service, very similar to Bit.Ly. I have asked this question in quite a few Interviews I have taken in the Initial interview rounds and this post covers all the aspects.
Cloud based solution design.
Deployment Strategy and replication for better UX
Services and Contracts Design
Database and ER Model Design.
You can refer the video on youtube for complete details, but we shall be discussing some pointers in this post. This question is targeted for interview questions and discussions on system and solution design. So Lets Begin…
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.