Tweet
I've worked all day yesterday in UI, over complicated something that was meant to be easy. I think I've sorted that one out.

Now to the next task - creating the API call to support the UI.

The joy of finding #DynamoDb patterns to support my app.

#buildinpublic #Serverless #AWS
Excited to share my latest blog post on Mind Mantle, where I explain how I'm building the app using AWS SAM, Cognito, and React. Check it out and let me know what you think!
medium.com/mind-mantle/bu…
#serverless #AWS #React #dynamodb #cognito #buildinpublic #indiehackers
Eating your own dog food does wonders when picking the next most important feature to build. Code generation, out! Search history, in! #buildinpublic #dynamodb
When you create your entities in #DynamoDb, do you make your attributes as small as possible? What I'm saving in the db I'm making them 1-2-3 characters long and what my API returns has a proper name that I can understand. Is it too much, too little? #startup #buildinpublic #AWS
Day 3/60. Continued thinking about my entities and playing with NoSql Workbench to visualise how the db will look like. It's hard work after my day job to find time to work for me. How are others managing? No excuse. #AWS #Dynamodb #NoSql #SaaS #buildinpublic #startups
Day 2/60. I have the domain registered in Route53 in AWS. Started thinking about the entities and having a play with NoSql Workbench to visualise how the db will look like #AWS #Dynamodb #NoSql #SaaS #buildinpublic #startups
Save 37% on #DynamoDB costs.

My first attempt to help you figure out what's happening with your @dynamodb tables and lower your costs. Burst Capacity warnings as a bonus.

Check it out cloudpouch.dev

What do you think? Feedback welcomed
#buildinpublic #aws #costSaving
🌼 MétéoPollen: Comme sur un autre projet, je me retrouve bloqué par les possibilités de DynamoDB... 💩💀
Je vais donc ajouter Mongo à la stack pour gérer l'historique. Dynamo sera utilisé pour stocker les tokens des devices et les données du jour.

#buildinpublic #aws #dynamodb
🌼 MétéoPollen : J'ai développé la première brique du backend :
- Mise à jour auto de la base de données des indices de pollens
- API pour récupérer les données depuis l'app #ios

Stack utilisée : #TypeScript, #DynamoDB, #Lambda et déploiement via #Serverless

#buildinpublic