InfoQ Homepage Architecture & Design Content on InfoQ
-
/articles/service-mesh-ultimate-guide-2021/en/smallimage/logo-1630968100375.jpg)
Service Mesh Ultimate Guide 2021 - Second Edition: Next Generation Microservices Development
Get up to speed on the adoption of service mesh. Learn how to deploy service mesh solutions in heterogeneous infrastructures and application/service connectivity.
-
/articles/reduce-technical-debt/en/smallimage/logo-1630929110479.jpg)
Technical Debt Isn't Technical: What Companies Can Do to Reduce Technical Debt
In this article, three experts discuss some of the key findings of the “State of Technical Debt 2021” report including the impact of technical debt on engineering teams, the pros and cons of dealing with maintenance work continuously, the future of technical debt and what each engineering teams can do to communicate the importance of dealing with technical debt to companies’ leadership.
-
/articles/cloud-native-architecture-adoption-part3/en/smallimage/adoption-cloud-native-architecture-part-3-logo-small-1630316844867.jpg)
Adoption of Cloud Native Architecture, Part 3: Service Orchestration and Service Mesh
This part 3 article in Cloud Native Architecture Adoption series, explores service interaction in a microservices based architecture, typical challenges we experience in distributed systems without proper governance, and how patterns like service orchestration and service mesh can help address those challenges.
-
/articles/pitfalls-patterns-microservice-dependency-management/en/smallimage/pitfalls-and-patterns-in-microservice-dependency-management-small-image-1630081386094.jpg)
Pitfalls and Patterns in Microservice Dependency Management
Silvia Esparrachiari shares stories on how a small change can impact a system, discussing the importance of having a broad view of a system to better understand how a change can impact a system. She presents three different scenarios that changed related to dependency management in an environment of microservices, all based on situations that she encountered while working at Google.
-
/articles/auth-layer-auth0-hasura/en/smallimage/logo-1629735628854.jpg)
Bootstrapping the Authentication Layer and Server with Auth0.js and Hasura
When you're trying to prototype an MVP for your app and want to start iterating quickly, the upfront cost of setting up authentication can be a massive roadblock. The authentication layer requires significant work, and you must always be on the lookout for security vulnerabilities.
-
/articles/consistency-coupling-complexity/en/smallimage/consistency-coupling-complexity-s-1628577348640.jpg)
Consistency, Coupling, and Complexity at the Edge
Successful use of a microservices architecture requires maintaining a clear separation of concerns in the various layers and by employing design principles best suited to each layer. While RESTful API design has become the standard for microservices, it can cause problems at the UI layer. Alternatives such as the Backend-for-Frontend pattern using GraphQL can provide better separation of concerns.
-
/articles/java-16-new-features/en/smallimage/what-is-new-java-16-small-image-1628078662649.jpg)
What's New in Java 16
Java 16 was released in March of 2021 as a GA build meant to be used in production. And Java 17, the next LTS build, is scheduled to be released this September. Java 17 will be packed with a lot of improvements and language enhancements, most of which are a culmination of all the new features and changes that have been delivered since Java 11.
-
/articles/microservices-inside-out/en/smallimage/turning-microservices-inside-out-small-image-1627634447180.jpg)
Turning Microservices Inside-Out
Turning microservices inside-out means moving past a single, request/response API to designing microservices with an inbound API for queries and commands, an outbound APIs to emit events, and a meta API to describe them both. A database can be supplemented with Apache Kafka via a connecting tissue such as Debezium.
-
/articles/github-monolith-microservices/en/smallimage/gitHub-journey-from-monolith-to-microservices-small-image-1627307383403.jpg)
GitHub’s Journey from Monolith to Microservices
This article explores GitHub's recent journey towards a microservices architecture. It takes a deeper look at GitHub’s historical and current state, goes over some internal and external factors, and discusses practical consideration points in how Github tackled their migration, including key concepts and best practices of implementing microservices architecture.
-
/articles/netops-secops-closing-gap/en/smallimage/bridge-the-gap-NetOps-SecOps-network-management-security-small-image-1627039022447.jpg)
How to Bridge the Gap between Netops and Secops for Ultimate Network Management and Security
Sometimes it can seem like a new IT management paradigm arrives every week. First, we had DevOps; then DevSecOps; now the most innovative organizations are talking about AIOps and even NetAIOps. Yet what is often forgotten about in this rush to name new ways of working is that many of them have been in place in the best-run teams for decades - a great example of this is NetOps and SecOps.
-
/articles/cloud-consolidate-on-prem/en/smallimage/leverage-the-cloud-on-prem-systems-small-image-1626702451636.jpg)
Leverage the Cloud to Help Consolidate On-Prem Systems
A cloud model can be used to architecturally validate the possibility of consolidating multiple application servers into a smaller number of physical resources that will ultimately remain on-prem.
-
/articles/from-design-systems-design-apis/en/smallimage/why-design-systems-need-apis-small-image-1626343329771.jpg)
Why Design Systems Need APIs - Q&A with Louis Chenais, Chief Evangelist at Specify
Design systems exist for their business value: to help organizations reach brand consistency across many platforms like the web, Android, or iOS. Design APIs strive to connect the consumers and the contributors of a design system through the tools they use on a daily basis.