Share this page!

Enter Twitter Thread URL to Unroll

Needs to be the full URL like: https://twitter.com/threadreaderapp/status/1644127596119195649

How to get URL link on Twitter App

  1. On the Twitter thread, click on or icon on the bottom
  2. Click again on or Share Via icon
  3. Click on Copy Link to Tweet
  4. Paste it above and click "Unroll Thread"!
  5. More info at Twitter Help
Khawaja Shams Profile picture
@ksshams
Apr 20 • 4 tweets • 3 min read Twitter logo Read on Twitter
Getting started with just 5 lines of code was pretty neat, but how about zero?

Momento Console is here!

@dymxzvf personally worked on this alongside our awesome deveco team. DM us for early access to upcoming features.

#launch #serverless

gomomento.co/3Af3iH8
Getting started on the @momentohq console is as simple as using your existing Google/Github accounts to sign-on! Image
If you are a new customer, you may not have any caches - but not to worry, it takes 10 seconds to make one! Image
To make a cache, just pick a name, a cloud provider, & the region. That’s it! You now have a secure cache ready for millions of tps w/ zero downtime.

No complex configurations, remembering to turn on auth/ TLS, picking instance family/size/number.

NO MAINTENANCE WINDOWS! Image

• • •

Missing some Tweet in this thread? You can try to force a refresh
　

Keep Current with Khawaja Shams

Khawaja Shams Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @ksshams

Khawaja Shams Profile picture
Apr 3
A customer was considering leaving #dynamodb due to costs.

@pj_naylor and I helped them save half a million dollars per year with one simple, magical, optimization.

Want to save DynamoDB costs like a pro? Let’s start with some background…
1\ DynamoDB writes are 20x more expensive than reads. If you have 5 GSIs, you may be doing 6 writes every time you write a single item into a DynamoDB table.

The 20x is not a typo. More on that soon.
2\ The read & write request units are a bit complex. Let’s simplify, @momentohq style.

DynamoDB writes are charged in 1KB increments.

If you write 100 bytes, you pay for 1KB. 1.1KB => 2KB.

Writing exactly 1KB items costs $1.25/GB (on-demand), but….👇
Read 17 tweets
Khawaja Shams Profile picture
Jan 30
#DynamoDB strongly consistent reads are magical, but not for the reason most of us think.

SC reads have higher latencies, lower availability, and cost more - but worth it if you use them for the right reasons.

🧵👇explains what they are & how to unlock their real power!
0\ Primer: Doug Terry does a phenomenal job explaining the various consistency models through an illustrative exercise:
microsoft.com/en-us/research…

Read this first to become a consistency ninja!
1\ The most common mistake I see with DynamoDB SC reads is assuming it’s fresher than it is. Suppose you want to increment a counter: an SC Read tells you X=2 - you *cannot* set X=3 because another thread may have already changed it in the meantime. Use Conditional Puts instead!
Read 18 tweets

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

Send Email!

:(