dotnet6-openapi
aws-lambda-runtimes-p
| dotnet6-openapi | aws-lambda-runtimes-p | |
|---|---|---|
| 4 | 2 | |
| 38 | - | |
| - | - | |
| 0.0 | - | |
| over 2 years ago | - | |
| TypeScript | ||
| 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.
dotnet6-openapi
-
Is it a bad idea to build a marketplace app using .Net core?
.NET Web API has great tooling for generating OpenAPI on build. Once you have this, you can easily generate TypeScript bindings for your front-end. See also: https://github.com/CharlieDigital/dotnet6-openapi
-
The Case for C# and .NET
This will scaffold a project which is more or less the exact same as Flask, Express, or any other "easy" framework.
OpenAPI output is built-in, but tooling for development does require a bit of knowledge (agree that Microsoft would benefit from making this work out of the box).
A small repo here showing how to connect OpenAPI and front-end TypeScript client generation: https://github.com/CharlieDigital/dotnet6-openapi
-
Im confused by different types of ASP.NET design patterns.
I have one example that shows how to do this with Vue and Svelte: https://github.com/CharlieDigital/dotnet6-openapi
-
Learn to make a web app with ASP NET Core and Vue?
A lot of the work I've done is closed source, but I do have a simple template here that is a typical starting point: https://github.com/CharlieDigital/dotnet6-openapi
aws-lambda-runtimes-p
- The Case for C# and .NET
-
AWS Lambda Cold Start Times
> NodeJs is the slowest runtime, after some time it becomes better(JIT?) but still is not good enough. In addition, we see the NodeJS has the worst maximum duration.
The conclusion drawn about NodeJS performance is flawed due to a quirk of the default settings in the AWS SDK for JS compared to other languages. By default, it opens and closes a TCP connection for each request. That overhead can be greater than the time actually needed to interact with DDB.
I submitted a pull request to fix that configuration[0]. I expect the performance of NodeJS warm starts to look quite a bit better after that.
[0]: https://github.com/Aleksandr-Filichkin/aws-lambda-runtimes-p...
What are some alternatives?
Fable.Remoting - Type-safe communication layer (RPC-style) for F# featuring Fable and .NET Apps
flyctl - Command line tools for fly.io services
dn6-mongo-react-valtio - A fully featured sample .NET 6 Web API with MongoDB, React, and Valtio. Set up for Google Cloud Run for the back-end with a Dockerfile.
piku - The tiniest PaaS you've ever seen. Piku allows you to do git push deployments to your own servers.
BaGet - A lightweight NuGet and symbol server
ionide-vscode-fsharp - VS Code plugin for F# development
aws-lambda-runtimes-performance - AWS Lambda Performance comparison
docs - This repository contains .NET Documentation.
apollo-client - :rocket: A fully-featured, production ready caching GraphQL client for every UI framework and GraphQL server.
tonehub - Provides an API for your personal collection of music, audio books and podcasts