# Lifecycle Published articles for Lifecycle. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Why Kafka retention.ms can delay message deletion DevFeed: [Why Kafka retention.ms can delay message deletion]() Original publisher: [Read original article]() Author: Rogerio Santos Published: 2026-09-16T13:05:06Z Content type: tutorial Language: en Sources: [Red Hat](), [Red Hat Developer]() Topics: [Kafka](), [Apache-Kafka](), [configuration](), [file](), [Event-Streaming]() Tags: [broker](), [configuration](), [diagnose](), [event-driven](), [how-to](), [kafka](), [lifecycle](), [retention](), [storage](), [stream-processing]() ### AI overview This guide explains why Kafka messages can remain readable beyond a topic's retention.ms setting. Kafka deletes closed log segments rather than individual messages, and the active segment and continuous writes can delay removal of older records. ### Source excerpt A customer opened a support case with a deceptively simple complaint: a Kafka topic was configured with a 12-hour retention (retention.ms), yet messages produced on July 24 were still readable 4 days later, on July 28. Nothing was broken. The broker logged no errors. The retention policy was working as designed, but the segment layout and continuous write pattern delayed when the old records could actually be removed. The post Why your Kafka topic ignores retention.ms (and how to fix it) appeared first on Red Hat Developer. ## Cisco UCS Manager: Celebrating the legacy, shaping the future with Cisco Intersight DevFeed: [Cisco UCS Manager: Celebrating the legacy, shaping the future with Cisco Intersight]() Original publisher: [Read original article]() Author: Jacob Van Ewyk Published: 2026-09-15T21:00:37Z Content type: opinion Language: en Sources: [Cisco Blogs]() Topics: [Cisco](), [Server](), [Automation](), [configuration](), [API](), [legacy]() Tags: [api](), [automation](), [cisco](), [data-center](), [end-of-life](), [eol](), [infrastructure](), [legacy](), [lifecycle](), [management](), [server]() ### AI overview Cisco describes the legacy of Cisco UCS Manager and positions Cisco Intersight as the strategic platform for future Cisco UCS software management. The article also outlines announced end-of-sale and end-of-life milestones, including a planned Last Date of Support of December 31, 2030, subject to applicable contracts and service terms. ### Source excerpt Cisco UCS Manager shaped 17 years of infrastructure management. Now, with its end-of-life announced, Cisco Intersight carries that foundation forward with centralized visibility, automation, and scale. Learn the key dates for the UCS Manager EOL. ## September 09, 2026 DevFeed: [September 09, 2026]() Original publisher: [Read original article]() Published: 2026-09-09T17:00:00Z Content type: release Language: en Sources: [AndroidX Release Notes]() Topics: [Jetpack](), [releases](), [Release notes](), [Compose](), [Library]() Tags: [benchmark](), [compose](), [jetpack](), [latest-release](), [libraries](), [lifecycle](), [navigation](), [release-notes](), [room](), [security](), [sqlite](), [tracing](), [ui]() ### AI overview This Android developer page lists AndroidX library components across four release channels and provides recent release dates and version information. It also links to component release histories, archived release notes, and the current versions page. ### Source excerpt Activity Version 1.14.0-alpha02 Annotation Version 1.11.0-rc01 Benchmark Version 1.5.0 Car App Version 1.9.0-alpha02 Collection Version 1.7.0-alpha01 Compose Animation Version 1.12.1 Compose Animation Version 1.13.0-alpha03 Compose Foundation Version 1.12.1 Compose Foundation Version 1.13.0-alpha03 Compose Material Version 1.12.1 Compose Material Version 1.13.0-alpha03 Compose Material3 Version 1.5.0-alpha28 Compose Material3 Adaptive Version 1.4.0-alpha02 Compose Remote Version 1.0.0-alpha19 Compose Remote Foundation Version 1.0.0-alpha02 Compose Runtime Version 1.12.1 Compose Runtime Version 1.13.0-alpha03 Compose Ui Version 1.12.1 Compose Ui Version 1.13.0-alpha03 Core Uwb Version 1.1.0-alpha02 Credentials Providerevents Version 1.0.0-beta01 Datastore Version 1.3.0-alpha11 Emoji2 Version 1.7.0-rc01 Glance Adaptive Version 1.0.0-alpha02 Glance Wear Version 1.0.0-alpha18 Heifwriter Version 1.2.0-alpha02 Ink Version 1.1.0-alpha08 Lifecycle Version 2.12.0-alpha03 Mediarouter Version 1.9.0-alpha02 Navigation Version 2.10.1 Navigation3 Version 1.2.0-rc01 Room Version 2.8.5 Room3 Version 3.0.3 Room3 Version 3.1.0-alpha01 Savedstate Version 1.6.0-alpha03 Security Version 1.0.0 Security Version 1.1.0 Sqlite Version 2.7.1 Sqlite Version 2.8.0-alpha01 Tracing Version 2.0.2 Wear Compose Version 1.7.0-rc01 Wear Compose Remote Version 1.0.0-alpha11 Webkit Version 1.18.0-alpha01 Xr Arcore Version 1.0.0-rc01 Xr Glimmer Version 1.0.0-alpha19 Xr Projected Version 1.0.0-alpha12 Xr Runtime Version 1.0.0-rc01 Xr Runtime Version 1.1.0-alpha01 Xr Scenecore Version 1.0.0-rc01 ## How engineering teams can measure AI coding ROI with cost attribution and outcome metrics DevFeed: [How engineering teams can measure AI coding ROI with cost attribution and outcome metrics]() Original publisher: [Read original article]() Author: Kelsey Rosen Published: 2026-09-08T00:00:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [ai-coding](), [Ground truth / benchmark quality](), [coding](), [Finance]() Tags: [ai](), [ai-coding](), [analysis](), [blog](), [coding](), [cost](), [datadog](), [engineering](), [governance](), [harness](), [incident](), [lifecycle](), [measurement](), [metrics](), [numbers](), [production](), [team](), [tokens](), [tooling](), [workflow]() ### AI overview A Harness panel discussion outlines ways engineering organizations can measure AI coding ROI. The panel recommends attributing costs to specific work, combining throughput metrics with qualitative evidence, and using governance and process changes to interpret results. ### Source excerpt Harness panelists share practical strategies for measuring AI coding ROI, from granular cost attribution and lifecycle metrics to budgeting, governance. | Blog ## Week Ending August 30, 2026 DevFeed: [Week Ending August 30, 2026]() Original publisher: [Read original article]() Published: 2026-09-04T01:00:00Z Content type: news Language: en Sources: [Last Week in Kubernetes Development]() Topics: [Kubernetes](), [Open Source](), [observability](), [Cloud](), [Kubernetes v1.32]() Tags: [2026](), [cloud-native](), [developer](), [kubernetes](), [lifecycle](), [news](), [observability](), [open-source](), [release]() ### AI overview A weekly Kubernetes developer news roundup covering the Maintainer Summit schedule, the KubeCon Europe CfP, the 2026 Kubernetes Steering Committee election, KCD San Francisco Bay Area, the Kubernetes v1.38 release cycle, and recent StatefulSet observability and Dynamic Resource Allocation fixes. ### Source excerpt Developer News ## Building Trust in AI DevOps: Validating the Harness Knowledge Graph DevFeed: [Building Trust in AI DevOps: Validating the Harness Knowledge Graph]() Original publisher: [Read original article]() Author: Vikram Sahu Published: 2026-08-31T18:37:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [DevOps](), [Testing](), [Graphs](), [Artificial Intelligence](), [Software]() Tags: [ai](), [ai-evals](), [api](), [automated](), [data](), [devops](), [evals](), [graph](), [knowledge-graph](), [lifecycle](), [operational](), [other](), [pipeline](), [schema](), [sdlc](), [security](), [services](), [software](), [software-delivery](), [validation]() ### AI overview This article explains how Harness validates answers from its SDLC Knowledge Graph. Its multi-layered approach combines AI evaluations, schema traversal, API checks, direct product verification, production data, and shift-left testing to improve reliability. ### Source excerpt Discover our multi-layered validation approach combining AI evals to ensure reliable AI-powered software delivery insights. | Blog ## Multi-tenant OAuth requires credential lifecycle management beyond token isolation DevFeed: [Multi-tenant OAuth requires credential lifecycle management beyond token isolation]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-27T00:00:00Z Content type: opinion Language: en Sources: [WorkOS Blog]() Topics: [OAuth](), [Encryption](), [Authorization]() Tags: [architecture](), [encryption](), [iam](), [lifecycle](), [oauth](), [rotation](), [storage](), [vault]() ### AI overview The article argues that token isolation and storage architecture are only the starting point for multi-tenant OAuth. The harder, ongoing problems include refresh races, key rotation, provider-wide revocations, token expiration, and external revocations without webhooks. It also explains how envelope encryption and per-tenant key contexts can support bridge-style isolation. ### Source excerpt Storage architecture is the half you can finish. The refresh loop, key rotation, and revocation are the half that never does. ## Incremental backup on AWS Glacier with rustic DevFeed: [Incremental backup on AWS Glacier with rustic]() Original publisher: [Read original article]() Published: 2026-08-19T21:04:01Z Content type: tutorial Language: en Sources: [Personal blog of Anurag Bhatia]() Topics: [backups](), [restic](), [Amazon Web Services](), [Amazon S3](), [Rust](), [Open Source](), [Feathers]() Tags: [aws](), [aws-glacier-deep-archive](), [backblaze-b2](), [backup](), [backups](), [client](), [config](), [cost](), [data](), [encryption](), [encryption-at-rest](), [incremental](), [lifecycle](), [open-source](), [password](), [restic](), [restore](), [rust](), [rustic](), [s3](), [snapshots]() ### AI overview A practical guide to using rustic, a Rust implementation compatible with restic, for incremental backups with AWS Glacier cold storage. It explains keeping backup data in cold storage while maintaining metadata in S3 Standard or Backblaze B2 so snapshots, incremental backups, and targeted restores remain possible. ### Source excerpt I have been a heavy restic user for several years. In Jan of this year, I tried making restic work with AWS Glacier deep archive but it did not work out. AWS Glacier Deep Archive, for those who may not know, is one of the cheapest storage options, with costs as low as $1/TB, but with very expensive retrieval due to high egress charges from AWS, in addition to retrieval fees, API charges, etc. It can act as a backup of last resort, kind of like insurance if everything else fails, since it costs roughly 1/7th of what Backblaze B2 charges for the same data ($6.95/TB/month). Restic by design is not compatible with Glacier because it stores a mix of data blobs and tree blobs inside /data. Thus, as AWS lifecycle rules move data from S3 Standard to Glacier, basic repo operations start failing. They do have some experimental support as per FAQ, but it did not work out for me when I tried in Jan. A few days back, I came across an open-source project named rustic -- it's a restic implementation in Rust and supports cold storage. The rustic client is compatible with a traditional restic repo. Rustic and cold storage Rustic supports AWS Glacier as well as OVH cold storage. The way it works is: they keep all data in cold storage and a copy of the metadata in hot storage. This additional copy of metadata in hot storage allows operations like incremental backups, viewing snapshots, and requesting restores where only the specific data blobs needed for the restore are pulled from Glacier. This additional hot storage can sit on S3 standard or even Backblaze B2 (which I prefer due to zero API cost). Demo 1) Create repo Let's create two buckets - one in S3 (to store data in Glacier) and one on Backblaze B2 to hold an additional copy of metadata. > rclone mkdir s3:rustic-demo-cold > rclone mkdir b2:rustic-demo-hot 2) Create rustic config profile This file will define the cold and hot repo locations, along with the password file location, restoration command syntax, etc. [repository] repo ## Use compile-time DI checks without losing runtime tests DevFeed: [Use compile-time DI checks without losing runtime tests]() Original publisher: [Read original article]() Published: 2026-08-18T00:00:00Z Content type: tutorial Language: en Sources: [Koin - Cloud-Inject.io -Kotzilla]() Topics: [test](), [configuration]() Tags: [compiler](), [configuration](), [dependency](), [lifecycle](), [tests](), [validation]() ### AI overview The article explains how compile-time dependency injection validation can catch structural problems such as missing definitions, invalid qualifiers, and broken constructor paths before application startup. It emphasizes that runtime tests remain necessary for configuration, parameters, lifecycle behavior, and ownership, and recommends using layered validation. ### Source excerpt Compile-time dependency validation can catch a missing definition, an invalid qualifier, or a broken constructor path before an application starts. That is valuable. It does not prove that runtime configuration, parameters, or lifecycle behavior are correct. Divide the evidence Let compiler validation answer structural questions: Can the graph resolve this constructor path? Does a binding exist for the requested type and qualifier? Is generated wiring compatible with the declaration? Let tests answer behavioral questions: ## Match Compose injection scopes to real UI ownership DevFeed: [Match Compose injection scopes to real UI ownership]() Original publisher: [Read original article]() Published: 2026-08-18T00:00:00Z Content type: tutorial Language: en Sources: [Koin - Cloud-Inject.io -Kotzilla]() Topics: [Compose](), [ui](), [navigation](), [Process]() Tags: [compose](), [lifecycle](), [navigation](), [screen](), [ui]() ### AI overview This tutorial explains how to align Compose injection scopes with actual UI ownership and lifecycle events. It distinguishes object retrieval from creation, discusses process, navigation-destination, request, and feature-session lifetimes, and recommends testing both retention and exit behavior. ### Source excerpt Compose makes it easy to request an object close to the UI that uses it. Proximity is useful, but it does not define ownership. Recomposition can call a function many times. Navigation can keep or discard a back-stack entry. The operating system can recreate the process. A sound scope names the event that owns the object. Separate retrieval from creation Ask two questions for each injected object: Where is the object retrieved? Which lifecycle creates and releases it? A repository retrieved by a composable can still be process-scoped. A screen model can be owned by a navigation destination. A transient formatter can be created for each request. Write the lifetime next to the definition and test that the object survives, or does not survive, the intended event. ## Introducing memory retention for agentic memory in OpenSearch DevFeed: [Introducing memory retention for agentic memory in OpenSearch]() Original publisher: [Read original article]() Author: Erfan Ballew Published: 2026-08-13T22:29:25Z Content type: article Language: en Sources: [OpenSearch]() Topics: [Amazon OpenSearch Service](), [AI Agent](), [audit trail](), [model-deployment]() Tags: [agentic](), [audit-trail](), [blog](), [compliance](), [cost](), [experimental](), [lifecycle](), [memory](), [opensearch](), [precision](), [retention](), [storage](), [technical]() ### AI overview This article explains OpenSearch 3.8's experimental memory retention feature for agentic memory. It describes age-based and count-based limits for different memory types, how policies prevent stale context and uncontrolled storage growth, and how to enable retention on an existing cluster. ### Source excerpt Learn how the memory retention policy in OpenSearch automatically manages the lifecycle of agentic memory, controlling storage growth while preserving specific memories. The post Introducing memory retention for agentic memory in OpenSearch appeared first on OpenSearch. ## Xen 4.22: Strengthening Open Source Virtualization for Cloud, Embedded, and Automotive Systems DevFeed: [Xen 4.22: Strengthening Open Source Virtualization for Cloud, Embedded, and Automotive Systems]() Original publisher: [Read original article]() Author: Cody Zuschlag Published: 2026-08-05T15:18:36Z Content type: article Language: en Sources: [Blog - Xen Project]() Topics: [virtualization](), [Open Source](), [Cloud](), [Hardware](), [Scalability](), [Arm](), [RISC-V]() Tags: [arm](), [automotive](), [cloud](), [developers](), [embedded](), [hardware](), [improvements](), [lifecycle](), [maintenance](), [open-source](), [performance](), [platform](), [release](), [releases](), [risc-v](), [safety](), [security](), [standards](), [systems](), [virtualization](), [xen-4-22]() ### AI overview Xen 4.22 is presented as the latest Xen hypervisor release, adding modern hardware support, Arm virtualization improvements, continued RISC-V progress, and Xenstore scalability updates. The Xen Project also introduces a consistent five-year security support lifecycle for Xen 4.20 and later releases. ### Source excerpt Xen 4.22 adds modern hardware support, Arm improvements, continued RISC-V progress, Xenstore scalability updates, and a five-year security support lifecycle. ## Announcement: Xcode16 Deprecation in Semaphore DevFeed: [Announcement: Xcode16 Deprecation in Semaphore]() Original publisher: [Read original article]() Author: Pete Miloravac Published: 2026-08-04T13:47:48Z Content type: release Language: en Sources: [Semaphore Engineering]() Topics: [Xcode](), [macOS](), [ci]() Tags: [announcement](), [ci](), [deprecated](), [end-of-life](), [lifecycle](), [macos](), [operating-systems](), [product-news](), [yaml]() ### AI overview Semaphore is deprecating and retiring its macOS Xcode16 build environments. Brownout periods will run from September 7 through October 4, 2026, before the environments are removed on October 5, 2026. Users are instructed to migrate pipelines to macos-xcode26 and validate them. ### Source excerpt MacOS Xcode16 reached the end of its supported lifecycle on Semaphore. To ensure the security, reliability, and maintainability of our platform, we are announcing the deprecation and end of life of MacOS Xcode16 build environments. Semaphore users should switch to Xcode26. Why We're Deprecating Xcode16 As operating systems age, they cease to receive timely security [...] The post Announcement: Xcode16 Deprecation in Semaphore appeared first on Semaphore. ## How EKS is simplifying Kubernetes cluster lifecycle management DevFeed: [How EKS is simplifying Kubernetes cluster lifecycle management]() Original publisher: [Read original article]() Author: Spyros Angelopoulos Published: 2026-08-01T15:00:00Z Content type: article Language: en Sources: [Kubernetes Overview, News and Trends | The New Stack]() Topics: [Amazon Elastic Kubernetes Service](), [Kubernetes](), [Availability](), [Deployment]() Tags: [availability](), [aws-marketplace](), [cloud-services](), [deployment](), [devops](), [kubernetes](), [lifecycle](), [post-contributed](), [sponsor-aws-marketplace](), [sponsored-post-contributed](), [upgrades]() ### AI overview The article describes the operational challenges of Kubernetes upgrades and EKS efforts to make cluster lifecycle management easier. It highlights Extended Support, which broadens the availability of each Kubernetes version to 26 months, giving organizations more time to validate and schedule upgrades. ### Source excerpt Kubernetes moves at a pace of three minor version releases per year, and staying current is not optional if you The post Kubernetes upgrades don't have to break things: How EKS is making cluster lifecycle management simpler and safer appeared first on The New Stack. ## Feature Flag Security in your CI/CD Pipeline DevFeed: [Feature Flag Security in your CI/CD Pipeline]() Original publisher: [Read original article]() Author: Lena Sano Published: 2026-07-22T00:00:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [feature flags](), [Security](), [CI/CD](), [AI Agent]() Tags: [ai-agent](), [ci-cd](), [cleanup](), [feature](), [feature-flagging](), [feature-flags](), [governance](), [lifecycle](), [local](), [pii](), [privacy](), [remote](), [security]() ### AI overview This article explains security practices for Harness Feature Management and Experimentation. It covers local versus remote feature-flag evaluation, privacy considerations for sensitive user data, governance, automated cleanup, and an AI agent for feature-flag lifecycle management. ### Source excerpt Secure feature flags with Harness FME using local or remote evaluation, automated cleanup, governance, and AI-powered lifecycle management. | Blog ## Harness Agent DLC: Secure the Agent Lifecycle DevFeed: [Harness Agent DLC: Secure the Agent Lifecycle]() Original publisher: [Read original article]() Author: Jyoti Bansal Published: 2026-07-21T00:00:00Z Content type: release Language: en Sources: [Harness Blog]() Topics: [Artificial Intelligence](), [Development](), [Testing](), [Security]() Tags: [agentic-ai](), [ai-agents](), [lifecycle](), [security](), [testing](), [update]() ### AI overview Harness introduces Agent DLC, a platform extension intended to help teams build, test, deploy, operate, and govern AI agents across the agent development lifecycle. The offering includes AI testing, an AIBOM, Agent Discovery, AI Firewall, and AgentTrace. ### Source excerpt Secure AI agents from build to runtime with Harness Agent DLC, featuring AI testing, AIBOM, Agent Discovery, AI Firewall, and AgentTrace. | Blog ## Навигация в Jetpack Compose без магии: что на самом деле делают библиотеки навигации DevFeed: [Навигация в Jetpack Compose без магии: что на самом деле делают библиотеки навигации]() Original publisher: [Read original article]() Author: karenkov\_id (hh.ru) Published: 2026-07-01T08:20:40Z Content type: tutorial Language: ru Sources: [HeadHunter RU]() Topics: [Compose](), [Jetpack Compose](), [Android](), [Mobile]() Tags: [android](), [compose](), [jetpack-compose](), [kotlin](), [lifecycle](), [mobile](), [modo](), [remembersaveable](), [saveablestateholder](), [tag-08a48a9394c3](), [tag-f538878e20ff](), [viewmodel]() ### AI overview This article explains why naïve screen-list navigation is insufficient in Jetpack Compose and examines how the Modo navigation library addresses screen state isolation, navigation-graph persistence, lifecycle and resource cleanup, and instance stability. ### Source excerpt Вы когда-нибудь задумывались, зачем нужны библиотеки для навигации в Jetpack Compose? Почему мы не можем просто взять mutableStateOf со списком экранов и переключаться между ними? Оказывается, если мы попробуем реализовать такой наивный подход, то столкнёмся с рядом проблем: rememberSaveable не работает, ViewModel не очищаются после ухода с экрана, Lifecycle не работает корректно и многое другое. В статье разберём, как работают библиотеки навигации в Jetpack Compose и какие задачи они решают на примере библиотеки навигации Modo. Читать далее ## Subscription Management Software: A 2026 Buyer's Guide DevFeed: [Subscription Management Software: A 2026 Buyer's Guide]() Original publisher: [Read original article]() Author: Aarthi Poonia Published: 2026-06-28T00:00:00Z Content type: article Language: en Sources: [Dodo Payments Blog]() Topics: [Software](), [Software as a service](), [Finance]() Tags: [2026](), [billing](), [churn](), [compare](), [compliance](), [features](), [guide](), [lifecycle](), [payment](), [pricing](), [recovery](), [reporting](), [retention](), [revenue](), [saas](), [subscription-billing](), [subscriptions](), [tax]() ### AI overview A 2026 buyer's guide to subscription management software, covering its role across the recurring-customer lifecycle, must-have billing and operational features, leading options, and platform selection for SaaS businesses. ### Source excerpt What subscription management software does, the must-have features, top tools compared, and how to choose the right platform for your SaaS in 2026. ## Stripe Recurring Payments: How to Set Them Up in 2026 DevFeed: [Stripe Recurring Payments: How to Set Them Up in 2026]() Original publisher: [Read original article]() Author: Aarthi Poonia Published: 2026-06-26T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [stripe](), [API](), [configuration]() Tags: [2026](), [billing](), [cancellation](), [checkout](), [customer](), [guide](), [how-to](), [lifecycle](), [merchant-of-record](), [payment](), [stripe](), [subscriptions](), [tax](), [webhooks]() ### AI overview A practical guide to Stripe recurring payments covering subscription setup, payment-method collection, billing lifecycles, failed payments and dunning, tax responsibility, and when a merchant of record may be a better fit. ### Source excerpt A practical 2026 guide to Stripe recurring payments: how to set up subscriptions, handle failed payments and dunning, manage tax, and when an MoR fits better. ## Custom Scopes in Koin: A Practical Example DevFeed: [Custom Scopes in Koin: A Practical Example]() Original publisher: [Read original article]() Author: Gabriel Bronzatti Moro Published: 2026-06-19T12:01:01Z Content type: tutorial Language: en Sources: [Koin developers - Medium]() Topics: [App](), [Open Source](), [Mobile]() Tags: [app](), [components](), [compose-multiplatform](), [data](), [dependency](), [implementation](), [koin](), [kotlin](), [lifecycle](), [open-source](), [project](), [scopes](), [state](), [stateless](), [user-experience]() ### AI overview A practical tutorial on using custom scopes in Koin to keep a selected user profile image available across an application. It demonstrates a session scope, session data, and a stateless session manager using StreamPlayerApp as the example. ### Source excerpt Hey friends 👋 Today, we are going to explore how we can create a custom scope, one of the powerful features provided by Koin. To make things practical 🔨, we'll walk through a real-world use case from the open-source project StreamPlayerApp (created by CodandoTV). Wireframes of a mobile app -- Unsplash by @alvarordesignWhat is the problem? StreamPlayerApp is an open-source project that aims to recreate the core experience of Netflix. One of its features allows users to select a profile, similar to the profile selection screen found in streaming platforms. The selected profile image needs to be accessible across the entire application, ensuring a consistent user experience on every screen. Whenever a user changes their profile, the updated image should be immediately reflected throughout the app, allowing all screens to stay synchronized with the current profile selection. Screenshots demonstrating the user profile selection feature.How we solve this problem using Custom Scopes? First, we create a class that represents the scope of a user session: class SessionScope Next, we create a lightweight data class containing only the information that needs to be kept in memory throughout the user session: data class UserSessionInfo( // represents the time user changed the profile val userTimestamp: Instant, // represents the selected picture url val profileImageUrl: String ) We then created a dedicated class responsible for managing the user's session lifecycle and state. class SessionManager { private val scopeId: String = "user_session" /** * Create custom scope and hold the user's session data */ fun openSession(imageUrl: String) { closeSession() val koin = KoinPlatform.getKoin() val scope = koin.createScope( scopeId = scopeId, ) scope.declare( UserSessionInfo( userTimestamp = Clock.System.now(), profileImageUrl = imageUrl ) ) } /** * Retrieve the current user session */ fun userSessionInfo(): UserSessionInfo? { return KoinPlatform.getKoin() .getScopeOrNull(sc ## How to build a resilient platform control plane with Temporal DevFeed: [How to build a resilient platform control plane with Temporal]() Original publisher: [Read original article]() Author: Joshua Smith Published: 2026-06-01T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [control-plane](), [Provisioning](), [Python](), [SDKs](), [API]() Tags: [build](), [error-handling](), [how-to](), [infrastructure](), [lifecycle](), [provisioning](), [python](), [retries](), [sdk](), [workflow]() ### AI overview This tutorial explains how to build a resilient platform control plane with Temporal. It compares basic infrastructure Workflows with long-running Entity Workflows that manage a resource's lifecycle, including message handling, retries, compensation, and durable state. ### Source excerpt Learn how to build a resilient platform control plane with Temporal using the Entity Workflow pattern: message handling, Continue-as-New, and compensation. ## Announcement: Xcode15 Deprecation in Semaphore DevFeed: [Announcement: Xcode15 Deprecation in Semaphore]() Original publisher: [Read original article]() Author: Pete Miloravac Published: 2026-05-12T10:56:42Z Content type: release Language: en Sources: [Semaphore Engineering]() Topics: [Xcode](), [ci](), [macOS]() Tags: [announcement](), [ci](), [deprecated](), [lifecycle](), [product-news](), [scheduled](), [september-2026](), [switching](), [xcode]() ### AI overview Semaphore announces the deprecation and end of life of its macOS Xcode15 build environments. Brownout periods will precede removal on July 6, 2026, and users are advised to migrate their pipelines to a supported Xcode version, preferably Xcode26. ### Source excerpt MacOS Xcode15 reached the end of its supported lifecycle on Semaphore. To ensure the security, reliability, and maintainability of our platform, we are announcing the deprecation and end of life of MacOS Xcode15 build environments. Semaphore users should consider switching to Xcode26 as Xcode16 is scheduled for deprecation in September 2026. Why We're Deprecating Xcode15 [...] The post Announcement: Xcode15 Deprecation in Semaphore appeared first on Semaphore. ## EU AI Act Compliance: Requirements, Risks, and What to Document DevFeed: [EU AI Act Compliance: Requirements, Risks, and What to Document]() Original publisher: [Read original article]() Author: info@goteleport.com (Kayne McGladrey, CISSP) Published: 2026-04-15T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [Artificial Intelligence](), [Requirements](), [Documentation](), [audit](), [data-governance](), [Logging](), [Monitoring](), [Deployment](), [data]() Tags: [ai](), [compliance](), [cybersecurity](), [data](), [data-governance](), [dataset](), [deployment](), [development](), [documentation](), [eu](), [iso-27001](), [lifecycle](), [logging](), [monitoring](), [nist](), [real-time](), [reproducibility](), [soc-2](), [versioning]() ### AI overview A practical guide to EU AI Act compliance covering requirements, risks, technical documentation, logging, data governance, lifecycle evidence, traceability, monitoring, and human oversight. It outlines key compliance milestones from August 2025 through August 2027. ### Source excerpt Cut through EU AI Act complexity with practical guidance on requirements, risks, and documentation. ## Zuora Review 2026: Is Enterprise Billing Software Worth the Complexity? DevFeed: [Zuora Review 2026: Is Enterprise Billing Software Worth the Complexity?]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-04-10T00:00:00Z Content type: comparison Language: en Sources: [Dodo Payments Blog]() Topics: [Software as a service](), [Software](), [Orchestration](), [cloud-infrastructure]() Tags: [2026](), [alternatives](), [billing](), [complexity](), [enterprise](), [erp](), [features](), [implementation](), [integration](), [lifecycle](), [orchestration](), [review](), [reviews](), [saas](), [software]() ### AI overview A review of Zuora as an enterprise subscription management platform, covering its product scope, pricing at enterprise scale, implementation complexity, target customers, and alternatives. The article describes Zuora as a billing orchestration layer for recurring billing, revenue recognition, quote-to-cash operations, subscriptions, invoices, and downstream integrations. ### Source excerpt An honest review of Zuora's enterprise billing platform - covering features, pricing, implementation complexity, and simpler alternatives for SaaS. [Next page]()