You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
We will be integrating with potentially multiple data sources (Mongo or a mock API for automated testing and dev work), while integrating with Salesforce for production. Currently, we have the retrieval of these resources directly embedded within the endpoints (i.e. the request to our database and that business logic happens within our backend). However, it would be ideal if that logic is handled through an external source, such that we can call getAllResources and the logic would be handled depending on what environment variable is set.
Describe the solution you'd like
A clear and concise description of what you want to happen.
There's a few ways we can architect this to ease our transition to using Salesforce in production. One way we might handle this would be through a small library we create within our backend that we can call into directly as part of our route handler for, say, GET /resources/. I envision us having an environment variable keeping track of the two use-cases: salesforce backend and our custom (Mongo) backend, and then have the library handle this logic. We essentially want to build an API for our backend API to consume (API galore!) so all the logic is abstracted.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
We will be integrating with potentially multiple data sources (Mongo or a mock API for automated testing and dev work), while integrating with Salesforce for production. Currently, we have the retrieval of these resources directly embedded within the endpoints (i.e. the request to our database and that business logic happens within our backend). However, it would be ideal if that logic is handled through an external source, such that we can call
getAllResources
and the logic would be handled depending on what environment variable is set.Describe the solution you'd like
A clear and concise description of what you want to happen.
There's a few ways we can architect this to ease our transition to using Salesforce in production. One way we might handle this would be through a small library we create within our backend that we can call into directly as part of our route handler for, say,
GET /resources/
. I envision us having an environment variable keeping track of the two use-cases: salesforce backend and our custom (Mongo) backend, and then have the library handle this logic. We essentially want to build an API for our backend API to consume (API galore!) so all the logic is abstracted.The text was updated successfully, but these errors were encountered: