Urgent.News

What's breaking now, across thousands of outlets.

Tech

Respaldo NoSQL en Firestore: cifrar, verificar y recuperar documentos

Autor: Antony Piero Solorzano Zegarra Equipo: Antony Piero Solorzano Zegarra y Adriana Rafaela Laos Gonzales. Guardar un archivo no demuestra que podamos recuperar una aplicación. Para estudiar esa diferencia preparamos una estrategia de respaldo de Campus Tareas , una aplicación de tareas con Cloud Firestore Standard. Código público: https://github.com/AntonyS3010/nosql-backup-firestore Qué…

We haven't written up this one. Dev.to has the full story — the link below goes straight to it.

Read the original at dev.to →

More in Tech

Very cool insights

How I benchmark coding agents stepping on each other (and the bug it found) Michele Matozza Michele Matozza Michele Matozza Follow Nov 18 How I benchmark coding agents stepping on each other (and the…

Una estrategia de backup NoSQL necesita automatización y ensayos de recuperación

Autora: Adriana Rafaela Laos Gonzales Equipo: Antony Piero Solorzano Zegarra y Adriana Rafaela Laos Gonzales. Una estrategia de respaldo debe responder qué información protege, cuánto podría perderse…

  • Effective NoSQL backup strategy requires automation and recovery testing
  • Backup copy of Firestore-based task app retained for at least 24 hours, daily execution
  • Backup process involves temporary token, document querying, encryption, and artifact storage

Brain Frizz, Part 1: Blocking My Day

Brain Frizz, Part 1: Blocking My Day I review a lot of pull requests (PRs) now. Some of that is the job. As a staff engineer, part of my work is helping other people get unstuck, and on a team where…

  • Engineer experiences "brain frizz" during workday
  • Divides day into fixed blocks for specific tasks
  • Tracks brain frizz levels twice daily during experiment

The BIGINT Problem Explained

What Happens When Your Database Reaches 1 TB? How a growing events platform like Matoo helps us understand database limits, performance challenges, and the need to plan for scale.

  • BIGINT(20) supports up to 9.2 quintillion values, unlikely to be exhausted through normal use.
  • Indexes improve data retrieval efficiency but add storage overhead as database grows.

More from Thursday 19 November →