The ability to put data in the cloud allows developers to create better applications faster, as well as deliver those applications in a way that meets both their needs and the needs of their customers.
One possible implementation model is the managed implementation model. This is a model in which the company is able to provide a fully managed service while storing customer data on its data platform.
However, companies have recently begun to explore a model of related implementation. In this model, code and data are separated in the way that the application provider creates and maintains the code while customers retain control over their data.
In one SD Times Live! eventdata company Snowflake explained more about the differences between the models, as well as information on how to choose the right one for your situation.
According to Brad Culberson, chief data platform architect at Snowflake’s CTO office, the connected model gives customers much more control they wouldn’t have in a traditionally managed offering, such as managing calculations and budgets.
“There are no cross-client datasets in this model, and all data is well isolated in customer owner accounts,” Culberson said. “It’s much, much easier to get approval from within organizations because you always control the data set and no matter what happens, you always have the ability to edit and revoke access at any time in the future. ”
Culberson went on to add that this model scales well for a large number of customers. Other benefits include shifting infrastructure costs to the end customer and greater flexibility for the customer.
To learn more about how to get started with a related deployment model, watch the recap webinar here.