How would you prepare for rapid scaling?

Speedy data delivery is vital for any thriving web app. Which data storage path would you take and why?

Speaker: Rody Davis

[GoogleDevelopers]

The answer we've locked in is B) A balanced hybrid of data storage solutions. This approach strategically uses NoSQL databases for their schema flexibility, SQL databases for their structured query power, and cloud storage for its expansive capacity, especially for multimedia content. It's a tailored blend that anticipates scale, ensures speedy access, and leverages caching to deliver an uninterrupted user experience.

[MahRabie]

I would pick (C)

Here are some scenarios and use cases where option C would be preferred:

(1) Heavy Unstructured Data Usage
- Content Delivery Networks (CDNs)
- Media Streaming Services

(2) High Scalability and Flexibility Needs
- IoT Applications
- Real-Time Data Processing

(3) Rapid Development and Schema Evolution
- Startups and New Products
- Agile Development Environments

(4) Big Data Applications
- Data Lakes
- Analytics and Machine Learning

(5) Global Distribution and Availability
- Global Applications
- High Availability Systems

(6) Cost-Effectiveness and Simplicity
- Cost-Sensitive Projects
- Simplified Architecture

[GoogleDevelopers]

Which would you choose?
A . SQL only
B. NoSQL and SQL plus Cloud Storage
C. NoSQL plus Cloud Storage
D. Peer to peer

[RandyGalliher]

D. Peer to Peer lowest latency. But C would be faster to deploy and require less recommend time. Also easier to scale.

[maximilian]

what about using a CDN and hold the data on the device with a sync script to update across devices.

D but with a relay server additionally to get around NAT + dynamic IPs and Cloud storage to stop worrying about space.

the rest is not scalable enough to likely handle 5 billion users.

[banzai]

For me, it’s (B). Hybrid
User private data are stored in SQL but user contents, messaging, etc would be in No SQL, Cloud. Always consider your network and encoding for realtime performance.

[AMGunawardana]

C is the pick. Catching and amount of resources types are endless in no sql and scalability and available is possible because of cloud storage.

If get sql into this equation point of failure will be increased because of the speed and cost benefit.

[OnyxStudiosInteractive]

I'm guessing C because it's a multiple choice question and there's firebase😂

[FatimaCantante]

If not in a hurry, I would chose d. but if in a hurry I would have to resource to c.

[namelastname]

you lost me after first sentence.. sound impossible 😂 blocked