(no title)
tenaciousDaniel | 4 years ago
1. Create dynamic schemas. Some of our clients had their own dimensions that they cared about.
2. Pick the level of integration. Imagine having an out-of-the-box integration available, but then offering fully customizable solutions for one-off scenarios.
Really it comes down to those two things, which basically means "flexibility". Like I said, we spent months evaluating products, and while we found several companies claim to offer the above, no one actually did.
tenaciousDaniel|4 years ago
igorlukanin|4 years ago
The motivation is diverse but one of the reasons is that a Cube app should be scaled differently from a client-facing app. Noone probably wants their app to hang when Cube serves a ton of requests or refreshes cached data (and vice versa). That’s why it’s recommended to run Cube as microservices. I hope it’s not a big deal since a lot of cloud platforms provide container environments.
Also, just recently, we’ve launched Cube Cloud which provides serverless experience for Cube apps and has a free tier: https://cube.dev/cloud/
seektable|4 years ago
pklee|4 years ago
igorlukanin|4 years ago
mason55|4 years ago