Can you partition a database between public clouds and on-premises?

I get this request a whole lot: We have a single, substantial database and want to hold section of the info on-premises and section of the info in the cloud. Is that attainable? 

Of study course. Ample time and cash can address all difficulties. The serious query is not “can we,” but “should we?” Here are the realities:

Most databases deliver actual physical partitioning mechanisms that let you to separate actual physical info above networks, which include the open Online, in which a partition is hosted in the cloud. Some enterprises use this architecture for hybrid cloud use cases. On the other hand, they are not usually intended for the cloud and the slower network of the Online. 

The problems? Even if you get it performing, the latency will be obvious for 50 % of the stored info. Let’s say a cloud-primarily based software accesses the cloud and on-premises partitioned info. The info that resides on the distant partition (in this case in point, the on-premises partition) will have obvious latency problems. 

Don’t forget, functionality is decided by the slowest ingredient. When a database creates info with latency, the in general info latency will be sluggish as effectively. You can verify this employing functionality modeling or merely consider it. The gratification you get for keeping some of your info nearby will charge you in functionality. Indeed, in most cases, it’s unworkable. 

Several of the database players, cloud and not, will not tell having to pay shoppers who want to use this composition that the respond to really should be no. Clearly, you can toss cash at the difficulty, these kinds of as for detected network circuits. But the charge of accomplishing that usually gets rid of any value that cloud-primarily based databases may perhaps carry. In other phrases, it’s more affordable to remain on-premises.