Henning Rohdeherohde.hashnode.net·Jan 7, 2023FeaturedThe Overuse of MicroservicesEvery programmer knows not to use monolithic architectures, and microservices have become the default choice for distributed systems. Smaller is better, to a limit: a config microservice; a microservice to abstract database access; a microservice for...Marvin Kweyu and 4 others are discussing this5 people are discussing thisDiscuss·64 likes·2.4K readsatomicityThanks for the article. I have had countless arguments with colleagues over this as well. Most times, a monolithic approach is perfect for a solution and one doesn't need to overengineer 10
Tobi Ojuolapetobiojuolape.hashnode.net·Apr 1, 2023A Comprehensive Guide to Lightning’s Atomic Multipath Payments (AMP)Introduction The Lightning network seamlessly facilitates small payments (micropayments) on Bitcoin as traditional Bitcoin transactions typically had a longer confirmation time and could incur huge fees for small transactions. This focus on micropaym...Discuss·10 likes·478 readsMastering Bitcoin and Lightninglightning network
Henning Rohdeherohde.hashnode.net·Jan 24, 2023The Next 700 Stateless ServicesIn today's public cloud age, few distributed services use local disks directly. Instead, they delegate their data durability needs to some infrastructure that ultimately does, usually a distributed SQL database or message broker. Practically all clou...Discuss·2 likes·49 readsarchitecture
Tobi OjuolapeforTobi's Dev Log ✌🏼tobiojuolape.hashnode.net·Apr 1, 2023A Comprehensive Guide to Lightning’s Atomic Multipath Payments (AMP)Introduction The Lightning network seamlessly facilitates small payments (micropayments) on Bitcoin as traditional Bitcoin transactions typically had a longer confirmation time and could incur huge fees for small transactions. This focus on micropaym...Discuss·10 likes·478 readsMastering Bitcoin and Lightninglightning network
Henning RohdeforSoftware Engineering Blogherohde.hashnode.net·Mar 25, 2023The Caching TrapReliable distributed systems are notoriously difficult to architect. Even somewhat standardized designs, such as stateless microservices, require navigating numerous pitfalls when converting theory into practice. As discussed in a previous article, T...Discuss·1 likeGeneral Programming
Georgios Komninosforgosom.hashnode.net·Mar 25, 2023Managing Distributed Transactions in PostgreSQL and Golang using two phase commitIf you're building a distributed system with PostgreSQL as the database backend, you might have encountered issues with managing transactions across multiple nodes. When a transaction spans multiple databases, ensuring atomicity and consistency can b...Discuss·107 readsGo Language
Henning RohdeforSoftware Engineering Blogherohde.hashnode.net·Jan 24, 2023The Next 700 Stateless ServicesIn today's public cloud age, few distributed services use local disks directly. Instead, they delegate their data durability needs to some infrastructure that ultimately does, usually a distributed SQL database or message broker. Practically all clou...Discuss·2 likes·49 readsarchitecture
Henning RohdeforSoftware Engineering Blogherohde.hashnode.net·Jan 7, 2023FeaturedThe Overuse of MicroservicesEvery programmer knows not to use monolithic architectures, and microservices have become the default choice for distributed systems. Smaller is better, to a limit: a config microservice; a microservice to abstract database access; a microservice for...Marvin Kweyu and 4 others are discussing this5 people are discussing thisDiscuss·64 likes·2.4K readsatomicityThanks for the article. I have had countless arguments with colleagues over this as well. Most times, a monolithic approach is perfect for a solution and one doesn't need to overengineer 10
