Our great sponsors
-
aws-lambda-dotnet
Libraries, samples and tools to help .NET Core developers develop AWS Lambda functions.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
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
-
aws-lambda-java-libs
Official mirror for interface definitions and helper classes for Java code running on the AWS Lambda platform.
According to this GitHub issue we need to add and configure an additional package when running a custom runtime on ARM:
The way I prefer to deploy simple Lambdas is by using the Serverless framework.
That's it! We have now deployed a minimal serverless GraphQL API in .NET 6 on AWS Lambda. Full working code is available at GitHub.
GraphQL has quickly become my primary choice when it comes to building most kinds of APIs for a number of reasons:
Verify using curl: curl "http://localhost:/graphql?query=%7B+sysInfo+%7D"
AWS Lambda is usually marketed (and used) as a way to run small isolated functions. Usually with 10 line Node.js examples. But it is so much more! I would argue it is the quickest and most flexible way to run any kind of API.