Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEAT] Merge Push, Email & SMS modules #23

Closed
kkopanidis opened this issue Feb 8, 2022 · 1 comment
Closed

[FEAT] Merge Push, Email & SMS modules #23

kkopanidis opened this issue Feb 8, 2022 · 1 comment
Labels
discussion enhancement New feature or request

Comments

@kkopanidis
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Currently conduit spins up multiple containers that don't really make sense to be separate, since they can't practically scale independently. Email, push and sms utilise different external providers for their operations, but they fulfil a common goal of outgoing operations with templates etc.

Describe the solution you'd like
I think it'd be best for these to be merged into a singular "communications" module, that handles all outgoing user communications with either channel. This will allow for even cool things like "reach the user by any mean necessary", and incorporate more channels ex. viber, whatsapp etc.

Additional context
This particular module merge doesn't have any scalability arguments i think, since basically their capacity dependes 80-90% to the external services and merging them shouldn't provide any significant benefits or drawbacks on that part. But, it'd definitely save up some ram and cpu in the deployments.

@kkopanidis kkopanidis added enhancement New feature or request discussion labels Feb 8, 2022
@kon14
Copy link
Contributor

kon14 commented Feb 9, 2022

This will allow for even cool things like "reach the user by any mean necessary", and incorporate more channels ex. viber, whatsapp etc.

Nice one, definitely a feature we'd be interested in supporting.

This is also going to affect URIs much like #22.

@ConduitPlatform ConduitPlatform locked and limited conversation to collaborators Apr 17, 2022
@kkopanidis kkopanidis converted this issue into discussion #122 Apr 17, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
discussion enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants