GoCracow #17 - designing error codes, TSDB in Go, PGO

Announcing next GoCracow meetup! We're thrilled to have Splunk a Cisco company as our host!

The meetup is going to take place in the new Splunk Kraków Office which is located in High 5ive FOUR, 2nd floor (Pawia 21, Kraków). We recommend entering the building from the northern entrance. Someone with Cisco badge should help you entering the office.

Info: Register yourself at the office’s reception. Please do not come at the last moment.

Info: Most APIs end up with a graveyard of ad-hoc error messages and random HTTP status codes. This talk shows how to model domain errors explicitly—making business rules like “insufficient funds” or “portfolio not found” first-class concepts—and then map them cleanly into HTTP responses. We’ll cover patterns for error types, codes, and payloads, how to keep domain logic free from transport details, and how a good error design makes debugging, observability, and client integrations dramatically less painful.

Info: Time series data generated by monitoring systems is usually measured in millions of samples per second. To keep up with the load, TimeSeries database needs to be as efficient with resources as possible. The talk will review performance optimizations we learned while writing a TSDB from scratch.

Info: The Go compiler is incredibly smart, but it usually operates in the dark - optimizing code without knowing how it actually runs in the real world. In this talk, we will explore how to "nudge" the compiler to its best using production profiles, guiding it to make better optimization decisions that yield "free" performance improvements.

Info: Max 5 min per lightning talk + Q&A.

Know what’s Happening Next — before everyone else does.

Get App

Host or Publisher GoCracow