Generative AI solutions are here but how can an enterprise leverage these capabilities? 1) Model to Data - take your data and integrate the Generative AI model with it. 2) Data to Model - take your data to the Generative AI model which is hosted and managed by the platform. What are your thoughts on this?

3.2k views2 Upvotes4 Comments

VP of IT in Education, 501 - 1,000 employees
For us, Data to Model approach sounds best
CIO in Energy and Utilities, 5,001 - 10,000 employees
If you have data residency issues, then Model to Data approach will make more sense. Security concerns may also be addressed better through this approach. However, you will have to invest in the right infrastructure. If there are no data issues, then Data to Model will be more effective. In both cases, you need to select the right partner.
Senior Director, Data and Digital Solutions in Consumer Goods, 10,001+ employees
Short/medium term Model to Data will be the only real option, assuming the platforms get the security aspects and other enterprise needs addressed. Long term once possibilities and experience with GenAI evolves, Model to Data will be more viable option for some use cases.
Chief Technology Officer in Software, 11 - 50 employees
This is the answer from GPT4 and I agree with it:  Both Model to Data and Data to Model approaches can be effective ways for an enterprise to leverage Generative AI capabilities, depending on their specific needs and resources. Here are some thoughts on each approach:
Model to Data:
In this approach, the enterprise integrates the Generative AI model into its own data infrastructure. This can be beneficial for organizations with strict data privacy requirements or those that want to maintain control over their data. Additionally, integrating the AI model into existing systems may allow for better customization and fine-tuning to the specific needs of the organization. However, this approach may require significant investment in computing resources and expertise to manage and maintain the AI model.


Greater data privacy and control
Potential for better customization to specific use-cases
Integration with existing data infrastructure


Higher upfront investment in resources and expertise
Potential challenges in managing and maintaining the AI model
Data to Model:
In this approach, the enterprise sends its data to the Generative AI model hosted and managed by an external platform. This option is usually more accessible and cost-effective for organizations that lack the resources or expertise to manage AI models in-house. By leveraging a managed platform, enterprises can take advantage of the latest AI advancements without needing to maintain the infrastructure themselves. However, data privacy and control may be a concern for some organizations in this approach.


Lower upfront investment in resources and expertise
Access to the latest AI advancements
Managed platform takes care of model maintenance and updates


Potential data privacy concerns
Less control over data and AI model
May be less customizable to specific use-cases

In conclusion, both approaches have their own merits and drawbacks. Enterprises should carefully consider their specific needs, resources, and data privacy requirements when deciding which approach to adopt for leveraging Generative AI solutions.

Content you might like

Modbus (widely used protocol in industrial automation and control systems)13%

OPC UA (protocol for machine-to-machine communication that is designed for use in industrial automation and control systems)48%

MQTT (lightweight messaging protocol that is designed for use in low-bandwidth, high-latency networks)21%

DDS (real-time publish-subscribe communication protocol that is designed for use in distributed systems)10%

AMQP (messaging protocol that is designed for use in distributed systems)2%

LoRaWAN (long-range radio-wide area network used for IoT, smart cities, and industrial applications)1%

Proprietary protocols (please, comment)4%


675 views1 Upvote

Big Data21%

Remote Work17%

Microservices / Containerization11%

CI / CD5%



Digital Transformation16%

Cloud / Cloud Native1%

DevOps or DevSecOps6%

Other (comment)1%


2.6k views5 Upvotes16 Comments

CTO in Software, 201 - 500 employees
Without a doubt - Technical Debt! It's a ball and chain that creates an ever increasing drag on any organization, stifles innovation, and prevents transformation.
Read More Comments
40.8k views131 Upvotes319 Comments