aws-lambda-dotnet
foundation
aws-lambda-dotnet | foundation | |
---|---|---|
10 | 212 | |
1,540 | 86 | |
1.1% | - | |
9.0 | 0.0 | |
4 days ago | 5 months ago | |
C# | ||
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
aws-lambda-dotnet
-
Cloudwatch Alarm Lambda error triggering, but I can't find the log error
I saw this issue: https://github.com/aws/aws-lambda-dotnet/issues/245
-
Migrating .NET Console App Cron from GitHub Action to AWS Lamda
Creating Lambda Project using Amazon.Lambda.Templates. I use Amazon.Lambda.Annotations because it will be similar to my previous console program, and we can use dependency injection.
-
Adopting the Lambda Annotations Framework
Hopefully, this post will have intrigued you enough to check out the new framework, and try converting some of your existing functions into what I think is a much more readable and easier to comprehend format. Also, the development team is always interested in feedback, which you can supply in the issues folder of their repo. You can also find the design document for the annotations in this issue.
- AWS Lambda for hosting asp.net core webapis?
-
Debugging .NET Lambdas similarly to RIE
I don't think it's exactly what you're looking for, but you could try out the LambdaTestTool https://github.com/aws/aws-lambda-dotnet/tree/master/Tools/LambdaTestTool
- Anyone running ASP.Net Core on AWS Lambda? Or dotnet on AWS Lambda in general !
-
Running a GraphQL API in .NET 6 on AWS Lambda
According to this GitHub issue we need to add and configure an additional package when running a custom runtime on ARM:
-
AWS hosting multiple api’s using hangfire or going serveless with Lambda
I'm assuming API's are REST APIs. Those sound like excellent use cases for running as Lambda functions. If the API's are an ASP .NET Core Web API project it is possible to deploy that to Lambda using the Amazon.Lambda.AspNetCoreServer, https://github.com/aws/aws-lambda-dotnet/tree/master/Libraries/src/Amazon.Lambda.AspNetCoreServer, NuGet package. That can be a quick way to get something working and then later choose to rearchitect to a smaller more micro services architecture if necessary.
-
Cloud Migration 101: Developer Edition
AWS provides a NuGet package (see Amazon.Lambda.AspNetCoreServer) that makes it easy to do this. It works pretty well, but instead of one copy of the API serving many clients you have many copies of the API each serving one client at a time. There are also limitations in areas like file upload and download (which vary depending upon whether this is being used with API Gateway or an Application Load Balancer).
- Voice your support for an AWS Lambda container base image for PowerShell ☁
foundation
-
Building Scalable GraphQL Microservices With Node.js and Docker: A Comprehensive Guide
GraphQL is a query language and runtime for APIs. It provides a flexible and efficient way for clients to request and retrieve specific data from a server using a single API endpoint.
-
Type-Safe Fetch with Next.js, Strapi, and OpenAPI
When you use technologies like GraphQL, it is trivial to derive TypeScript types. A GraphQL API is created by implementing a schema. Generating the TypeScript type definitions from this schema is simple, and you do not have to do any more work than just making the GraphQL API. This is one reason why I like GraphQL so much.
-
REST vs. GraphQL: A Detailed Comparison of API Architectures for Developers
REST and GraphQL have advantages, drawbacks, and use cases for different environments. REST is for simple logic and a more structured architecture, while GraphQL is for a more tailored response and flexible request.
-
Gatsby tutorial: Build a static site with a headless CMS
A Gatsby site uses Gatsby, which leverages React and GraphQL to create fast and optimized web experiences. Gatsby is often used for building static websites, progressive web apps (PWAs), and even full-blown dynamic web applications.
-
Rust GraphQL APIs for NodeJS Developers: Introduction
In my usual NodeJS tech stack, which includes GraphQL, NestJS, SQL (predominantly PostgreSQL with MikroORM), I encountered these limitations. To overcome them, I've developed a new stack utilizing Rust, which still offers some ease of development:
-
How to convert a TypeScript built-in enum to a GraphQL enum
At Woovi we are GraphQL lovers, hence we develop many helpers around this tool to bring a good developer experience.
-
How to Build & Deploy Scalable Microservices with NodeJS, TypeScript and Docker || A Comprehesive Guide
A query language for APIs that allows clients to request only the data they need. It provides a more flexible and efficient alternative to RESTful APIs. GraphQL provides a single endpoint for multiple data sources, making it efficient for clients to retrieve only the necessary information forexample if a Node.js microservice uses GraphQL, a client can send a query to request specific data, and the GraphQL service will fetch the required information from the underlying data sources and respond accordingly.
-
Embracing the Headless Channel in Xperience by Kentico
This approach is particularly beneficial for teams looking to enhance their digital presence without the need for extensive coding or software development. By leveraging the GraphQL API endpoint, developers can prepare and execute queries to retrieve the desired content. This makes the Headless Channel a valuable tool 🔨 for content managers and developers, offering ease of use and practicality.
-
Building a CRUD application with React, TypeScript, TypeORM, MySQL, GraphQL, and NodeJs | Part A
To know about Graphql and why it's being used head over to for more details, Now let's cut to the chase.
-
Supercharging Your App Development: Unleashing the Full Potential of React Native
GraphQL is an excellent choice for real-time data synchronization in React Native apps. By using GraphQL, you can retrieve precisely the data you need and receive updates in real-time, reducing network usage and providing a seamless user experience.
What are some alternatives?
serverless-offline - Emulate AWS λ and API Gateway locally when developing your Serverless project
MongoDB - The MongoDB Database
chalice - Python Serverless Microframework for AWS
Hasura - Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
GraphQL-in-DotNet-6-on-AWS-Lambda - The accompanying code to my dev.to article
reddit-clone-with-redwoodjs
fargate-game-servers - This repository contains an example solution on how to scale a fleet of game servers on AWS Fargate on Elastic Container Service and route players to game sessions using a Serverless backend. Game Server data is stored in ElastiCache Redis. All resources are deployed with Infrastructure as Code using CloudFormation, Serverless Application Model, Docker and bash/powershell scripts. By leveraging AWS Fargate for your game servers you don't need to manage the underlying virtual machines.
Apache Cassandra - Mirror of Apache Cassandra
demo-serverless-aspnetcore - ASP.Net Core 3.1 on AWS Lambda demo
React - The library for web and native user interfaces.
libcurl - A command line tool and library for transferring data with URL syntax, supporting DICT, FILE, FTP, FTPS, GOPHER, GOPHERS, HTTP, HTTPS, IMAP, IMAPS, LDAP, LDAPS, MQTT, POP3, POP3S, RTMP, RTMPS, RTSP, SCP, SFTP, SMB, SMBS, SMTP, SMTPS, TELNET, TFTP, WS and WSS. libcurl offers a myriad of powerful features
Materialize - Materialize, a CSS Framework based on Material Design