Optimize Amazon RDS and Aurora Costs with ElastiCache for Redis - AWS Databases in 15

Поделиться
HTML-код
  • Опубликовано: 29 окт 2024

Комментарии • 6

  • @Ffaarg7
    @Ffaarg7 8 месяцев назад +1

    This is great. Thank you. But you could arguably get much of the caching advantage using the RDS database itself by using it as the caching driver without the complexity of more infrastructure. I would say that for many smaller and medium sized businesses that would be a better approach than immediately adding more infrastructure. If the caching API is well designed it will be as simple as changing the driver in the future.

  • @razvancomsa2276
    @razvancomsa2276 15 часов назад

    I'm also curious how is more advantageous compared to just caching the queries results in your app ?

  • @sadekhossain9566
    @sadekhossain9566 2 месяца назад

    Ok so its manual. We have to store the cache, validate and purge. Like a normal redis? Difference is its managed. It would have been awesome if rds does it automatically without changing application code

  • @enricviv
    @enricviv 11 месяцев назад

    The paramount question here is what's the difference of applying one ElasticCache cluster to our Aurora cluster PostgreSQL (2 nodes: readable/writeable) versus to keep using our two auto scaling policies based on cpu and connections threshold?

    • @awssupport
      @awssupport 11 месяцев назад +1

      Great question! You're always welcome to directly ask your question to re:Post for our community experts to review: go.aws/aws-repost. Additionally, our Sales team can help answer any question you may have: go.aws/3N2dae3. 📎 ^LG

  • @onemaninaboat
    @onemaninaboat Год назад +1

    140 subscribers, 70 views. You must be doing something right then...🤦