This is a tricky one. I'm not sure if opening up Slack to all customers is the best approach, as that might create more chaos than structure. And the Chatter groups seem more focused on internal collaboration. I'm leaning towards the Customer Service template, but I'll need to think it through a bit more.
This is a tricky one. I'm not entirely sure about the correct answer, but I'll try to eliminate the options that are clearly consequences of not having a will.
Okay, I think I've got this. The key is to use the `ds.as_mount()` method to pass the dataset as an argument to the script. That way, the data will be streamed directly from the source.
I think the Legacy Wrapper pattern could be a good way to go. It might help with the loose coupling aspect, but I'm a bit unclear on the implementation details and how it interacts with the shared database.
upvoted 0 times
...
Log in to Pass4Success
Sign in:
Report Comment
Is the comment made by USERNAME spam or abusive?
Commenting
In order to participate in the comments you need to be logged-in.
You can sign-up or
login
Moon
4 months agoKristeen
5 months agoWynell
5 months agoCarmela
5 months agoEric
5 months agoShonda
5 months agoShalon
5 months agoMarci
5 months agoAnnett
5 months agoCiara
6 months agoShad
6 months agoIdella
6 months agoLeota
6 months ago