posts/well_designed_code_is_easy_to_delete

I mostly wanted to avoid utterances app, and see if this appears on the blog. But also, nice article.

What are some things you think can help with ensuring code can be deleted, replaced outside of OpenAPI?

I Really like queueing technologies for this, because I can leave publishing as-is, and setup new consumers without loss of data. That can be as simple as any queue service buffering between services, or with persistent / durable queues such as EventStore or Kinesis with DataStreams, you can move a read head for a consumer, and add a new consumer at the very first message / event.

https://blacksheepcode.com/posts/well_designed_code_is_easy_to_delete