Prediction: Serverless Applications Repository's new Nested App feature will be one of the most important launches of 2018 for AWS #serverless.https://twitter.com/AWSreInvent/status/1068201190972768256 …
Show this thread
-
Wouldn’t that move discovery off SAR though? (To the extent one didn’t want to use unsupported acquisition)?
Seems to me like a big value of SAR is an *internal* library of microapps. As your app/team gets bigger, decreases duplication of non-business-logic code - i.e. glue code for AWS primitives. As AWS rolls out native support (e.g. SQS as event source for Lambda), refactor to remove
-
-
Absolutely, private consumption is also very important and beneficial.
@JoeEmison is talking more about the public/OSS side - I'm sure@salman_paracha (PM) would love to hear your input on support model and any other feedback you have. -
For me to believe in SAR as a useful marketplace of services, I would expect to see: 1. Great documentation for all apps (like as good as Twilio) 2. Ability to communicate with authors easily (maybe specific public forums, also ticketing) 3. Ability to pay per use/support
- 2 more replies
New conversation -
-
-
But if it’s your code, wouldn’t it be better in your repository and deployed as part of regular CI/CD? I don’t get where it makes sense to have it in SAR if it’s your bespoke code.
-
Nested Apps in SAM makes it easy to compose and reuse applications, including versioning support from SAR. Allows you to draw from both public and private/internal apps.
- 2 more replies
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.