InfoQ Homepage Microservices Content on InfoQ
-
/articles/redhat-release-quarkus-1-0/en/smallimage/Quarkus-a-Kubernetes-Native-Java-Framework-Reaches-Version-1.0-logo-1575365421309.jpg)
Quarkus, a Kubernetes Native Java Framework, Reaches Version 1.0: Q&A with Thomas Qvarnstrom
Quarkus, a Kubernetes native Java framework tailored for GraalVM and OpenJDK HotSpot, has reached version 1.0. Quarkus is an Open Source stack for writing Java applications, offering unparalleled startup time, memory footprint and developer experience. InfoQ spoke with Thomas Qvarnstrom, senior principal product manager at Red Hat, in order to learn about the Quarkus journey, extensions, and more.
-
/articles/cloud-native-architecture-adoption-part1/en/smallimage/adoption-cloud-native-architecture-part-1-logo-1574756652648.jpg)
Adoption of Cloud-Native Architecture, Part 1: Architecture Evolution and Maturity
In this article, authors Srini Penchikala and Marcio Esteves discuss what organizations should assess when adopting cloud native architectures for hosting their applications on cloud. It focuses on architecture hosting models. They also discuss how architecture patterns like microservices, containers, serverless, and service mesh can help with organizational adoption of cloud native solutions.
-
/articles/tyler-treat-observability/en/smallimage/microservice-observability-tyler-treat-logo-small-1574349954703.jpg)
Q&A with Tyler Treat on Microservice Observability
Tyler Treat attempts to disambiguate the concepts of Observability and Monitoring. He discusses how the complexity of elastic systems produces more unknowns that require a discovery-based approach. InfoQ recently sat down with Treat to discuss the topics of observability and monitoring, and he shares some challenges and best practices when introducing observability concepts.
-
/articles/testing-techniques-microservices-use-cases/en/smallimage/testing-microservices-part-3-logo-small-1572849393575.jpg)
Testing Microservices: Six Case Studies with a Combination of Testing Techniques - Part 3
This article presents six real world use cases of testing microservice-based applications, and demonstrates how a combination of testing techniques can be evaluated, chosen, and implemented.
-
/articles/twelve-testing-techniques-microservices-tradeoffs/en/smallimage/twelve-testing-techniques-microservices-tradeoffs-logo-1568716442005.jpg)
Testing Microservices: Examining the Tradeoffs of Twelve Techniques - Part 2
A successful microservice testing strategy must effectively manage the interdependent components involved. This article presents the tradeoffs for twelve testing techniques. Each approach has advantages and disadvantages. Which technique, or blend of techniques, should be used for your application, depends on your context.
-
/articles/cellery-code-first-kubernetes/en/smallimage/cellery-code-first-kubernetes-l-1566554395052.jpg)
Cellery: A Code-First Approach to Deploy Applications on Kubernetes
Cellery is a code-first approach to building, integrating, running, and managing composite applications on Kubernetes, using a cell-based architecture. Learn what cells are, how Cellery works, and see how an existing Kubernetes application written by Google can be deployed, managed, and observed using Cellery.
-
/articles/engineers-guide-to-sleep/en/smallimage/logo-1565941207544.jpg)
An Engineer’s Guide to a Good Night’s Sleep
Increased microservices adoption, fueled by the move to the cloud where architectures and infrastructure can flex and be ephemeral, adds complexity every day to the systems we create and maintain. This takes place alongside operating models with autonomous and totally empowered teams, so each distributed system has its own tapestry of technical approaches, languages, and services.
-
/articles/twelve-testing-techniques-microservices-intro/en/smallimage/twelve-testing-techniques-microservices-intro-s-1565852740949.jpeg)
Testing Microservices: an Overview of 12 Useful Techniques - Part 1
When building a microservice system, you will need to manage inter-dependent components in order to test in a cost and time effective way. You can use test doubles in your microservice tests that pretend to be real dependencies for the purpose of the test. However, there are many options for implementing this. This article provides an overview and tradeoffs of 12 techniques.
-
/articles/kubernetes-workloads-serverless-era/en/smallimage/logo-1564662062598.jpg)
Kubernetes Workloads in the Serverless Era: Architecture, Platforms, and Trends
Explore how microservices architecture has evolved into cloud-native architecture, where many of the infrastructure concerns are provided by Kubernetes in combination with additional abstractions provided by service mesh and serverless frameworks. In addition, the serverless ecosystem is evolving by exploring standard and open packaging, runtimes, and event formats.
-
/articles/java-jvm-trends-2019/en/smallimage/InfoQ-Trend-Report-Java2019-s-1563268318310.jpg)
Java InfoQ Trends Report - July 2019
The InfoQ Java trend report provides an overview of technology adoption and commentary on how we see the Java and JVM-related space evolving in 2019. Key developments include the release of Java 13, the rise of non-HotSpot JVMs and the evolution of GraalVM, and the changing landscape of Java microservice frameworks.
-
/articles/evolve-devops-devsecops/en/smallimage/How-to-Seamlessly-Evolve-DevOps-into-DevSecOps-logo-small-1561367768393.jpg)
How to Seamlessly Evolve DevOps into DevSecOps
As DevOps evolved, it became obvious that it was about more than just software development and operations management. With each new story of a massive data breach and its catastrophic consequences, cybersecurity swiftly became recognized as a critical part of any IT ecosystem. This realization led to DevSecOps. This article looks at how to embrace a DevSecOps approach.
-
/articles/obscuring-complexity/en/smallimage/obscuring-complexity-s-1560786483000.jpeg)
Obscuring Complexity
One of the most important things that software architects do is manage the complexity of their systems in order to mitigate release disruption while maintaining sufficient feature velocity. When we cannot reduce complexity, we try to hide or shift it. Software architects tend to manage that complexity with the time-honored strategies covered in this article.