More should be written/discussed about the serverless application repository. It has never been of particular interest to me, and I find @dzimine very convincing in his explanation of why it likely will never be: functions aren’t actually reusable in the way libraries/APIs are.
I'd love to hear more. The public func repository has been tried soo many times both pre and post FaaS. Part of me wants to think one day it will happen, the other part thinks it never will.
-
-
My take on describing why it will never take off: leveraging others’ code is nothing without developers actively maintaining it. We have two models that work for this: open source library (GitHub, issues, tests, samples, package mgmt) and API-based service (docs)
-
In other words, everything that works looks like microservices: an encapsulated team with clear and clean rules/docs on usage and ongoing development velocity to address changing worlds/software.
-
For sufficiently small enough code (e.g., snippets), stack overflow works (since you copy/paste). But you likely don’t want to run small code as a separate lambda, you want to incorporate. And as the code gets longer, you need it to be maintained.
-
I think you can extend it beyond small, copy/paste-able code. Most code on GitHub consists of libraries that I pull into my app. But it's not clear why calling a remote function with that library code is better than just npm install / pip install. Why add the network call?
-
You can deliver API gateway based systems in SAR and it's effectively open source too so there's nothing stopping you building on top of it. Usefulness is in building reusable components rather than full blown applications. Can also build ingestion tools so nobody needs an sdk
-
My point is that reusable systems without supporting developers, docs, samples are not useful.
-
Labeling something without supporting docs and and samples as “reusable” is a misnomer, not just unusable.
-
Agreed. Opportunity is there to do it right.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.