Get in touch if you want to expand to NetSuite. We can have a chat...
Launch HN: Bracket (YC W22) – Two-Way Sync Between Salesforce and Postgres
51–60 of 82 posts
Re: Launch HN: Bracket (YC W22) – Two-Way Sync Between Salesforce and Postgres
#52Neat. I once wrote a Salesforce to Oracle sync app. I think the goal was to bulk pull data out of Salesforce for processing in Oracle to avoid Salesforce API costs. This was years ago. It was a fun and aggravating project.
Sounds similar to the use cases we're seeing, where it's not only easier to process/build on Postgres, but also saves you on the Salesforce API.
Re: Launch HN: Bracket (YC W22) – Two-Way Sync Between Salesforce and Postgres
#53Earlier quoted context omitted.
Yeah, so far, we’ve found that this combination of the three APIs is a happy medium between reliability, simplicity, and API limit consciousness.
I'm curious what's the biggest table you've tested on? Things start to get really interesting in Salesforce when your object has a million rows.
Re: Launch HN: Bracket (YC W22) – Two-Way Sync Between Salesforce and Postgres
#54Earlier quoted context omitted.
Agreed that many technical founders build on the pain points they've experienced themselves. I'm curious your take on why the managed services approach is hard to scale? IMO, the reason many YC companies struggle with enterprise sales is because it's generally much harder than PLG, with long sales cycles and delayed feedback loops. It was definitely a learning curve for us!
(opinions as ex-AWS GTM specialist for AI) An underrated challenge with enterprise sales is often that customers often misguidedly believe that 1) they can build it themselves, 2) they are worried about your companies ability to "scale" to their needs, and/or 3) the customer wants to "own" that responsibility for personal/political/career reasons. Sales is hard for everyone including Azure, AWS, etc, just gotta keep…
Re: Launch HN: Bracket (YC W22) – Two-Way Sync Between Salesforce and Postgres
#55Even if this only accomplished one-way directional sync with backup and disaster recovery capabilities, it'd probably find a 10x wider audience.
Thanks for the comment - are you saying that one-way sync has a 10x wider audience than two-way syncs?
If so, then Heroku connect probably does need an alternative.
A business user (non-technical 10x audience) just wants to sleep at night knowing their daily backup was successful and they have recovery capabilities on-demand.
There are unicorn scale companies in this space (such as https://www.owndata.com/). And Salesforce is getting back into the backup game.
Re: Launch HN: Bracket (YC W22) – Two-Way Sync Between Salesforce and Postgres
#56Neat! How specific is your solution to Postgres? Could it be ported to another db engine? (And, how are conflicts resolved? In a huge system with millions of records coming from everywhere it can fast become nightmarish?)
Re: Launch HN: Bracket (YC W22) – Two-Way Sync Between Salesforce and Postgres
#57Neat! How specific is your solution to Postgres? Could it be ported to another db engine? (And, how are conflicts resolved? In a huge system with millions of records coming from everywhere it can fast become nightmarish?)
> How specific is your solution to Postgres? Could it be ported to another db engine? Our polling approach is relatively database-agnostic. We just need to handle each DB's quirks with our transformers (e.g. dealing with MySQL's lack of BOOL field types). Streaming is currently Postgres-specific. We're planning on rolling out support for MySQL next, after we've finished our Hubspot integration. Do you have a specific…
This is a very fancy way of saying that you just drop conflict and pretend they didn't happen. Syncing databases is very, very tricky. Conflicts are a big part of the trickiness.
Re: Launch HN: Bracket (YC W22) – Two-Way Sync Between Salesforce and Postgres
#58Earlier quoted context omitted.
> How specific is your solution to Postgres? Could it be ported to another db engine? Our polling approach is relatively database-agnostic. We just need to handle each DB's quirks with our transformers (e.g. dealing with MySQL's lack of BOOL field types). Streaming is currently Postgres-specific. We're planning on rolling out support for MySQL next, after we've finished our Hubspot integration. Do you have a specific…
> The primary source wins any merge conflicts that happen within a sync period. This is a very fancy way of saying that you just drop conflict and pretend they didn't happen. Syncing databases is very, very tricky. Conflicts are a big part of the trickiness.
Re: Launch HN: Bracket (YC W22) – Two-Way Sync Between Salesforce and Postgres
#59Salesforce reps don't even know what Heroku Connect is. I couldn't get someone to sell it to me! I think the idea is great, glad to see someone picking it up.
Re: Launch HN: Bracket (YC W22) – Two-Way Sync Between Salesforce and Postgres
#601. Do you have any plans to release an API rather than utilizing a webapp for defining the sync? 2. Does your Salesforce integration support syncing metadata, including custom metadata? 3. Do you have data on the impact Bracket has on platform events and other Salesforce limits? 4. Can you share any information on pricing?
Thanks!