Edin Zulich

NoSQL @AWSCloud. I like doing more with less... I like cloud & serverless 😁 Social media shy. Views my own.

[Edin Zulich @EdinZulich]

@houlihan_rick So sorry to hear that, Rick. My deepest condolences to you and family. You’re in my thoughts. 💔

[Edin Zulich @EdinZulich]

@jeremy_daly @goserverless Nice! My favorite rye this holiday season is Angel’s Envy Finished Rye. Merry Christmas! Happy Holidays!

[Edin Zulich @EdinZulich]

@dynamodb These positions are flexible in terms of locations, in their respective regions. We are all working from home/remotely these days, anyway. If you have DynamoDB/NoSQL skills and like to use them to help others, take a look. DM me (I'm the hiring manager) If you have any questions.

[Edin Zulich @EdinZulich]

@billbarthel @houlihan_rick @dynamodb Yes, it could. Feel free to DM me if you have any other questions (I'm the hiring manager).

[Edin Zulich @EdinZulich]

@juancpgo @dynamodb Not yet. Emailed you the model.

[Edin Zulich @EdinZulich]

@MattCCrampton @alexbdebrie @jeremy_daly @dynamodb @houlihan_rick @NoSQLKnowHow No: A key attribute cannot be null, so 1) when you create a GSI, items that have null as the GSI partition key would not be projected, and 2) with a GSI in place, attempts to write an item with null as the value of the GSI key attribute would fail with a ValidationException.

[Edin Zulich @EdinZulich]

@jeremy_daly @dynamodb @houlihan_rick @alexbdebrie @NoSQLKnowHow Null in DynamoDB was added with several other types when support for storing JSON documents as DynamoDB items was added. This is one case where you’d need it. https://t.co/VMX9gBfjrJ

[Edin Zulich @EdinZulich]

@jeremy_daly @dynamodb @houlihan_rick @alexbdebrie @NoSQLKnowHow Remove the attribute. In SQL null is used to represent missing data. If a schema defines a column and a row doesn’t have a value for it, null is the way to represent that state. In NoSQL/DynamoDB, if data is missing—well, it’s missing. No need to waste storage to tell me that.

[Edin Zulich @EdinZulich]

@alexbdebrie @houlihan_rick Thank you both for finding time to come to Seattle for this! Btw, https://t.co/VoEkmQII6V posted a trimmed version of the recording (sans 7+ min of intro splash screen):

https://t.co/zufERAutMU

[Edin Zulich @EdinZulich]

Enjoyed hosting @alexbdebrie and @houlihan_rick for an insightful and fun conversation. Big thank you to both! https://t.co/VoEkmQII6V posted a nicely trimmed version (without 7+ minutes of intro splash screen + elevator music): https://t.co/zufERAutMU

[Alex DeBrie @alexbdebrie]

For more on this, make sure you watch the recording of @EdinZulich, @houlihan_rick, and I talking about single-table design on Twitch last week

https://t.co/WjpABLc79a

[Edin Zulich @EdinZulich]

On https://t.co/LOQYLcTJC1 this Thursday, at 11am Pacific: Join us to find out and ask questions about one of the fundamental concepts in NoSQL and DynamoDB: how to think about denormalization/single-table design.

[DynamoDB @dynamodb]

It's happening! This Thursday on Twitch. January 30. 11 AM Pacific Time.

Rick Houlihan & Alex DeBrie discuss the pros & cons of DynamoDB single-table design, & other best practices for designing your data models.

Join us! https://t.co/brkCcEhr4Q

[Edin Zulich @EdinZulich]

@dynamodb @cloudbart @mikiUK There won't be a show specific page. Just go to https://t.co/IdL0XvdzG2 on Thursday, January 30th, at 11am Pacific.

[Edin Zulich @EdinZulich]

Happy birthday, DynamoDB! It’s been a fun ride working with you and watching you grow. My top 3 all-time favorite new features: 1) On-demand capacity mode (pay per request), 2) Global Tables, and 3) Adaptive Capacity. Truly #serverless #cloudnative #nosql database.

[DynamoDB @dynamodb]

Happy eighth birthday to DynamoDB! Lots of good things planned for the service's ninth year in 2020, but here's a reminder of the year DynamoDB had in 2019: https://t.co/PWFwcJ8sCW

[Edin Zulich @EdinZulich]

@NosqlH @dynamodb 😁 I couldn’t single out just one of the Adaptive Capacity features. It’s about what the package does as a whole to make DynamoDB better at handling imbalanced traffic, resulting in better app performance and better capacity utilization->lower cost.

[Edin Zulich @EdinZulich]

If you're a DynamoDB user, you'll find this review of features released in 2019 very handy. My top 3 are: 1. Global tables: add replica, and cost optimization, 2. new Adaptive capacity features, and 3. CW contributor insights: turn-key hot key detection. What are yours?

[DynamoDB @dynamodb]

2019: The year in review for Amazon DynamoDB. Summaries of all 35 DynamoDB launches this year: https://t.co/qdxfJL870Z

[Edin Zulich @EdinZulich]

@houlihan_rick @alexbdebrie @sethcenterbar @dynamodb @ben11kehoe @Twitch Right on. I'll reach out to get the ball rolling.

[Edin Zulich @EdinZulich]

@jeremy_daly @paulswail @dynamodb Thanks, and yeah--that's a great point too. 'cart' table would likely have some denormalized data from 'catalog' table/service as well (e.g. name and desc. for each cart item) so that we pick up everything we need for a full cart view with a single read from 'cart' table.

[Edin Zulich @EdinZulich]

Cost should be a key concern and input when designing solutions in the cloud. I use cost estimates to inform my design choices.
To learn how to do this for @dynamodb, check out the latest episode of Build with DynamoDB: https://t.co/Hkh9AYKQVq.

[Edin Zulich @EdinZulich]

@bjorg @jeremy_daly @jbesw @mavi888uy @sbarski @chrismunns @alex_casalboni @hichaelmart @amsxbg @kneekey23 Kinesis Data Firehose has a default throughput limit when used standalone. This limit goes away if it’s configured to use Kinesis Data Streams in front of it, as the data source. Hence “Kinesis in front of Kinesis”.