I'm back at Microsoft after 4 years away! ๐
I'm joining the Databases org as a Principal PM on Azure Postgres โ VS Code extension, DX, and the agent experience.
Also moving the family back to Seattle!
Missed Microsoft. Missed Seattle. Excited for both!
GraphQL aggregations are finally here in @Microsoft Fabric.
Query smarter, not harder.
Group and summarize data natively without the usual workarounds.
Make sure you check out Cosmos DB Conf happening now! Lots of the engineering team is also in the chat to answer any questions you might have. https://t.co/dxtzQw1C3b
Really cool case study showing how Toyota is using Azure Durable Functions and Cosmos DB to build multi-agent AI systems to enhance vehicle development productivity!
https://t.co/Y4Oa8NHpiP
๐ Exciting news! Dynamic Scaling is now GA in #AzureCosmosDB! ๐ Save up to 70% on autoscale costs for non-uniform workloads with independent scaling per region and partition.
Learn more: https://t.co/0q1cR651jH
@freshperspected I'm lucky enough to have worked with some of the best people in MSFT and AWS. Even in MSFT, the teams I've worked on can be quite different from one another. I think high functioning teams will often look different because they are going to optimize for their specific problems.
I'm excited to share that I've joined Microsoft. I'll be working across Azure Databases with a focus on innovating developer experience. โค๏ธ๐๐๐
As always, my DMs are open. If you have any feedback or ideas on how we could make Azure Databases better, I would love to hear from you and learn more.
Today is my last day at Amazon. A lot has happened over the past 2.5 years. My very first day on DynamoDB was also the day my wife and I learned we were pregnant with my son. They got to see him start to walk and talk. Iโm grateful I got to work with such amazing, kind people. ๐
@houlihan_rick@MongoDB These days, it's far simpler to use an export as the source for reads. Plus, you can use incremental export to get any changes since you started the export, making finding other changes easier. Generally more cost efficient than hyper-scaling, depending on the scenario.
@richdevelops Yeah, in your case, it probably makes sense to just rotate the account. I usually create a burner anytime I'm going to be presenting publicly. Helps to also avoid leaking other info like non-public features/etc.