InfoQ Homepage Architecture Content on InfoQ
-
Culture & Methods Trends Report March 2021
The most significant impact on culture and methods in 2021 is the disruption caused by COVID-19. We look at what's needed for good remote and the impact of bad remote, how management practices are evolving, and the importance of people skills for technologists. Paying attention to ethical issues, diversity and inclusion, tech for good, employee experience and psychological safety are important.
-
Serverless Functions for Microservices? Probably Yes, But Stay Flexible to Change
When designing cloud-native systems, it is important to accommodate freedom to change deployment strategy, from FaaS to containers or VMs, for potentially significant savings on cloud bills.
-
Blockchain Node Providers and How They Work
In this article, we will review the concept of a blockchain node, the problems a developer might face while deploying a node, and the working principle of Blockchain-as-a-Service providers, which simplify the integration of the blockchain into products, maintaining wallets, or keeping the blockchain in sync.
-
Saga Orchestration for Microservices Using the Outbox Pattern
The outbox pattern, implemented via change data capture, is a proven approach for addressing the concern of data exchange between microservices. The saga pattern, as demonstrated in this article, is useful for data updates that span multiple microservices.
-
The Future of Data Engineering
Chris Riccomini examines the current and future states of the art in data pipelines, data streaming, and data warehousing. He presents a six-stage evolution that data ecosystems follow, from a simple monolith to a complex data-microwarehouse architecture as the data engineers who manage them solve problems and clarify their roles as infrastructure engineers, rather than data stewards.
-
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.
-
Who is on the Team?
Ahmad Fahmy and Cesario Ramos take the changes to the new Scrum Guide as an opportunity to explore what it means to be "on a team." They draw on research to create an ACID test to differentiate who is on the team and who isn't. They discuss different mental models around the idea of a team with the hopes that you take this opportunity to discuss and elevate the roles within your organization.
-
Testing Quarkus Web Applications: Component & Integration Tests
Quarkus is a full-stack, Kubernetes-native Java framework made for Java virtual machines (JVMs) and native compilation. Instead of reinventing the wheel, Quarkus uses well-known enterprise-grade frameworks backed by standards/specifications and makes them compilable to a binary using Graal VM. This article focuses on using some of the Quarkus testing facilities.
-
The Evolution of Precomputation Technology and its Role in Data Analytics
In this article, author Yang Li discusses the importance of precomputation techniques in databases, OLAP and data cubes, and some of the trends in using precomputation in big data analytics.
-
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.
-
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.
-
Adaptive Frontline Incident Response: Human-Centered Incident Management
The third article in a series on how software companies adapted and continue to adapt to enhance their resilience zeros in on the sources that comprise most of your company’s adaptive resources: your frontline responders. In this article, we draw on our experiences as incident commanders with Twilio to share our reflections on what it means to cultivate resilient people.