# Learning Palantir Foundry 🚀 "How do we connect to an on-prem Oracle or SAP in a closed network without poking holes in the firewall?" Data Connection is what clears that first hurdle of enterprise adoption. 📌 Title and Feature URL Title: Data Connection URL: 📝 Overview Data Connection is an application that synchronizes external system data into Foundry for use across the data integration, modeling, and ontology layers. It also supports outbound connections through webhooks and data exports to write data back to external systems. It handles many source types and abstracts away the messy parts — authentication, scheduling, and monitoring — so you can configure pipelines from simple interfaces. 🔧 How It Works Foundry standardizes data connections around three principles: - Robustness: automatic retries, processing in small batches, and integrated health monitoring that warns of failures. Data should be ingested "as-is" from the most primitive source, making Foundry's versioned pipelines the single source of truth for all transformations rather than depending on external preprocessing. - Extensibility: beyond standard integrations (databases, FTPS, HDFS, S3, SFTP), the system accommodates new source types. Because core functions like scheduling and orchestration are standardized, only connection-specific adjustments are needed. - Usability: the system abstracts complexity, letting users configure through simple interfaces instead of manually managing authentication, scheduling, and monitoring. - Key components include agent setup, source configuration, batch/streaming syncs, webhooks, and exports. 🛠 Practical Usage - Access Data Connection from the workspace navigation or the application portal. - Configure a source, then set up a batch or streaming sync to ingest data "as-is." - Concentrate post-ingestion transformations in Foundry pipelines, avoiding preprocessing on the source side. - For write-back, configure outbound integrations using webhooks or exports. 🎯 Use Cases - Connect on-prem Oracle/SAP in a closed network via an agent model (outbound-only) without firewall changes. - Scheduled batch ingestion from diverse sources such as databases, SFTP, and S3. - Outbound integration to write processed results back into external systems. ⚠️ Caveats - The design assumes ingesting data "as-is" and centralizing transforms in Foundry pipelines; transforming on the source side undermines traceability. - Configuring agents and sources requires proper network and authentication setup. - Do not assume external service limits or terms; verify the constraints of each connected source in advance. #PalantirFoundry# #DataIntegration#

The first stage was boomer PMs pattern-recognizing CHGG being disrupted across other sectors post Claude Code The second stage is CEOs pattern-recognizing AI-adoption within their employee-base vs prior cycles of cloud eating on-prem or excel eating graph paper The third stage is CFOs pattern-recognizing AI agents as analogous to outsourcing labor to China or India The fourth stage is exec boards watching a new vertical like accounting get torched overnight and running the pattern-rec on to their own sector and panicking. Claude Code was easy to dismiss. Verifiable rewards. Domain expertise of the labs. Fully digital. When the model capability broadens you get tipping points and the second tipping point marks a pattern. Human psychology isnt rocket science.

“Voters are realizing that [they have the power]… to say ‘I do not want my tax dollars funding this genocide’." Fresh off new progressive victories in Michigan, @prem_thakker spoke to CO DSA candidate @MelatKirosCO about the future of the Democratic Party.

Hyperscalers are depleting their free cash flow for AI. But the models are getting cheaper and enterprises are increasingly moving on-prem. @PatrickMoorhead and @danielnewmanUV debate whether AI CapEx has already outrun its return on Ep. 306 of The Six Five Pod.

Can we shut the internet/X down for a few days/weeks so we don't have to listen to Arsenal fans after tonight result.. Or we are literally never going to hear the end of it about them winning the Prem.. @elonmusk, please?