concept challenge in category cloud

This is an excerpt from Manning's book Designing Cloud Data Platforms.
The next section explains why a data warehouse alone just won’t deliver on the growth in data variety, volume and velocity being experienced today, and how combining a data lake with a data warehouse to create a data platform can address the challenges associated with today’s data: variety, volume and velocity, otherwise known as the Three V’s.
The challenge with building an ingestion pipeline for a NoSQL database is that there is no single standard on how data can be extracted from those and in which format it will be presented to the ingestion applications. NoSQL name implies that typically SQL as a data access language is not supported and every NoSQL database vendor has their own set of APIs to access the data.

This is an excerpt from Manning's book The Cloud at Your Service: The when, how, and why of enterprise cloud computing.
The challenge for an RDBMS in the cloud is scaling. Applications having a fixed number of users and workload requiring an RDBMS won’t have any problems. Most cloud providers have an RDBMS offering for these cases. But when applications are launched in environments that have massive workloads, such as web services, their scalability requirements can change quickly and grow large. The first scenario can be difficult to manage if you have a relational database sitting on a single in-house server. For example, if your load triples overnight, how quickly can you upgrade your hardware? The second scenario can be too difficult to manage with a relational database, because it becomes a bottleneck choking the application’s ability to scale. We’ll cover solutions to this in depth in chapter 5.
In the next section, we’ll explore the challenges and problems with sharding. You need to understand that although it’s extremely powerful, sharding shouldn’t be used too early or too often.