This is a Discussion

Description

Once you build a large micro-service infrastructure communication between those services can become complicated. You might not want every service to be able to talk to every other service, you might want to invoke specific services whenever one finishes or simply send out an event and have other services react to that event automatically and asynchronously.

Communication issues to solve

Following are a couple of use cases we think need to be solved by the Serverless Framework. To support them the Framework will automatically create resources in your AWS account and connect the functions to those resources with the help of our upcoming SDK. E.g. when you configure a service to be able to raise an event we will create a SNS topic that other services can easily subscribe to through a simple serverless syntax.

• Send out Async events through code and have other services subscribe to these events and run functions
• Listen to a function starting or finishing (including success/failure) and run a follow up function
  • e.g. after the SaveUser function has finished successfully you want to send out an email
• Call a another function synchronously from your code and do something with the result
• Call another function async from your code

Another part of this service communication in the future will be communication across different providers.

Similar or dependent issues:

• Error when using sls-invoke local with docker image #12345