/explore
|
You are here 
|
codeinthehole.com | ||
| | | | |
simonwillison.net
|
|
| | | | | For the last few years I've been trying to center my work around creating what I consider to be the Perfect Commit. This is a single commit that contains all ... | |
| | | | |
www.aleksandrhovhannisyan.com
|
|
| | | | | It can be tempting to lump unrelated code changes into a single commit, but this makes it difficult to debug and time travel in Git. Prefer to write atomic commits that have a single responsibility. | |
| | | | |
di.nmfay.com
|
|
| | | | | analyzing the organization-wide impact of database schema changes, as a service | |
| | | | |
archive.qconsf.com
|
|
| | | Debezium (noun | de·be·zi·um | /d?:?b?:zi?m/) - Secret Sauce for Change Data Capture Apache Kafka is a highly popular option for asynchronous event propagation between microservices. Things get challenging though when adding a services database to the picture: How can you avoid inconsistencies between Kafka and the database? Enter change data capture (CDC) and Debezium. By | ||
