# separate Published articles for separate. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Route specialized workloads DevFeed: [Route specialized workloads]() Original publisher: [Read original article]() Author: Cecil Phillip Published: 2026-05-11T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [GPU](), [Machine learning](), [cpu](), [data analytics](), [Hardware]() Tags: [analytics](), [cost](), [cpu](), [gpu](), [ml](), [queues](), [scaling](), [separate](), [temporal-concepts](), [worker]() ### AI overview The article describes a Temporal Validated Pattern for routing Activities with different resource requirements to separate Task Queues. Dedicated Worker pools can handle GPU-intensive machine learning, CPU, high-memory analytics, and specialized hardware workloads independently. ### Source excerpt Route ML, analytics, and CPU Activities to separate Temporal Task Queues. Cut GPU costs by 60-80% while scaling each Worker pool independently. ## Community threads: Is it possible to write a single Workflow with different languages? DevFeed: [Community threads: Is it possible to write a single Workflow with different languages?]() Original publisher: [Read original article]() Author: Caz Michaels Published: 2024-03-05T08:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [interoperability](), [SDKs](), [Programming]() Tags: [community](), [interoperability](), [languages](), [sdk](), [sdks](), [separate]() ### AI overview A Temporal Workflow Definition should use one language, but its Activities can be written in other languages. Each language requires a separate Worker and task queue, with unique Activity names to support execution and interoperability. ### Source excerpt Today's Thread focuses on a question asked by a Temporal user who wants to know: Is it possible to write a single Workflow in multiple languages? ## How Apple built iCloud to store billions of databases DevFeed: [How Apple built iCloud to store billions of databases]() Original publisher: [Read original article]() Author: Engineer's Codex Published: 2024-01-14T21:53:05Z Content type: article Language: en Sources: [Engineer's Codex]() Topics: [Apache Cassandra](), [Database](), [Multitenancy](), [Cloud](), [NoSQL](), [Architecture & Design](), [Scalability]() Tags: [architecture](), [cassandra](), [cloud](), [database](), [nosql](), [scalability](), [separate]() ### AI overview This article examines how Apple built iCloud and CloudKit using FoundationDB and Cassandra. It discusses the systems' extreme multi-tenant architecture and engineering choices such as asynchronous processing, stateless design, resource isolation, and layered abstractions to support scalability, reliability, availability, and developer experience. ### Source excerpt Apple uses Cassandra and FoundationDB for CloudKit, their cloud backend service. We take a look into how exactly each is used within their cloud and the problems they've solved. ## Open sourcing code into a separate git repository DevFeed: [Open sourcing code into a separate git repository]() Original publisher: [Read original article]() Published: 2023-03-19T21:15:22Z Content type: tutorial Language: en Sources: [Signs of Triviality]() Topics: [Code](), [Git]() Tags: [code](), [git](), [how-to](), [local](), [open](), [remote](), [repository](), [separate]() ### AI overview A brief guide to adding a second Git remote repository to open-source code from a local project. ### Source excerpt A quick description of how to add a second remote repository for the purposes of open sourcing local code. ## Logging to a File with Craft CMS 4 DevFeed: [Logging to a File with Craft CMS 4]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2022-12-21T19:35:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Content Management System](), [Logging](), [log management](), [PHP]() Tags: [article](), [cms](), [craft](), [custom](), [easily](), [file](), [how-to](), [insights](), [learn](), [logging](), [logs](), [module](), [php](), [plugin](), [send](), [separate]() ### AI overview A tutorial showing how to configure Craft CMS 4 plugins or modules to send their logs to separate files using Monolog and a FileLog helper class. It explains log levels, category matching, namespaces, and storage/logs output. ### Source excerpt Learn how to easily send logs from your custom module or plugin to a separate file in Craft CMS 4 ## Mitigating the Risk of Siloed Native Code - Touchlab DevFeed: [Mitigating the Risk of Siloed Native Code - Touchlab]() Original publisher: [Read original article]() Published: 2020-04-01T20:32:29Z Content type: opinion Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [multiplatform](), [Development](), [business logic](), [Error Handling]() Tags: [android](), [architecture](), [business](), [code-sharing](), [developer-velocity](), [development](), [ios](), [kotlin-multiplatform](), [multiplatform](), [native](), [separate](), [thoughts]() ### AI overview The article argues that maintaining separate native Android and iOS codebases increases platform-specific errors, slows feature iteration, causes feature drift, raises costs, and creates recruitment and management risks. It presents shared native code as a way to reduce those risks. ### Source excerpt There's risk with siloed native code or managing two separate code bases. We discuss why we believe shared native code is less risky. ## Let's Build A Simple Interpreter. Part 13: Semantic Analysis. DevFeed: [Let's Build A Simple Interpreter. Part 13: Semantic Analysis.]() Original publisher: [Read original article]() Author: Ruslan Spivak Published: 2017-04-27T05:00:00Z Content type: tutorial Language: en Sources: [Ruslan Spivak]() Topics: [syntax](), [Parsing](), [Parser](), [compilers](), [context]() Tags: [blog](), [compilers](), [errors](), [parsing](), [separate](), [syntax](), [types]() ### AI overview This tutorial explains semantic analysis in interpreters and compilers. It shows why grammatically correct Pascal programs can still contain errors, and how an abstract syntax tree, symbol table, and separate semantic-analysis phase can detect issues such as using undeclared variables. ### Source excerpt Anything worth doing is worth overdoing. Before doing a deep dive into the topic of scopes, I'd like to make a "quick" detour and talk in more detail about symbols, symbol tables, and semantic analysis. In the spirit of "Anything worth doing is worth overdoing", I hope you'll ... ## Some notes about Skytools3 DevFeed: [Some notes about Skytools3]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2011-04-11T09:30:00Z Content type: article Language: en Sources: [Dimitri Fontaine]() Topics: [PostgreSQL](), [configuration](), [Server]() Tags: [documentation](), [packaging](), [production](), [release](), [separate](), [services](), [system]() ### AI overview The article discusses packaging Skytools3, including separating its daemons and subprojects into installable components for PostgreSQL environments. It describes service users, configuration files, startup and shutdown integration, logging defaults, and planned documentation work before a public release. ### Source excerpt I've been working on skytools3 packaging lately. I've been pushing quite a lot of work into it, in order to have exactly what I needed out of the box, after some 3 years of production and experiences with the products. Plural, yes, because even if pgbouncer and plproxy are siblings to the projets (same developers team, separate life cycle and releases), then skytools still includes several sub-projects. Here's what the skytools3 packaging is going to look like: