Stream: dotnet
Topic: AWS Lambda and .NET API
Richard Kavanagh (Jan 23 2018 at 23:32):
Currently, AWS only allows for a maximum NETStandard.Library of 1.6.0. The NuGet has this built using version 1.6.1 which means you can not use the .NET libraries on AWS.
Does anyone know whether the .NET API actually needs to target that version of NETStandard.Library?
Brian Postlethwaite (Jan 24 2018 at 00:13):
I don't know the answer to that one. Does amazon have any timelines on newer support?
Brian Postlethwaite (Jan 24 2018 at 00:13):
(You could also build locally with that config and try the unit tests to see if its still cooking)
Peter Jordan (Jan 24 2018 at 03:15):
Does this offer any answers? https://awsinsider.net/articles/2018/01/17/lambda-net-core.aspx
Richard Kavanagh (Jan 24 2018 at 21:57):
Thank @Brian Postlethwaite and @Peter Jordan - I think I will need to try and do a build myself at some point. It does look like AWS now supports .NET Core 2 but it does not look like the NuGet does (yet).
Brian Postlethwaite (Jan 25 2018 at 19:09):
It should do, you need to create your project that uses it as netcore 2 first though. Haven't tried myself. Maybe we can take a look sat morn in New Orleans
Richard Kavanagh (Jan 26 2018 at 14:05):
I had a look - it's beyond my .NET skills
Ewout Kramer (Jan 28 2018 at 20:10):
Hi Richard, I actually build the .NET API against .NET Standard 1.0 and .NET Standard 1.3 - as far as I can see I have no dependency on anything higher than that - could this be caused by another external dependency?
Richard Kavanagh (Jan 29 2018 at 08:45):
Hi @Ewout Kramer thanks for responding. The issue seems to be that AWS Lambda only supports up to V1.6.0 of the NETStandardLibrary but the build required V1.6.1 or above. AWS jumps to v2 of .NETStandard after v1.6.0 - as far as I can see the .NET API is not available (as a NuGet) at v2 yet.
Richard Kavanagh (Feb 17 2018 at 17:37):
OK tried again and all seems fine now, as per @Peter Jordan comment - AWS now support .NET Core 2.0 for their Lambda service. So now have Alexa skills using FHIR courtesy of the .NET API.
Somnath (Apr 16 2018 at 08:34):
@Richard Kavanagh hi are you single instance of fhir client for every request in your application. actually I am facing memory issue with document of 70 MB.
Brian Postlethwaite (Apr 17 2018 at 22:27):
Is that just trying to process a single resource that is 70MB in size?
repeatedly?
Do you have a URL that we can test/profile against?
There are performance differences in using the streaming serializers vs the string read/write.
Last updated: Apr 12 2022 at 19:14 UTC
