daugaard47's avatar

Use Salesforce as a back-end?

I'm wanting to know if anyone here has ever used Salesforce as a back-end?

Quick Backstory:

I've created a nice data-driven website using Laravel with Nova, but work is requesting to explore the possibility of using Salesforce as a backend.

I want to know if anyone has been tasked with this. If so, what are the Pros & Cons? What issues might come into play?

I know there are a couple packages for Laravel to help with this if I wanted to stick with Laravel, but I would be willing to use another framework like Vue or React if need. I'm having a horrible time trying to find any documentation on this.

The way I see it there are two options:

  1. Keep the Laravel + Nova flow and push all data to MySql & Salesforce via the SF API on all Post Requests. (Manage/Sync two databases, Laravel and Salesforce.)

  2. Dump Laravel and Nova, Take all my current data, import to Salesforce, Map the fields, create the relationships and use the Salesforce API to Get/Post future data on the front-end. (Only manage Salesforce and a front-end)

Any help on this subject would be appreciated.

0 likes
4 replies
denisromanenko's avatar

Don't think that you should dump your work if it's works for you now.

I believe that if you move your workflow to Salesforce, at some time point you will start suffer from some restrictions and not enough flexibility, like it always happen with pre-tuned-for-80%-tasks instruments.

Also I don't think that it will be good to have two DBs, which are being processed by different tools. You will run into data inconsistency very soon, Master-Master DBs it's a fairytale.

What type of tasks you want to deal with salesforce?

binduguleria's avatar

Have you been able to resolve this issue?

I have to use the Laravel-Vuejs platform to perform some kind of CRUD operations on Salesforce using rest-api.

Can you suggest any best package for the same?

Please or to participate in this conversation.