InfoQ Homepage Distributed Systems Content on InfoQ
-
/articles/rmi-to-websocket/en/smallimage/migrate-a-RMI-based-legacy-application-to-WebSocket-small-1680106723513.jpg)
Migrate a RMI-Based Legacy Application to WebSocket
Technical debt, especially in enterprise software, is a relevant problem that developers recurrently have to face. This article provides a use case related to removing technical debt in a large enterprise application based on an old fashioned Remote Method Invocation (RMI) protocol, and migrating it toward modern cloud-aware communication technologies.
-
/articles/mva-distributed/en/smallimage/logo-1663312791288.jpg)
Location, Location, Location: MVA Considerations for Distributed Processing and Data
Even when designing a Minimum Viable Architecture (MVA), developers must consider resource location, especially when mobile apps are part of a distributed system. Distributing the data and processing can introduce new challenges if location is not part of the decision-making criteria.
-
/articles/microservices-seven-fail/en/smallimage/logo-1644492934255.jpg)
Seven Ways to Fail at Microservices
At QCon Plus last November, I presented some of the ways microservices can go wrong. I’m a consultant for IBM, and part of my job is helping businesses get cloud-native. These problems are based on my experience – which, unfortunately, I see repeatedly in the field.
-
/articles/blockchain-forensic-monitoring-xdpos2/en/smallimage/logo-1635366051273.jpg)
Forensic Monitoring of Blockchains is Key for Broader Industry Adoption
This article presents a new blockchain consensus mechanism, XinFin Delegated Proof-of-Stake Consensus Protocol 2.0, that provides a higher level of trust by creating an efficient judiciary system. It has been designed to keep all verifying nodes accountable and allow for bad actors to be identified and effectively neutralized.
-
/articles/reliable-systems-chaos-engineering/en/smallimage/chaos-engineering-logo-1622797752597.jpg)
Building Reliable Software Systems with Chaos Engineering
Advances in large-scale, distributed software systems are changing the game for software engineering. As an industry, we are quick to adopt practices that improve flexibility and improve feature velocity. If we can move quickly, can we do so without breaking things? Chaos Engineering practices can be used to navigate complexity and build more reliable systems.
-
/articles/cloud-trust-fail/en/smallimage/can-we-trust-cloud-not-to-fail-small-1620291566105.jpg)
Can We Trust the Cloud Not to Fail?
I will start with the theory behind failure detection, and then review a couple of real-world examples of how the mechanism works in a real cloud - on Azure. Even though this article includes real-world applications of failure detection within Azure, the same notions could also apply to GCP, AWS, or any other distributed system.
-
/articles/distributed-systems-kubernetes/en/smallimage/logo-1616433026924.jpg)
The Evolution of Distributed Systems on Kubernetes
At QCon in March, Bilgin Ibryam, product manager at Red Hat, gave a talk on the evolution of distributed systems with Kubernetes. You might have an answer to that, and Ibryam has one too. At the end of the article, you will find out what he thinks the answer will be.
-
/articles/microservices-from-trenches-lessons-challenges/en/smallimage/ivj9ss0o-1613044026543.jpeg)
Microservices from the Trenches: Lessons, Benefits, Challenges, and Mistakes
Nicky Wrightson, from Skyscanner, hosted a panel at QCon London with participants who have moved from the monolith to microservices and in some cases back again. They share their experience with microservices on production, and also strong opinions on monorepos, on operating distributed systems, and on the best way to structure an organization to make a success of this architecture.
-
/articles/migrating-monoliths-to-microservices-with-decomposition/en/smallimage/micreoservices-logo-1612542776368.jpeg)
Migrating Monoliths to Microservices with Decomposition and Incremental Changes
Microservices migrations are not a trivial change. You have to think carefully about whether or they're right for you. Maybe a monolith would be enough for your context and business needs. In this article, Sam Newman shares some decomposition and incremental changes patterns that can help you to evaluate and migrate to a microservices architecture.
-
/articles/hive-performance-tuning-techniques/en/smallimage/data-table-s-1612367270351.jpeg)
Performance Tuning Techniques of Hive Big Data Table
In this article, author Sudhish Koloth discusses how to tackle performance problems when using Hive Big Data tables.
-
/articles/go-language-13-years/en/smallimage/go-language-anniversary-steve-francia-logo-small-1609168280799.jpg)
Go Language at 13 Years: Ecosystem, Evolution, and Future in Conversation with Steve Francia
Go was started more than a decade ago in the Engineering department at Google. It was designed with the purpose of providing an easy-to-learn programming language that would allow to develop Google's systems at the next level. In the past decade, the language became more and more stable, currently being used for implementing some of the most popular tools on the web (Kubernetes, Terraform etc.).
-
/articles/2020-recap-best-posts/en/smallimage/2020-recap-100px-1608641842348.jpg)
InfoQ 2020 Recap, Editor Recommendations, and Best Content of the Year
As 2020 is coming to an end, we created this article listing some of the best posts published this year. This collection was hand-picked by nine InfoQ Editors recommending the greatest posts in their domain. It's a great piece to make sure you don't miss out on some of the InfoQ's best content.