3 ms·
* how is this different than deploying your own (micro)services on different hosts where you control the code? * if you don't control the service running the w
by Juliate 10y ago
* how is this different than deploying your own (micro)services on different hosts where you control the code?
* if you don't control the service running the web task, how do you trust the returned result to be the actual execution of the code you submitted?
- blaisio 10y ago1. Well obviously it's different in many ways. For example, it's easier to setup integrations, especially for non-developers. Even if everything is self hosted and internal it's nice to not need to modify a services code for every single use case. 2. I mean you can't I guess? But I'm not sure why that's a concern since it'd be part of a contract/SLA. If you don't trust them to follow the contract, then why are you even talking to them? Just host your own service that you do trust.
- Juliate 10y ago1 & 2. Got it. Thanks. It makes sense to extend a platform, from the user's perspective, for her own usage, right. That's what was not obvious to me, at all (speaking from a platform developer POV). Seen as that, yes, that looks like a very nice thing to have.