Although Lambda Layers can be used to push stale package references into externalized layers and let Lambda use these from the layers, we might also want to have our Custom Class libraries which might contain business logic to work in the same way, so that they could be reused in other lambda functions as well. For this, we make use of Nuget packages to pack and store our libraries. Learn how to implement this and deploy our libraries in Layers.
AWS Lambda Layers were introduced on top of the Lambda deployment stack for cloud applications. They are added to provide support for reusable components and in an attempt to reduce the coldstart issues of the Lambda services.
In this article, let's talk about another such simple Flow - which can be used for user authentication. It is called as the Resource Owner Password Credentials Grant (ROPC) flow.
In this article, let's look at Implementing ClientCredentials auth flow, which is one of the basic auth flows used for securing and granting access to API resources to clients which possess an access_token issued by the configured TokenServer safeguarding the API.
In this article, let's get to know in detail about how Token servers work and how we create and secure our AspNetCore APIs with IdentityServer4.
In this article, let's look at how the UserPool created is used in an actual application perspective - how we can secure an application using UserPool created in AWS Cognito. The expectation is that when a user authenticated in AWS Cognito and obtained a Token tries to access the API using the Token, the API must be able to validate the Token for its authenticity and let the user pass or deny access.
CQRS stands for Command Query Responsibility Segregation. It is an Architectural Design Pattern that advocates segregating or grouping the methods based on how they impact the data and design them separately according to their requirements. In ASP.NET Core, we can implement the Mediator pattern by using MediatR, an open source library which provides the template for a simple Mediator.
Logging, is perhaps one of the most essential components in an application. An application once moved to production still needs maintenance and monitoring for any uncovered bugs and runtime errors and a good logging mechanism can be a lot helpful in understanding the issues better. Let's discuss one such scenarios which we face in real-world while building a robust logging system for an API : Logging an overall request-response cycle.
Let's look at how we can leverage the IFormFile type in developing a simple Form that submits both text and Files to a backend API and how the submitted data can be handled in AspNetCore. We'll look at two distinct methods of submitting Form - the MVC submit way and the jQuery ajax way.
In this article let's look at how we can create a simple form and POST data to an AspNetCore API via jQuery. To style this application, we'll use Bootstrap, which is a popular CSS framework for desiging responsive web pages. We'll also make use of Tag Helpers, which make binding the back-end controller attributes - such as route urls in the views easy.