Shopify Shipping: When to Use Carrier Service API vs Delivery Customization

·2 views

Shopify offers two distinct tools for advanced shipping functionality: the Carrier Service API and Delivery Customization, each serving a different purpose in the checkout flow. The Carrier Service API is responsible for calculating and providing shipping rates, while Delivery Customization controls how already-collected rates are filtered, renamed, or reordered for the shopper. Shopify's shipping process follows four stages — Determine, Collect, Customize, and Render — with each tool operating at a different stage. The two approaches are not mutually exclusive; a carrier service can generate the rates while delivery customization manages their presentation. Developers are advised to choose the tool based on whether they need to create rates or control how existing rates appear at checkout.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Proxmox Automation Phase 2: Serial-Identified Disks with LVM and XFS for DB Workloads

A developer has published Phase 2 of a Proxmox automation pipeline that provisions four serial-labelled data disks on a virtual machine using Terraform and manages LVM-over-XFS storage via an idempotent Ansible playbook. The setup addresses a real-world problem in database server environments where multiple disks — for data, logs, backups, and var — must each be reliably identified and independently resized. Linux's reliance on kernel bus-scan order for disk naming (e.g., /dev/sdb) was identified as the core issue, as these assignments can silently change after a reboot, hotplug event, or disk addition. The solution uses persistent serial identifiers attached to each disk in Terraform so that the correct logical volume can be targeted for online expansion by editing a single variable and re-running the pipeline. The phase intentionally excludes live directory migration and shrink operations, with monitoring integration and dynamic inventory planned for later phases.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

CHOps SQL Editor Aims to Streamline ClickHouse Query Development in One Interface

CHOps is a browser-based platform designed to manage ClickHouse deployments through a unified web interface, eliminating the need for multiple tools or command-line switching. Its SQL Editor consolidates schema browsing, query execution, performance analysis, and debugging into a single workspace. The editor features a four-panel layout covering a Schema Explorer, query tabs, an SQL writing area, and a results panel with execution statistics. Developers benefit from context-aware autocomplete that pulls real database, table, and column names directly from the connected ClickHouse cluster. Additional capabilities include AI-assisted SQL generation, bookmark management, query history, and secure direct authentication using ClickHouse credentials.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Builds Sub-$5/Day US Stock Data Feed Using WebSocket and REST APIs

A software developer built a low-cost personal US stock monitoring system after finding professional data terminals prohibitively expensive, with the cheapest option exceeding $200 per month. The solution uses a hybrid architecture combining WebSocket connections for real-time live quotes and REST API calls for historical minute-bar data. The developer selected a multi-asset API provider called AllTick, which supports US stocks, Hong Kong stocks, and forex under a single API key, with same-day onboarding. After roughly one month of operation, total server costs remained below $150, with single-digit millisecond latency for live quotes meeting all personal project requirements. The developer recommends starting with a small symbol list and validating reconnection logic before scaling, noting that an exponential backoff loop effectively handled WebSocket disconnection issues.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer builds stdlib-only git secret scanner, battles packfile format edge cases

A developer built a secret-scanning tool during a hackathon that reads git repository object databases using only Python's standard library, with no third-party git bindings allowed. The tool was designed to detect API keys and credentials across a repo's full history, including long-deleted files. A major hurdle emerged when git's garbage collection compressed loose objects into packfiles — the format used by every repository cloned from GitHub — forcing a full packfile parser to be written from scratch. Two subtle bugs surfaced: an offset varint encoding that silently differed from the size varint, producing plausible but wrong data without crashing, and a recursive delta resolver that exponentially re-processed shared base objects on larger repositories. Both issues were caught through rigorous SHA checksum verification and fixed with memoisation, yielding a working scanner that handles real-world repositories.

0 comments Read more at DEV Community