InfoQ Homepage Microservices Content on InfoQ
-
How Meta Uses Privacy-Friendly Credentials in De-Identified Authentication
Meta uses authentication to protect its service’s endpoints against abusive usage. Post-processing access data to remove personally identifiable information is an approach they found too resource-intensive. An article was published recently explaining how Meta leveraged de-identified authentication to protect their services and their user’s privacy at the same time.
-
Building Resiliency into the Twitter Ad Pacing Service
Twitter’s ad pacing algorithms were initially part of an ad-serving monolith. Later, Twitter’s engineering extracted them into a separate service to facilitate its development. Being an important service, it needs to be very reliable. An article was published recently describing how they built a reliable service by making economical design choices on managing different failure scenarios.
-
Scaling and Automating Microservice Testing at Lyft
Lyft used cloud-based isolated environments for several purposes, including end-to-end testing. As the number of microservices increased, tests using these environments became harder to scale and lost value. Recent articles describe how Lyft shifted to testing using request isolation in a shared staging environment and used acceptance tests to gate production deployments.
-
Uber's Engineering Manages to Cut 70k CPUs by Tuning Go GC
In an effort to help the company become profitable, Uber’s engineering department has focused their efforts on making their infrastructure more efficient. As an outcome of this effort, they managed to develop a semi-automated GO Garbage Collection tuning mechanism which in turn saved 70K CPU cores across 30 mission critical services.
-
QCon Software Development Conferences: Seven Tracks Not to Miss
Why are micro-frontends important? How should you optimise your organisational architecture for speed and flow? How to make microservices successful? Have you ever wondered how well-known tech companies can seamlessly deliver an exceptional user experience while supporting millions of users and billions of transactions? Looking for new processes and best software practices?
-
Quine Aims to Simplify Event Processing on Data in Motion
Developed at thatDot, Quine is an open source streaming graph solution aimed at high-volume event processing. Quine combines graph data and streaming technologies to enable the creation of real-time, complex event processing workflows at scale, says thatDot.
-
Service Overload Detection and Remediation at LinkedIn
LinkedIn recently published how it handles overload detection and remediation in its microservices. Its solution, Hodor, provides an adaptive solution that works out of the box with no configuration. It is a platform-agnostic mechanism to run overload detectors and load shedders inside the monitored process that samples load and sheds traffic from within the application's processing chain.
-
Scaling Video Quality Measurements at Netflix with Cosmos
Netflix relies heavily on measuring perceptual video quality for different business purposes. As metrics evolve and become part of more workflows, their measurement tool needs to scale too. Netflix recently described how a new video quality measurement workflow was implemented using Cosmos microservices to foster innovation in quality metrics, with good scalability and loose data coupling.
-
Microservice Calls’ Critical Path Analysis with Jaeger and Uber’s CRISP
Discovering which services need to be optimised to reduce end-to-end latency in a microservices-based system can be challenging because call graphs may be too complicated to read. Uber described an open-source tool called CRISP built to solve this problem by finding the critical paths in these graphs. These paths identify those operations whose optimisation benefits the overall system.
-
Dapr Joins CNCF Incubator: Q&A with Yaron Schneider
The Cloud Native Computing Foundation (CNCF) recently announced that it accepted the Distributed Application Runtime (Dapr) as a CNCF incubating project. This statement follows an earlier announcement by Dapr, announcing the formation of the Dapr project's Steering and Technical Committee (STC).
-
Domain-Driven Design with Value-Added Services and Domain Gateways at SoundCloud
Two articles were recently published to describe SoundCloud’s service architecture evolution towards implementing Domain Gateways, with a stop at Value-Added Services on the way. The authors describe how these Domain-Driven Design-based patterns helped reduce duplications and homogenise business and authorisation logic.
-
Micronaut 3.0 Delivers Significant Changes Adaptable for Future Development
Object Computing, Inc. has released Micronaut 3.0 featuring the removal of a default reactive streams implementation, a change in annotation inheritance, and HTTP compile-time validation. This release was a culmination of work to resolve design faults of the past to make the framework more intuitive and adaptable to future requirements.
-
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.