Steve Taylor - Tracking microservices in your CI/CD Pipeline
Playback access may have expired or the stream is unavailable. Reload the page to request fresh access.
Another tab is open for this lesson. You can keep watching here; the newest position wins.
Saved position may be approximate: the browser clock disagreed with the server.
Your free preview has ended
Create a free account to finish this lesson, or subscribe for the full library.
Your viewing record
No viewing recorded yet. Press play; your position is saved about every 10 seconds.
Last viewed . Last position —.
Completion
Based on 0:00 of unique watched video. Repeats and skipped parts do not increase it.
If you have adopted CI/CD for your monolithic practices, in this interview we will discuss how to enhance your pipeline to handle the complexities of microservices.
As we move into microservices, we move away from a traditional check-out and build a continuous integration process where an application binary is created and versioned.
We are faced instead with managing independently deployed microservices across the dev, test, and prod states, where the ‘link’ so to speak is done via APIs and runtime.
In this interview, we will explore how to include Ortelius for managing microservices into your CI/CD pipeline. We will cover the maintenance of a ‘logical application’ view and version, bill of material reporting, difference reports, and a ‘blast radius’ report showing the impact a single microservice update could make to any single cluster.
Comments (0)
Log in to join the discussion.
No comments yet. Be the first to comment.