InfoQ Homepage Microservices Content on InfoQ
-
Uncover What's Next for Software Engineering at QCon Plus Online Software Conference (Nov 1-12)
QCon Plus gives you access to a curated learning experience that covers the topics that matter right now in software development and technical leadership. Learn from the laser-focus sharing experiences of 64+ software practitioners from early adopter companies to help you adopt the right patterns and practices.
-
Quarkus 2.0 Delivers Continuous Testing, CLI and Supports Minimal JDK 11
Red Hat has released Quarkus 2.0 with new features such as continuous testing, a new CLI, and developer services. This version upgrades its core as well, moving to JDK 11, Vert.x 4.0 and MicroProfile 4.0, promising to have a seamless upgrade experience. InfoQ reached out to the Quarkus’ core team members to provide a brief description on the benefits of each newly-added feature in Quarkus 2.0.
-
Distributed DevOps Teams: Enabling Non-Stop Delivery
Keeping in touch and being cohesive as a distributed team is a challenge many face. Assigning stories from a shared backlog helped a distributed team in doing non-stop delivery, as did giving all members of the team the authority to promote to production and back-out code at need. You need to give attention to the architecture to prevent creating similar or duplicate micro-services.
-
QCon Plus November 2021 is Now Hybrid. Attend Online and In-Person (NY & SF)
The QCon Plus software development conference will be back November 1-5, 2021 - online and in-person. Get the chance to engage and network with professionals driving change and innovation inside the world’s most innovative software organizations.
-
The Road to Quarkus 2.0: Continuous Testing
Quarkus continues its effort to make Java enterprise applications as efficient as possible, both from the perspective of its run time, resources, start and terminate time and now also from the development of applications. Quarkus 2.0 will enrich its dev mode with the continuous testing capability. Stuart Douglas, the senior principal engineer working on it, provides us with an overview.
-
Jolie - a Service-Oriented Programming Language for Distributed Applications
The Jolie programming language recently attracted the attention of developers on Hacker News. Jolie is a service-oriented language that encourages developers to model distributed software as composable services whose orchestration is described separately from communication protocols (SOAP, HTTP, XML-RPC) and deployment architecture. Jolie adopts services as a first-class concept.
-
Alibaba Cloud Uses Dapr to Support Its Business Growth
In a recent blog post, Sky Ao, a staff engineer at Alibaba Cloud, details how Alibaba Cloud uses the Distributed Application Runtime (Dapr) to support its business growth. As Alibaba's business rapidly grows while also purchasing other companies, a clear need to support multiple programming languages across varying cloud environments rises. To support this need, Alibaba chose to use Dapr.
-
Vamp Announces Results of State of Cloud-Native Release Orchestration 2021
Vamp.io, a company providing a release automation platform, recently published the State of Cloud-Native Release Orchestration 2021 survey results. Results show that Kubernetes and microservices are popular, and high-risk release strategies are still being used.
-
Dropbox Reveals Atlas - a Managed Service Orchestration Platform
In a recent blog post, Dropbox revealed Atlas, a platform whose aim is to provide various benefits of a Service Oriented Architecture while minimizing the operational cost of owning a service. Atlas' goal is to support small, self-contained functionality, saving product teams the overhead of managing a full-blown service, including capacity planning, alert setup, etc.
-
Netflix Embraces GraphQL Microservices for Rapid Application Development
Netflix engineering recently published a blog post detailing how Netflix embraced GraphQL microservices for rapid application development. In this post, Dane Avilla, a senior software engineer at Netflix, describes their key learnings in the process and how GraphQL lends itself well for proof-of-concept development.
-
Distributed Application Runtime (Dapr) v1.0 Announced
The Distributed Application Runtime (Dapr) team announced today that Dapr v1.0 is now available and is considered production-ready. Dapr is an open-source runtime that allows developers to build resilient, microservices-based applications that run on the cloud and edge. With the v1.0 release, developers can deploy Dapr applications to Kubernetes clusters in production scenarios.
-
The Journey from Monolith to Microservices at GitHub: QCon Plus Q&A
GitHub needed to fundamentally rethink how they did software development due to all of the different cultures, norms, and technology stacks that their teams brought to the table. They are migrating toward a microservices architecture that enables different teams and systems and technologies to work harmoniously together.
-
Netflix Implements GraphQL Federation at Scale
Netflix has successfully implemented a federated GraphQL API at scale. In a recent blog post series, engineers from Netflix describe their journey and the lessons learned in the process. With GraphQL federation, the API gateway implementation is distributed to backend teams owning the individual domain services they implement instead of centrally developed as part of the API gateway.
-
The Challenges of End-to-End Testing of Microservices
Microservices work well with independent teams who have end-to-end responsibility and use an automated CI/CD pipeline. Ensuring software quality through end-to-end testing can conflict with rapidly integrating and releasing software components. If an end-to-end test fails, the CI/CD pipelines of all involved microservices are blocked until the problem causing the test to fail is solved.
-
Data Mesh Principles and Logical Architecture Defined
The concept of a data mesh provides new ways to address common problems around managing data at scale. Zhamak Dehghani has provided additional clarity around the four principles of a data mesh, with a corresponding logical architecture and organizational structure.