5 ms·

Serverless Components keep track of all the resources it creates/updates and their properties locally in the .serverless directory. It also keeps it synced with

Serverless Components keep track of all the resources it creates/updates and their properties locally in the .serverless directory. It also keeps it synced with the actual state of the resource on the provider (in case you've changed them in the console for example) So if you change the configuration, the component will be able to figure things out.

scarface74 7y ago
Does Serverless handle all of the AWS resource types that you may need for your lambda?
- eahefnawy 7y ago
  You can write your own component that handles whatever service you need and share it with the community. The more components that are built, the easier it'll be to write higher level components that use those. As of today, those are the available components: https://github.com/serverless-components https://github.com/serverless-components
  - ac360 7y ago
    @scarface74 Let us know what you need. We have about a dozen more coming out within the next week.
    - scarface74 7y ago
      Most of the lambda related things I do are backend ETL and message processing. Is Serverless just for API use cases or does it support other event triggers like SNS and SQS or one of the patterns we use is S3 Event -> SNS -> SQS -> lambda and all of the related permissions and subscriptions. But then again, isn’t the whole purpose of using Serverless instead of SAM to be cloud vendor neutral? Once you add AWS specific resources doesn’t that go against the whole ideal of using Serverless?
    - ac360 7y ago
      @scarface74 We have three projects. Here's how they may be helpful to you: 1) Serverless Framework The Serverless Framework enables you to provision serverless applications in a Function + Events pattern. Using this, you can accomplish the patterns you're describing, and hundreds of thousands of people are doing this already with the Framework. https://github.com/serverless/serverless https://github.com/serverless/serverless 2) Serverless Framework Enterprise SFE works with the Serverless Framework to give you more than development and deployment convenience. SFE focuses on other phases of the serverless application lifecycle, like monitoring, alerting, security, collaboration, secrets and much more. It's a powerful solution for teams and orgs investing more in serverless application development. https://serverless.com/enterprise https://serverless.com/enterprise 3) Serverless Components This is a new take on serverless application development. We've learned the serverless community and teams are looking for ways to deploy and share composable architectural pieces (features, use-cases), more than infra. So we're building a new type of provisioning system to enable this. The Realtime Application Component is an example of this. https://github.com/serverless-components/RealtimeApp https://github.com/serverless-components/RealtimeApp
  - scarface74 7y ago
    I’ll be the first to admit that most of the missing resources would be useless for lambda. There are a few missing ones that might matter. https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-template-resource-type-ref.html https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGui...

scarface74 7y ago

Does Serverless handle all of the AWS resource types that you may need for your lambda?

eahefnawy 7y ago
You can write your own component that handles whatever service you need and share it with the community. The more components that are built, the easier it'll be to write higher level components that use those. As of today, those are the available components: https://github.com/serverless-components https://github.com/serverless-components
- ac360 7y ago
  @scarface74 Let us know what you need. We have about a dozen more coming out within the next week.
  - scarface74 7y ago
    Most of the lambda related things I do are backend ETL and message processing. Is Serverless just for API use cases or does it support other event triggers like SNS and SQS or one of the patterns we use is S3 Event -> SNS -> SQS -> lambda and all of the related permissions and subscriptions. But then again, isn’t the whole purpose of using Serverless instead of SAM to be cloud vendor neutral? Once you add AWS specific resources doesn’t that go against the whole ideal of using Serverless?
  - ac360 7y ago
    @scarface74 We have three projects. Here's how they may be helpful to you: 1) Serverless Framework The Serverless Framework enables you to provision serverless applications in a Function + Events pattern. Using this, you can accomplish the patterns you're describing, and hundreds of thousands of people are doing this already with the Framework. https://github.com/serverless/serverless https://github.com/serverless/serverless 2) Serverless Framework Enterprise SFE works with the Serverless Framework to give you more than development and deployment convenience. SFE focuses on other phases of the serverless application lifecycle, like monitoring, alerting, security, collaboration, secrets and much more. It's a powerful solution for teams and orgs investing more in serverless application development. https://serverless.com/enterprise https://serverless.com/enterprise 3) Serverless Components This is a new take on serverless application development. We've learned the serverless community and teams are looking for ways to deploy and share composable architectural pieces (features, use-cases), more than infra. So we're building a new type of provisioning system to enable this. The Realtime Application Component is an example of this. https://github.com/serverless-components/RealtimeApp https://github.com/serverless-components/RealtimeApp
- scarface74 7y ago
  I’ll be the first to admit that most of the missing resources would be useless for lambda. There are a few missing ones that might matter. https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-template-resource-type-ref.html https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGui...