home.social

#cloudsql — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #cloudsql, aggregated by home.social.

  1. Aprovechando la transición a #Manjaro en la cual estoy reinstalando, les cuento como conectarse a una instancia de #Google #CloudSql.

    Resumen:

    + Instalar Google Cloud SDK (#AUR)
    + Autenticación proyecto
    + Autenticación credenciales por defecto de aplicación
    + Instalar Cloud SQL Proxy (AUR)
    + Instalar cliente de base de datos. En este caso, uso #DbGate (flatpak)

    cosmoscalibur.com/es/blog/2024

  2. Aprovechando la transición a #Manjaro en la cual estoy reinstalando, les cuento como conectarse a una instancia de #Google #CloudSql.

    Resumen:

    + Instalar Google Cloud SDK (#AUR)
    + Autenticación proyecto
    + Autenticación credenciales por defecto de aplicación
    + Instalar Cloud SQL Proxy (AUR)
    + Instalar cliente de base de datos. En este caso, uso #DbGate (flatpak)

    cosmoscalibur.com/es/blog/2024

  3. Aprovechando la transición a #Manjaro en la cual estoy reinstalando, les cuento como conectarse a una instancia de #Google #CloudSql.

    Resumen:

    + Instalar Google Cloud SDK (#AUR)
    + Autenticación proyecto
    + Autenticación credenciales por defecto de aplicación
    + Instalar Cloud SQL Proxy (AUR)
    + Instalar cliente de base de datos. En este caso, uso #DbGate (flatpak)

    cosmoscalibur.com/es/blog/2024

  4. Aprovechando la transición a #Manjaro en la cual estoy reinstalando, les cuento como conectarse a una instancia de #Google #CloudSql.

    Resumen:

    + Instalar Google Cloud SDK (#AUR)
    + Autenticación proyecto
    + Autenticación credenciales por defecto de aplicación
    + Instalar Cloud SQL Proxy (AUR)
    + Instalar cliente de base de datos. En este caso, uso #DbGate (flatpak)

    cosmoscalibur.com/es/blog/2024

  5. Our simple database-as-a-service CloudSQL now supports live resizing database instances! 🚀

    brightbox.com/blog/2024/04/09/

    #cloudsql

  6. Our simple database-as-a-service CloudSQL now supports live resizing database instances! 🚀

    brightbox.com/blog/2024/04/09/

    #cloudsql

  7. Our simple database-as-a-service CloudSQL now supports live resizing database instances! 🚀

    brightbox.com/blog/2024/04/09/

    #cloudsql

  8. Our simple database-as-a-service CloudSQL now supports live resizing database instances! 🚀

    brightbox.com/blog/2024/04/09/

    #cloudsql

  9. Our simple database-as-a-service CloudSQL now supports live resizing database instances! 🚀

    brightbox.com/blog/2024/04/09/

    #cloudsql

  10. Yesterday was largely spent cleaning up other peoples messes, which isn't always fun.

    Today I am going to be working more on cloud vulnerability stuff related to cloudsql in GCP, working on EDR exclusions and creating a security training for Jamf :D

    #security #cloudsql #gcp #edr #Jamf

  11. Yesterday was largely spent cleaning up other peoples messes, which isn't always fun.

    Today I am going to be working more on cloud vulnerability stuff related to cloudsql in GCP, working on EDR exclusions and creating a security training for Jamf :D

    #security #cloudsql #gcp #edr #Jamf

  12. Yesterday was largely spent cleaning up other peoples messes, which isn't always fun.

    Today I am going to be working more on cloud vulnerability stuff related to cloudsql in GCP, working on EDR exclusions and creating a security training for Jamf :D

    #security #cloudsql #gcp #edr #Jamf

  13. Yesterday was largely spent cleaning up other peoples messes, which isn't always fun.

    Today I am going to be working more on cloud vulnerability stuff related to cloudsql in GCP, working on EDR exclusions and creating a security training for Jamf :D

    #security #cloudsql #gcp #edr #Jamf

  14. Yesterday was largely spent cleaning up other peoples messes, which isn't always fun.

    Today I am going to be working more on cloud vulnerability stuff related to cloudsql in GCP, working on EDR exclusions and creating a security training for Jamf :D

    #security #cloudsql #gcp #edr #Jamf

  15. Hi friends! Today #CloudSQL is introducing tiers! The new Enterprise Plus tier offers improved performance, availability and data protection.

    For more details, check out the video (links to longer blog in description):

    youtube.com/watch?v=JyVXBHvw0K

    #GoogleCloud

    #Postgres #MySQL

  16. Hi friends! Today #CloudSQL is introducing tiers! The new Enterprise Plus tier offers improved performance, availability and data protection.

    For more details, check out the video (links to longer blog in description):

    youtube.com/watch?v=JyVXBHvw0K

    #GoogleCloud

    #Postgres #MySQL

  17. Hi friends! Today is introducing tiers! The new Enterprise Plus tier offers improved performance, availability and data protection.

    For more details, check out the video (links to longer blog in description):

    youtube.com/watch?v=JyVXBHvw0K4

  18. Hi friends! Today #CloudSQL is introducing tiers! The new Enterprise Plus tier offers improved performance, availability and data protection.

    For more details, check out the video (links to longer blog in description):

    youtube.com/watch?v=JyVXBHvw0K

    #GoogleCloud

    #Postgres #MySQL

  19. Hi friends! Today #CloudSQL is introducing tiers! The new Enterprise Plus tier offers improved performance, availability and data protection.

    For more details, check out the video (links to longer blog in description):

    youtube.com/watch?v=JyVXBHvw0K

    #GoogleCloud

    #Postgres #MySQL

  20. For reasons, we need to attest that "the application can recover a #CloudSQL failure with exponential backoff".
    The HTTP+JSON based APIs in question are #Java and #Tomcat based, but Tomcat JDBC connection pool doesn't support exponential backoff.
    I would like to understand what could be a good reason to insist to have exponential backoff in this setup.
    In my mind there is no good reason, as JDBC connection pool will recover from failure eventually, but only faster.
    What do you think?

  21. For reasons, we need to attest that "the application can recover a #CloudSQL failure with exponential backoff".
    The HTTP+JSON based APIs in question are #Java and #Tomcat based, but Tomcat JDBC connection pool doesn't support exponential backoff.
    I would like to understand what could be a good reason to insist to have exponential backoff in this setup.
    In my mind there is no good reason, as JDBC connection pool will recover from failure eventually, but only faster.
    What do you think?

  22. Hey y'all! GA today, #CloudSQL for #Postgres WAL will be stored on Google Cloud Storage instead of on disk. Lots of good details here:

    cloud.google.com/sql/docs/post

  23. Hey y'all! GA today, #CloudSQL for #Postgres WAL will be stored on Google Cloud Storage instead of on disk. Lots of good details here:

    cloud.google.com/sql/docs/post

  24. Hey y'all! GA today, for WAL will be stored on Google Cloud Storage instead of on disk. Lots of good details here:

    cloud.google.com/sql/docs/post

  25. Hey y'all! GA today, #CloudSQL for #Postgres WAL will be stored on Google Cloud Storage instead of on disk. Lots of good details here:

    cloud.google.com/sql/docs/post

  26. Hey y'all! GA today, #CloudSQL for #Postgres WAL will be stored on Google Cloud Storage instead of on disk. Lots of good details here:

    cloud.google.com/sql/docs/post

  27. Do you use #kubernetes and #CloudSQL? We're making that easier for you!

    New k8s operator for the Cloud SQL Proxy in public preview now. 8 lines of YAML to enable it in your deployment now vs 61 lines, and a lotta manual deployment before. Check it!

    github.com/GoogleCloudPlatform

  28. Do you use #kubernetes and #CloudSQL? We're making that easier for you!

    New k8s operator for the Cloud SQL Proxy in public preview now. 8 lines of YAML to enable it in your deployment now vs 61 lines, and a lotta manual deployment before. Check it!

    github.com/GoogleCloudPlatform

  29. Do you use and ? We're making that easier for you!

    New k8s operator for the Cloud SQL Proxy in public preview now. 8 lines of YAML to enable it in your deployment now vs 61 lines, and a lotta manual deployment before. Check it!

    github.com/GoogleCloudPlatform

  30. Do you use #kubernetes and #CloudSQL? We're making that easier for you!

    New k8s operator for the Cloud SQL Proxy in public preview now. 8 lines of YAML to enable it in your deployment now vs 61 lines, and a lotta manual deployment before. Check it!

    github.com/GoogleCloudPlatform

  31. Do you use #kubernetes and #CloudSQL? We're making that easier for you!

    New k8s operator for the Cloud SQL Proxy in public preview now. 8 lines of YAML to enable it in your deployment now vs 61 lines, and a lotta manual deployment before. Check it!

    github.com/GoogleCloudPlatform

  32. Doing nightly work for the first time in ages.

    Moving data from an old private cloud #postgres cluster to #cloudsql in #googlecloud. I love it when my projected time schedule is spot on - it helps to have tested the migration a couple of times to iron out any potential issues or bottlenecks.

    #sre

  33. Das neue Werkzeug Cloud SQL Insights soll Entwickler beim Aufspüren und Beheben von Performanceengpässen im Datenbankdienst unterstützen.
    Datenbankdienst: Google verschafft mehr Einblick in Cloud SQL
  34. Google’s managed database service to support Microsoft SQL Server - It’s not every day that you read a headline with both Google and Microsoft. Google is announcing to... more: feedproxy.google.com/~r/Techcr #googlecloudnext2019 #googlecloudnext #googlecloudsql #googlecloud #developer #cloudsql #google #cloud