Backend

Most backend systems eventually need to produce documents: invoices, reports, offers, letters, CVs, certificates, export packs. The business treats those documents as serious output. They are sent to customers, attached to applications, used by operations teams, and archived for compliance. The code that produces them often does not get the same respect. This is the companion to What Drove Me to Build GraphCompose — that post was the personal story of how GraphCompose started. This one is about a claim I now believe after living inside that code: document generation is backend infrastructure, and it pays off when you build it like infrastructure instead of like a one-off script. ...

I decided to create a personal blog because I often have thoughts that are too large for a quick note and too useful to leave only in my head. My name is Artem Demchyshyn. I am a Ukrainian Java Backend Developer based in London. My work is mostly around backend systems, Java, Spring Boot, APIs, databases, product logic, and the practical engineering decisions that make software reliable. But this blog is not only about code. ...