menu

Working with Amazon ElastiCache for Redis

Go to Lab

121 Revisar

3cdeea73cbbb22cd0d3c48f1ce0f0c48

ShiJun W. · Avaliado 5 dias atrás

Df57704a3807a70a5838b6ce0bde4e2e

Parirajan R. · Avaliado 5 dias atrás

110757b0ea22f7a73b65c3acf5942a60

Could use a little more time for this - the data distro to redis can take a bit longer than expected

Eric F. · Avaliado 6 dias atrás

F7d88cf79c776ee2d2538083f52f36d8

satisfied, but I was unable to finish it due to an unexpected commitment that pulled me away from it. Would be nice if one could use the same code for the same account and lab, maybe within a 12 hour window or something like that.

Tony P. · Avaliado 8 dias atrás

E01746944c30fef28702c2d2f4dc4d5e

Alban D. · Avaliado 11 dias atrás

2ff80289bc39093f03b93e79cb632eba

Very interesting. Will be useful for my company's database caching.

Craig B. · Avaliado 16 dias atrás

0bb5778d35f9dee35f48291fde8fbbfe

Good

Hua J. · Avaliado 16 dias atrás

1d933e26b291dc91ef5699002c461b37

time not enough

anan c. · Avaliado 16 dias atrás

2ee1c87c9b3966412e4e5e9d1bd0e69a

A very nice exercise, however it must have more time! We got almost to the end (step 86) but the process of copying data from mysql to redis simply takes too long, and the lab was closed on us! SHAME.

Tal T. · Avaliado 16 dias atrás

8b50dec5fd1aefcd485819e91fe5a845

Dan H. · Avaliado 16 dias atrás

C765be0d0a26a9c687e04d55720725b9

David G. · Avaliado 17 dias atrás

643ceadfd1f2ac2f66a6be8933a63f20

Dana D. · Avaliado 17 dias atrás

3f3fad421bee1b28822361d9d9f577e5

lab worked fine, set up was fine. Just not sure I 100% understand what elastecashe is doing still

Tony D. · Avaliado 17 dias atrás

78cfa69e721485d0028a754d72ef8e57

you had questions at the end... how long did each query take to run...why do you think they run more quicky? I don't know...please tell me

Michael H. · Avaliado 17 dias atrás

A83ec24bce7f047a7ad138a56f419987

This lab felt more unpolished than some of the other ones I've done. There were several steps where there were long waits, which weren't clearly identified in the text. PuTTY kept timing out. 250000 rows was a little bit too slow to load into Redis using the python script, my PuTTY timed out towards the end, and the load progress didn't finish (DBSIZE didn't quite get to 250000). The Redis commands were not explained at all - there should have been a paragraph talking about what they are doing. The numbers that are output after running the commands are completely obscure and it isn't at all clear that the Redis is doing the same thing as the SQL, and the SQL query is unnecessarily complicated with an inner subquery to figure out the max acq date. And Redis didn't really give the timing statistics to even know that it's running faster than the SQL.

Leo Z. · Avaliado 17 dias atrás

Ee460d9ac7dfe7ffcdc026ecd6d41a67

William A. · Avaliado 17 dias atrás

F9dfd28d4449b58c4cbbe472eda0bc18

Tonny I. · Avaliado 18 dias atrás

F9dfd28d4449b58c4cbbe472eda0bc18

Tried EVERYTHING to connect through putty. So I did not learn anything from this

Tonny I. · Avaliado 19 dias atrás

926b1f0f1570211928207f375729a462

Jiyu Z. · Avaliado 19 dias atrás

A66cf5101e3619dd60965381ca6dcd54

Shigeo K. · Avaliado 19 dias atrás

85478835a23a7a84110a16d96a05f56f

Ross N. · Avaliado 19 dias atrás

9e60ab285bd53d816c94ab09b1d018c8

In "64.For Security group~", I can not click "Security group" and lab(vpc-XXX).

進 高. · Avaliado 23 dias atrás

9e60ab285bd53d816c94ab09b1d018c8

I can not it because of timeover in DBSIZE.

進 高. · Avaliado 23 dias atrás

F251ac844ae908928025d4f5816dddda

Ciprian M. · Avaliado 24 dias atrás

F634423be88cf3adbd0c3a9e6b01b4b5

Annie D. · Avaliado 25 dias atrás