@batmany13
Pinned post
www.linkedin.com The Pursuit of Impact An engineering leader’s journey to build thriving teams at Netflix Watch the presentation that goes with this blog! People leaders should pursue the virtuous reinforcement of designing, hiring,... MCP is not an integration strategy. We raised $15M from Bessemer to prove it.View quoted post on X
If you are building an enterprise agent that needs to connect with your customers’ critical systems, simply integrating with the Salesforce MCP isn’t going to cut it.
1. MCP isn’t going to help you backfill millions of transactions from your customer’s NetSuite, or millions of accounts from your customer’s HubSpot. For that, you need robust sync infrastructure.
2. Enterprise customers do not use tools out-of-the-box. Their CRMs, ERPs, and all the legacy systems of record have custom objects, custom fields, and bespoke workflows. MCP will not help you navigate that complexity.
3. MCP is built for real-time querying. Some work is better done async, especially when you are dealing with strict rate limits that many SaaS products have. You need async workloads and smart retry logic.
Ampersand is the integration infrastructure for deeply connecting with your customers’ systems of record. Because the SaaSpocalypse didn’t happen. The world still depends on CRMs, ERPs, HRISs, and ITSMs.
@NetflixEng @batmany13 I’d love to hear from you folks, if there’s anything you can share, maybe around the choice of building it in-house vs. existing implementations - I get the JVM compatibility; how about performances, did you realise other tools weren’t up to the task?View quoted post on X
#QConPlus talk on how Netflix scales its API layer via GraphQL Federation is now available:
buff.ly/3m7n0ffView quoted post on X
