Your video is the most clearest source, even compared to Spring docs. Aurora Engine is not supported in spring aws cloud, If you use Aurora with read replicas it "looks works" but the read replica is never used and all queries are sent to the writer instance.
Great Video! Just a query for my use case, if I am using secrets manager for db credential how can I make connection for read and write replica using the aws-cloud-sdk dependency because I will not be able to add the details in properties file, Can we acheive this using config or bean?
Very informative. SpringCloud AWS provides most of the features out-of-the-box. Btw, where is the connection details to your AWS Account? Did you configure the AWS AccountId and Key, Region in the SpringBoot application.properties file? Thank you so much!
You don´t need to care about these details about RDS. Once you configure it, you have an endpoint, then you can treat the connection as any other kind of database, connection by endpoint url.
In local env like compose or local network read replicas downgrades perfomance, so with single db perfomance is higer so i make spring app with two datasources for reads and writes i tried up to 12 instances of app and 12 instances of postgres, and tried different configs 12X12 one replica per instance, ot 1X4 and other, but no perfomance improvement used haproxy and pgpool for load balancing and RW segregation still single DB perfoms faster in common LAN or compose
Won't make a difference, but, you could setup an ingress rule from your local machine IP with a /32 CIDR towards that SG. This way, at least, you won't expose it to the whole world ;) - ofc, you still should not do it in production.
You explain very well the topics, could you please make more tutorials.
thank you
Your video is the most clearest source, even compared to Spring docs. Aurora Engine is not supported in spring aws cloud, If you use Aurora with read replicas it "looks works" but the read replica is never used and all queries are sent to the writer instance.
Great Video! Just a query for my use case, if I am using secrets manager for db credential how can I make connection for read and write replica using the aws-cloud-sdk dependency because I will not be able to add the details in properties file, Can we acheive this using config or bean?
Very informative. SpringCloud AWS provides most of the features out-of-the-box. Btw, where is the connection details to your AWS Account? Did you configure the AWS AccountId and Key, Region in the SpringBoot application.properties file? Thank you so much!
You don´t need to care about these details about RDS. Once you configure it, you have an endpoint, then you can treat the connection as any other kind of database, connection by endpoint url.
Another great video 👍🏻
Thanks
cool man , thank you
Awesome video!.Thanks a lot!.
Great feature explanation. Like!
Will there be anything different when using Aurora other than go for the MySQL driver lib vs PostgreSQL lib?
I've been looking for datasource url format a couple of days. Thanks!
As usual great content. Thanks
Thanks man!
TKS BRO AMAZING
In local env like compose or local network read replicas downgrades perfomance, so with single db perfomance is higer
so i make spring app with two datasources for reads and writes
i tried up to 12 instances of app and 12 instances of postgres, and tried different configs
12X12 one replica per instance, ot 1X4 and other, but no perfomance improvement
used haproxy and pgpool for load balancing and RW segregation
still single DB perfoms faster in common LAN or compose
cool demo!
Thanks for this, if I could request, please do reactive repository on relational dbms
Thanks! Added to a list
Great content.Thanks👍🏼
Thanks for feedback! Glad you liked it!
hello great video.
The version 2.4 works in the same way?
Thx!
Nice video! Can I set different repository classes pointing to different read replicas?
Would be interesting how to use Spring Cloud AWS with AWS IAM.
Hmmm like what for example?
Won't make a difference, but, you could setup an ingress rule from your local machine IP with a /32 CIDR towards that SG. This way, at least, you won't expose it to the whole world ;) - ofc, you still should not do it in production.