Good offering for cloud deployed sidecar.
Rating: 8 out of 10
IncentivizedUse Cases and Deployment Scope
For certain aspects of the BI Landscape, we required the data to be hosted in the cloud rather than on-premises. Architecture. - A sidecar database is deployed in Google Cloud SQL as a supplement to the main on-premise data warehouse. - Data is replicated from on-prem systems and sensor data - Cloud SQL acts as a read-optimized layer for BI tools and sharing to other cloud services.
Pros
- Performance scaling during peak use.
- Operational Simplicity.
- Avoids licensing costs of expensive middleware to expose on-premise systems to external cloud services.
Cons
- More customer control wrt. backup schedule and retention.
- More granular segmentation for workload limits depending on which pipeline accesses the data to avoid costly errors or misuse.
- Enhanced remote API for stored procedures, enabling initiation from on-premise databases to streamline orchestration and monitoring.
Likelihood to Recommend
Does what it promises well, for instance, as a sidecar for the main enterprise data warehouse. However, I would not recommend using it as the main data warehouse, particularly due to the heavy business logic, as other dedicated tools are more suitable for ensuring scalable operations in terms of change management and multi-developer adjustments.