rponte

Incident Communication Guide

For Small Teams

Purpose

This guide defines when to declare an incident, who is responsible for communication, and how to communicate externally during an incident.

It also defines how to act technically during an incident, emphasizing mitigation over fixes to reduce risk and downtime.

rponte

export $(cat .env | xargs) && uv run main.py

rponte

async def create_charge(charge: Charge, customer: Customer) -> None:
	
    if not customer.is_active():
        raise CustomerInactiveError("The customer is not active.")
		
    if not charge.has_valid_amount():
        raise InvalidChargeAmountError("The charge amount must be greater than zero.")
		
    if not charge.has_valid_due_date():
        raise InvalidDueDateError("The due date must be in the future.")

rponte

import org.assertj.core.groups.Tuple;
import org.junit.jupiter.api.DisplayName;
import org.junit.jupiter.api.Test;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.boot.autoconfigure.validation.ValidationAutoConfiguration;
import org.springframework.boot.test.context.SpringBootTest;
import org.springframework.test.context.ActiveProfiles;

import jakarta.validation.ConstraintViolation;
import jakarta.validation.Validator;

rponte

fair, fine grained, and deadlock free locking

first, a spin lock

you know what a spinlock is, right?

here's a spinlock:

rponte

# Brilliant one-liner

(echo "PID COMMAND PORT USER"; lsof -i -P -n | grep LISTEN | awk '{print $2, $1, $9, $3}' | sort -u | head -n 50; echo;) \
 | column -t \
 | llm "what servers are running on my machine and do some of them look like they could be orphaned things I can shut down"
 
 
 # Maybe even more brilliant one liner
 
 (echo "PID COMMAND PORT USER"; lsof -i -P -n | grep LISTEN | awk '{print $2, $1, $9, $3}' | sort -u | head -n 50) \

rponte

package base;

import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

import java.io.File;
import java.io.FileWriter;
import java.io.IOException;
import java.nio.file.Files;
import java.nio.file.Path;

rponte

package br.com.rponte.sample.ssh;

import com.jcraft.jsch.ChannelExec;
import com.jcraft.jsch.JSch;
import com.jcraft.jsch.Session;

import java.io.BufferedReader;
import java.io.InputStream;
import java.io.InputStreamReader;
import java.nio.file.Path;

rponte

-- (This code was run in PostgreSQL 9.6.1)
-- Demonstration of how serializable isolation for PostgreSQL, which detects possible
-- interference between concurrent transactions, can produce false positives

-- in psql, create the following table

CREATE TABLE users(
  id SERIAL NOT NULL PRIMARY KEY,
  username VARCHAR NOT NULL
);

rponte

Interesting articles and content about data partitioning

Slotted Counter Pattern

Some articles and tips about Slotted Counter Pattern:

• PostgreSQL Lock Contention For Frequently Updated Rows
  • Example of how partitioning a counter can improve throughput without giving up locks
• PlanetScale: The Slotted Counter Pattern
• Hacker News: The Slotted Counter Pattern