Questions about Direct Access Feature

[dplewis]

Enables direct access to parse-server, when using the JS SDK from the current node runtime.

All API calls from the JS-SDK are router through route matching (but /functions/:functionName)

Enable that feature by setting PARSE_SERVER_ENABLE_EXPERIMENTAL_DIRECT_ACCESS=1

So if I understand this correctly:

client -> request to Cloud Code Function (Server) -> calling object.save() in Cloud Code -> send http request to Server.

Enabling this feature

client -> request to Cloud Code Function (Server) -> calling object.save() in Cloud Code -> no additional request sent because both JS SDK and Server are on the same node runtime

Enabling this feature would make requests faster since there is one less request, should this be mainstreamed?

Should there be tests run against this?

Add to parse-server config definitions?

We should add documentation to make more users aware of this feature

[acinader]

or we should just turn it on?

I've never tested it which i'll try and do real soon now....

I don't know what potential issue if any it may cause. if there's not breaking change to it, then we should just turn it on. I think that @flovilmart wanted it out there to figure out if there was a breakage issue iircc ...

BUT, adding it to the definitions and testing would be good either way.

[flovilmart]

Most of the Test break with this feature on. There can be bad side effects due to the statefulness of the JS SDK.

[acinader]

In which case, @dplewis your initial suggestion is spot on.

[flovilmart]

I mean the whole test suite is broken when using this feature

_{Sent with GitHawk}

[dplewis]

I haven’t used it yet and don’t know the limitations but would love too. At least start testing against different routing matches and see how responses are handled

[flovilmart]

Simple thing is to turn it on for the test suite, and see what breaks. In an ideal world, all tests should pass as it warrants all cloud code / integration tests are OK.

_{Sent with GitHawk}

[dplewis]

It’s a great feature that is known by few. Definitely could use feedback. I’ll test it out shortly.

[mtrezza]

@dplewis or @davimacedo do you know what the state of this feature is?

It's feature flagged, merged into master but a lot of test cases still fail, so not safe for production, is that correct?

[mman]

@mtrezza i have it in production for more than a year, since 2.8 IIRC, if I understand it correctly requests from cloud code go directly to the instance handling the original request as opposed going outside to the load balancer doing TLS and back inside again. Not checked the failing tests though...

[mtrezza]

@mman Thanks. Do you recall the reason why you took it into production? Did you do a performance comparison?

_{Sent with GitHawk}