# Back End Published articles for Back End. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Website replatforming: How to migrate your site smoothly DevFeed: [Website replatforming: How to migrate your site smoothly]() Original publisher: [Read original article]() Author: Webflow Team Published: 2026-06-27T00:00:00Z Content type: tutorial Language: en Sources: [Webflow Blog]() Topics: [migration](), [Website](), [Content Management System](), [Scalability](), [hosting](), [Back end](), [Front end]() Tags: [back-end](), [cms](), [front-end](), [guide](), [hosting](), [how-to](), [migration](), [scalability](), [strategy]() ### AI overview A guide to website replatforming: migrating from an older CMS or custom setup to a new platform while preserving much of the existing content and design. It explains common reasons for replatforming, including outdated technology, poor performance, limited integrations, scalability limits, and rigid workflows. ### Source excerpt Explore how website replatforming preserves the best of your existing site, while making it more scalable and manageable for long-term performance. ## Screaming Architecture & Colocation: Let Your Project Structure Tell the Story DevFeed: [Screaming Architecture & Colocation: Let Your Project Structure Tell the Story]() Original publisher: [Read original article]() Author: The T-Shaped Dev Published: 2026-03-14T07:19:34Z Content type: tutorial Language: en Sources: [The T-Shaped Dev]() Topics: [Code](), [Back end](), [Node.js](), [Express](), [Front end](), [React]() Tags: [app](), [architecture](), [back-end](), [code](), [express](), [front-end](), [node-js](), [project](), [structure](), [technical](), [tests]() ### AI overview This tutorial explains how to organize Node.js, TypeScript, and React projects around business capabilities rather than technical layers. It presents Screaming Architecture and colocation as ways to improve code discoverability, team ownership, change isolation, feature removal, and maintainability. ### Source excerpt Learn why you should organize your code by what your app actually does, not by technical roles. (5 min) ## How agentic AI could pressure databases and challenge eventual consistency DevFeed: [How agentic AI could pressure databases and challenge eventual consistency]() Original publisher: [Read original article]() Author: Becca Weng Published: 2026-02-13T00:00:00Z Content type: opinion Language: en Sources: [Cockroach Labs]() Topics: [Artificial Intelligence](), [Databases](), [data](), [consistency](), [backends](), [Concurrency]() Tags: [agentic-ai](), [agents](), [ai](), [back-end](), [concurrency](), [consistency](), [data](), [databases](), [systems]() ### AI overview The article summarizes a Cockroach Labs webinar about how agentic AI may increase pressure on databases and back-end systems. It argues that autonomous agents can generate unpredictable, high-volume traffic and suggests that operational databases may need strong serializable consistency, correct reads, and predictable behavior under extreme concurrency. ### Source excerpt AI agents are no longer a thought experiment. They're already writing code, calling APIs, retrying failed requests, and coordinating work at machine speed. And they're about to put unprecedented pressure on the systems we use to store and move data. ## How to Integrate OAuth2 Into a Django/DRF Back End Without Losing Control DevFeed: [How to Integrate OAuth2 Into a Django/DRF Back End Without Losing Control]() Original publisher: [Read original article]() Author: Prachi Kothiyal Published: 2026-02-06T10:58:21Z Content type: tutorial Language: en Sources: [Backend Archives | Talent500 blog]() Topics: [Django](), [OAuth 2.0](), [Back end](), [Authentication](), [API](), [Framework]() Tags: [a-minimal-view-for-token-exchange](), [api](), [authentication](), [back-end](), [backend](), [configuring-back-end-authentication](), [django](), [newsletters](), [oauth2](), [rest](), [server-side-vs-client-side-oauth2-flows](), [testing-and-reliability-considerations](), [what-the-back-end-needs-to-do](), [why-rely-on-a-social-auth-library]() ### AI overview A practical guide to integrating OAuth2 social login into a Django or Django REST Framework back end. It recommends letting the front end handle the provider flow while the back end validates third-party tokens, maps social identities to local accounts, and issues API credentials. ### Source excerpt When a Django or Django REST Framework (DRF) back end is already handling authentication, adding "Log in with Google" or [...] The post How to Integrate OAuth2 Into a Django/DRF Back End Without Losing Control appeared first on Talent500 blog. ## Mob Programming: Smells Like Team Spirit DevFeed: [Mob Programming: Smells Like Team Spirit]() Original publisher: [Read original article]() Author: Dmytro Kurets Published: 2025-12-04T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [Programming](), [Code](), [pull-requests](), [Back end](), [Front end](), [Data analysis](), [Refactoring]() Tags: [back-end](), [code](), [collaboration](), [data-analysis](), [engineering](), [engineering-culture](), [front-end](), [keyboard](), [pairing](), [programming](), [review](), [team]() ### AI overview The article explains mob programming as structured, shared-focus collaboration with one driver, rotating typing roles, and navigators guiding the work. It describes a trivago team experimenting with collaborative review and coding changes to address pull requests piling up and slowing delivery. ### Source excerpt Mob programming often sparks hot takes. "It's counter-productive." "One person could do it faster." "Why waste five people on one keyboard?" If that's what it looks like in your head--one senior ... ## Simplifying back-end complexity with Supabase Data APIs DevFeed: [Simplifying back-end complexity with Supabase Data APIs]() Original publisher: [Read original article]() Author: Prashant Sridharan; Steve Chavez; Laurence Isla Published: 2025-05-17T07:00:00Z Content type: article Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [API](), [backends](), [CRUD](), [Database](), [GraphQL](), [SQL](), [telemetry]() Tags: [accelerate](), [apis](), [back-end](), [cost](), [graphql](), [observability](), [product](), [reduce](), [rest](), [sql]() ### AI overview Supabase Data APIs automatically expose Postgres tables, views, stored procedures, and database functions through REST and GraphQL APIs. The article explains how this reduces custom CRUD endpoint development and infrastructure maintenance while retaining querying, relationships, RPC, connection pooling, observability, and custom endpoint options. ### Source excerpt Replace custom CRUD endpoints, reduce infrastructure complexity, and accelerate product delivery. ## Easy way to upload, transform and deliver files and images (Sponsored) DevFeed: [Easy way to upload, transform and deliver files and images (Sponsored)]() Original publisher: [Read original article]() Author: David Walsh Published: 2025-03-24T22:58:30Z Content type: article Language: en Sources: [David Walsh]() Topics: [file](), [Image](), [Developer experience](), [Back end](), [Python]() Tags: [ascii](), [back-end](), [conversion](), [documentation](), [files](), [gif](), [images](), [python](), [qr-code](), [sponsored](), [uncategorized]() ### AI overview This sponsored developer article presents Filestack as a service for uploading, transforming, and delivering files and images. It describes a file-uploading interface, integrations with services such as Google Drive, Dropbox, GitHub, Facebook, and Instagram, a Python library for back-end uploads, documentation, and transformations for images, videos, and documents. ### Source excerpt Managing media is a really difficult task if you try to do all of it yourself, especially if the media comes from other sources. The file can be submitted in any state and size, but what if you need something really specific? You can code it all yourself or you can use an awesome service [...] The post Easy way to upload, transform and deliver files and images (Sponsored) appeared first on David Walsh Blog. ## Introducing The AWS AI Stack DevFeed: [Introducing The AWS AI Stack]() Original publisher: [Read original article]() Author: Serverless Team Published: 2024-09-11T00:00:00Z Content type: release Language: en Sources: [Serverless Blog]() Topics: [Artificial Intelligence](), [Amazon Web Services](), [Amazon Bedrock](), [Large Language Model](), [AWS Lambda](), [Boilerplate](), [Claude](), [React](), [Serverless](), [Back end](), [Front end](), [llama3]() Tags: [ai](), [aws](), [aws-lambda](), [back-end](), [bedrock](), [ci-cd](), [claude](), [cloud-computing](), [faas](), [front-end](), [function-as-a-service](), [infrastructure-as-code](), [llama3](), [llms](), [news](), [react](), [serverless](), [serverless-architecture](), [serverless-framework]() ### AI overview The AWS AI Stack is introduced as a full-stack, serverless boilerplate for building AI applications on AWS. It uses Bedrock LLMs including Claude 3.5 Sonnet and Llama3.1, with a React front end, AWS Lambda back end, and built-in CI/CD. ### Source excerpt Full-stack, serverless, boilerplate for AI applications on AWS, featuring Bedrock LLMs like Claude 3.5 Sonnet and Llama3.1, a React front-end, AWS Lambda back-end, built-in CI/CD and more. ## How to Use User Location in Applications and Assess Its Limitations DevFeed: [How to Use User Location in Applications and Assess Its Limitations]() Original publisher: [Read original article]() Author: Austin Published: 2024-07-25T14:10:28Z Content type: article Language: en Sources: [Back End - Austin Gil]() Topics: [Programming](), [App]() Tags: [app](), [back-end](), [business-logic](), [coding](), [compliance](), [development](), [edge-compute](), [front-end](), [geolocation](), [html](), [ip](), [javascript](), [js](), [location](), [location-based](), [privacy](), [programming](), [software](), [web-development]() ### AI overview This article examines location-based programming, including use cases such as regional language, currency, store locators, weather data, and geofencing. It distinguishes user-experience, application-logic, and policy or compliance concerns, then discusses four ways to obtain location: user reporting, device heuristics, IP address, and edge compute. ### Source excerpt A post discussing the nuances around location-based programming. Various ways to access user location, how they can fail, and what to do about it. ## Build Well-Documented and Authenticated APIs in Node.js with Fastify DevFeed: [Build Well-Documented and Authenticated APIs in Node.js with Fastify]() Original publisher: [Read original article]() Author: Julián Duque Published: 2024-04-29T23:25:00Z Content type: tutorial Language: en Sources: [Heroku]() Topics: [Fastify](), [API](), [Node.js](), [Authentication](), [JSON Web Tokens](), [OpenAPI Specification](), [Heroku](), [Postman](), [Swagger](), [Back end]() Tags: [apis](), [authentication](), [back-end](), [build](), [engineering](), [express](), [framework](), [heroku](), [how-to](), [javascript](), [jwt](), [node-js](), [openapi](), [postman](), [product-features](), [swagger]() ### AI overview A hands-on walkthrough for building a documented and authenticated API with Node.js and Fastify. It covers JWT authentication, Fastify Swagger plugins for generating an OpenAPI specification, Postman as an API client, and deployment to Heroku. ### Source excerpt If you're an API developer working with Node.js, then you're probably familiar with Express. But have you tried out the Fastify framework to build with power, speed, and convenience? In this walkthrough, we build a full-featured, easy-to-consume API with Fastify. And we deploy it to the cloud with ease. We show you how to: Get [...] The post Build Well-Documented and Authenticated APIs in Node.js with Fastify appeared first on Heroku. ## Working with ChatGPT Functions on Heroku DevFeed: [Working with ChatGPT Functions on Heroku]() Original publisher: [Read original article]() Author: Julián Duque Published: 2024-01-30T15:00:00Z Content type: tutorial Language: en Sources: [Heroku]() Topics: [Heroku](), [OpenAI](), [Node.js](), [API](), [Artificial Intelligence](), [Express](), [React](), [monorepo](), [web applications](), [GitHub]() Tags: [ai](), [ai-machine-learning](), [apis](), [back-end](), [chatgpt](), [deploy](), [developer-tools](), [engineering](), [express](), [front-end](), [generative-ai](), [github](), [heroku](), [how-to](), [javascript](), [monorepo](), [node-js](), [openai](), [react](), [web]() ### AI overview A tutorial showing how to build a Node.js Menu Maker application that uses OpenAI's Chat Completions API and function calling, with a React front end and Express back end, and deploys the application on Heroku. ### Source excerpt How to Build and Deploy a Node.js App That Uses OpenAI's APIs Near the end of 2023, ChatGPT announced that it had 100M weekly users. That's a massive base of users who want to take advantage of the convenience and power of intelligent question answering with natural language. With this level of popularity for ChatGPT, [...] The post Working with ChatGPT Functions on Heroku appeared first on Heroku. ## AI for Web Devs: Faster Responses with HTTP Streaming DevFeed: [AI for Web Devs: Faster Responses with HTTP Streaming]() Original publisher: [Read original article]() Author: Austin Published: 2023-10-24T19:51:38Z Content type: tutorial Language: en Sources: [Back End - Austin Gil]() Topics: [Streaming](), [HTTP](), [Qwik](), [web applications](), [OpenAI](), [Artificial Intelligence]() Tags: [ai](), [back-end](), [coding](), [development](), [front-end](), [http](), [javascript](), [js](), [openai](), [programming](), [qwik](), [software](), [streaming](), [web](), [web-applications](), [web-development]() ### AI overview This tutorial explains how to add HTTP streaming to an AI-powered Qwik application. It discusses the limitations of Qwik route actions for standard streaming and uses middleware and a standard Response object to support incremental responses. ### Source excerpt Adding HTTP streaming to AI applications can improve perceived performance. This post covers the server side and client side requirements. ## Accept E-Commerce Payments Easily with PayPal's Buttons Component DevFeed: [Accept E-Commerce Payments Easily with PayPal's Buttons Component]() Original publisher: [Read original article]() Author: Arit Developer Published: 2023-10-24T16:07:59Z Content type: tutorial Language: en Sources: [PayPal Technology]() Topics: [API](), [servers](), [Front end](), [HTML](), [npm](), [App]() Tags: [api](), [back-end](), [code](), [credentials](), [demo](), [e-commerce](), [ecommerce](), [environment](), [front-end](), [github](), [html](), [javascript](), [npm](), [package-json](), [payments](), [payments-technology](), [paypal](), [programming]() ### AI overview A tutorial for integrating PayPal Standard Checkout and its Payment Buttons component into a simple HTML and NodeJS shopping application. It covers prerequisites, sandbox credentials, backend and frontend setup, checkout flow, and custom integration guidance. ### Source excerpt Accepting online payments is now a universal must-have, catering to everyone from solo entrepreneurs to massive global corporations. PayPal's Standard Checkout allows for seamless integration of PayPal's Payment Buttons component into your e-commerce app, granting you the power to accept online payments. In this guide, I am going to show how to add Standard Checkout to a simple shopping app, built with HTML and NodeJS. Guide Overview Part 1. Prerequisites Part 2a. Basic Integration -- Code Setup Part 2b. Basic Integration -- Checkout Flow Part 3a. Custom Integration -- Code Setup Part 3b. Custom Integration -- Checkout Flow Part 4. Conclusion Part 5. Additional PayPal Payment Integrations Part 1. Prerequisites To complete this integration, you will need the following information: API Credentials (Client ID and Secret) for a PayPal REST app: paste these from your Developer Dashboard. Since we are working in a development environment in this demo, ensure that the Sandbox Toggle is on. Obtain Test API Credentials The username and password for a Personal Sandbox account: you will need this to complete the checkout process. Navigate to Sandbox Accounts under Testing ToolsObtain Personal Sandbox Account login details You can grab the code for our completed Checkout Integration demo from the PayPal Developer GitHub repository. Part 2a. Basic Integration -- Code Setup Navigate to PayPal's Integrate Checkout documentation. The documentation shows you how to set your development environment up: installing npm, verifying your package.json file, and setting up your .env file. Next, you will set up your back-end server and front-end code. The documentation presents the contents of three files: server.js (for the back-end server), app.js (for the client-side logic) and checkout.html (for the user interface). Copy the Backend CodeCopy the Frontend Code Grab these code snippets and paste them into your IDE (Integrated Development Environment). I strongly recommend that you implement the ## AI for Web Devs: Your First API Request to OpenAI DevFeed: [AI for Web Devs: Your First API Request to OpenAI]() Original publisher: [Read original article]() Author: Austin Published: 2023-09-19T11:53:28Z Content type: tutorial Language: en Sources: [Back End - Austin Gil]() Topics: [OpenAI](), [Qwik](), [API](), [Artificial Intelligence](), [API keys](), [Web Development]() Tags: [ai](), [api](), [api-keys](), [artificial-intelligence](), [back-end](), [coding](), [development](), [front-end](), [how-to](), [html](), [http](), [javascript](), [js](), [json](), [openai](), [programming](), [qwik](), [software](), [web-development]() ### AI overview A tutorial on integrating OpenAI API responses into a Qwik web application. It covers generating and protecting API keys, making a chat endpoint request with fetch, handling the JSON response, and beginning an interactive form. ### Source excerpt Make API request to OpenAI with fetch and Qwik forms, protect API keys with Qwik actions, and hide secrets with environment variables. ## AI for Web Devs: Project Introduction & Setup DevFeed: [AI for Web Devs: Project Introduction & Setup]() Original publisher: [Read original article]() Author: Austin Published: 2023-09-12T14:31:00Z Content type: tutorial Language: en Sources: [Back End - Austin Gil]() Topics: [Qwik](), [Artificial Intelligence](), [OpenAI](), [Web Development](), [JavaScript](), [Node.js](), [npm](), [Command-line interface](), [Tooling](), [Development]() Tags: [ai](), [artificial-intelligence](), [back-end](), [coding](), [development](), [front-end](), [html](), [javascript](), [js](), [node-js](), [npm](), [openai](), [programming](), [qwik](), [software](), [tooling](), [tutorial](), [web-development]() ### AI overview This tutorial series introduction explains how to prepare a Qwik web application for integrating OpenAI AI services. It covers the project goals, prerequisites, required Node.js and npm versions, OpenAI API access, and bootstrapping a Qwik app with the CLI. ### Source excerpt In this blog post, we start bootstrapping a web development project using Qwik and get things ready to incorporate AI tooling from OpenAI. ## From Monolith to Federation DevFeed: [From Monolith to Federation]() Original publisher: [Read original article]() Author: Daljit Summan Published: 2023-08-09T11:33:08Z Content type: tutorial Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [API](), [Back end]() Tags: [architecture](), [back-end](), [backend](), [data](), [gateway](), [graphql](), [incremental]() ### AI overview This article discusses using GraphQL Federation and the Strangler fig pattern to incrementally migrate a monolith. It describes placing a facade in front of the monolith, splitting it by domain, decoupling clients through a Federation interface, and routing data through an API Gateway. ### Source excerpt Introduction Many organizations own a Monolith (GraphQL or Non-GraphQL) and migrating away always seems an impossible task, most organizations fall into a seemingly endless amount of effort with very little progress to show for it. At Apollo we have seen many different patterns of migrating away from a monolith. ## File Upload Security and Malware Protection DevFeed: [File Upload Security and Malware Protection]() Original publisher: [Read original article]() Author: Austin Published: 2023-05-23T14:37:08Z Content type: tutorial Language: en Sources: [Back End - Austin Gil]() Topics: [Security](), [Node.js](), [Nuxt.js]() Tags: [back-end](), [coding](), [development](), [edge-compute](), [files](), [how-to](), [malware](), [malware-protection](), [node-js](), [nuxt](), [programming](), [recommendations](), [security](), [software](), [uploads](), [validation](), [web-development]() ### AI overview This tutorial explains how to secure web file uploads using OWASP recommendations. It covers extension validation and malware scanning in an application with a Nuxt.js backend using Node.js request handling. ### Source excerpt In this article, we implement several of the OWASP recommendations for file upload security. We also dive into malware scanning solutions. ## CDNs: Speed Up Performance by Reducing Latency DevFeed: [CDNs: Speed Up Performance by Reducing Latency]() Original publisher: [Read original article]() Author: Austin Published: 2023-05-01T14:57:05Z Content type: tutorial Language: en Sources: [Back End - Austin Gil]() Topics: [Latency](), [Cache](), [Cloud](), [cloud-infrastructure](), [cloud-computing]() Tags: [akamai](), [architecture](), [back-end](), [cache](), [cloud](), [cloud-computing](), [coding](), [development](), [latency](), [optimization](), [performance](), [programming](), [software](), [speed](), [uploads](), [web](), [web-development]() ### AI overview This tutorial explains how content delivery networks reduce latency for files stored in object storage. It describes caching copies near users and reports a reduction in one Japan-based request from 1.1 seconds to 0.2 seconds when served through a CDN. ### Source excerpt This post covers what CDNs are, how they work, and why you need one. I also show you how to connect Akamai CDN to Object Storage. ## Stream File Uploads to S3 Object Storage and Reduce Costs DevFeed: [Stream File Uploads to S3 Object Storage and Reduce Costs]() Original publisher: [Read original article]() Author: Austin Published: 2023-04-07T14:54:17Z Content type: tutorial Language: en Sources: [Back End - Austin Gil]() Topics: [Amazon S3](), [Node.js](), [cloud-infrastructure](), [distributed-systems]() Tags: [architecture](), [back-end](), [cloud-computing](), [coding](), [cost](), [development](), [hosting](), [node-js](), [object-storage](), [programming](), [s3](), [software](), [uploads](), [web-development]() ### AI overview A tutorial on uploading files from a Node.js application to S3-compatible Object Storage. It explains how object storage can centralize uploads, support distributed or serverless architectures, avoid application-server disk limits, and reduce storage costs. ### Source excerpt Learn how to upload files directly to S3-compatible Object Storage from your Node application to improve availability and reduce costs. ## Handling File Uploads on the Backend in Node.js (& Nuxt) DevFeed: [Handling File Uploads on the Backend in Node.js (& Nuxt)]() Original publisher: [Read original article]() Author: Austin Published: 2023-03-28T19:23:32Z Content type: tutorial Language: en Sources: [Back End - Austin Gil]() Topics: [Node.js](), [Nuxt.js](), [Tutorial](), [Back end](), [HTTP](), [Code]() Tags: [back-end](), [backend](), [coding](), [development](), [files](), [guide](), [http](), [javascript](), [js](), [node](), [node-js](), [nuxt](), [programming](), [software](), [streams](), [tutorial](), [uploads](), [web-development]() ### AI overview A tutorial on handling file uploads on the backend with Node.js and Nuxt.js. It explains how uploaded request data is received as chunks and streams, and introduces approaches for processing and saving the files. ### Source excerpt Learn about the low-level concepts for dealing with multipart/form-data in Node.js and how to save file uploads to disk with a high-level solution. ## Conditional API Responses For JavaScript vs. HTML Forms DevFeed: [Conditional API Responses For JavaScript vs. HTML Forms]() Original publisher: [Read original article]() Author: Austin Published: 2023-01-03T15:31:38Z Content type: tutorial Language: en Sources: [Back End - Austin Gil]() Topics: [Nuxt.js](), [API](), [Back end](), [HTTP](), [JavaScript](), [Forms]() Tags: [api](), [back-end](), [backend](), [building](), [coding](), [development](), [edge-compute](), [how-to](), [html](), [http](), [idea](), [javascript](), [js](), [programming](), [software](), [web-development]() ### AI overview A tutorial on detecting whether an HTTP request came from an HTML form or JavaScript in a Nuxt.js backend API. It explains returning redirects for form submissions and JSON for JavaScript requests, supporting progressive enhancement when JavaScript fails. ### Source excerpt Learn how to build backend APIs that support progressive enhancement by detecting if a request was submitted with HTML forms or JavaScript. ## DevOps at Findmypast: Postgres Database Upgrades DevFeed: [DevOps at Findmypast: Postgres Database Upgrades]() Original publisher: [Read original article]() Author: Robbie Hill Published: 2022-11-17T11:30:00Z Content type: article Language: en Sources: [Findmypast]() Topics: [Databases](), [DevOps](), [upgrade](), [Microservices](), [Kubernetes](), [Puppet](), [Ubuntu]() Tags: [back-end](), [clusters](), [configuration](), [databases](), [deployment](), [devops](), [engineering](), [findmypast](), [kubernetes](), [kubernetes-clusters](), [linux](), [microservices](), [mongodb](), [postgres](), [puppet](), [relational-databases](), [ubuntu](), [updates](), [upgrade](), [upgrades]() ### AI overview Findmypast describes its process for upgrading production and non-production Postgres databases. The article covers the database infrastructure, backup arrangements, Puppet-managed installations, version drift between environments, and the reasons for standardizing on the latest supported Postgres version. ### Source excerpt Introduction Findmypast and its sister site; the British Newspaper Archive (BNA), are served by a web of microservices operating across multiple Kubernetes clusters. A number of our microservices rely upon a back-end database, and although we do operate other database technologies (MSSQL, MongoDB etc.), Postgres is our de-facto standard for relational databases. When the DevOps team first realised the need to upgrade all of the database nodes to the latest Postgres version, we operated a total of twelve production Postgres databases, each running on their own dedicated Ubuntu Linux virtual machine (VM). Running on standalone VMs allows for separation of concerns, and limits the 'blast radius' of issues and failures should they occur. All VMs are managed by our Hyper-V cluster, and backed up regularly by Veeam. In addition to this backup method we operate Barman, which takes a full backup of all production Postgres database hosts nightly, and continuously receives WAL (Write Ahead Log) updates. We operate a a similar number of staging / integration / utility Postgres databases. Unlike the production databases these are (mostly) co-located on a single host, given the reduced storage and performance requirements of these databases. Existing Processes We manage Postgres installations and configuration through Puppet, pinning the installed version of Postgres. After the initial deployment we were not actively upgrading the Postgres version running on the hosts. Upgrades of the production databases were instead only undertaken by the feature teams (those teams that manage our micro-services), or by us when requested by the feature teams. This meant that we had a variety of Postgres databases deployed to production, between versions 9 and 14 (the latest supported version at the time). It also meant that the Production Postgres versions differed from their respective staging / integration database. We knew this situation, as well as the approach to upgrades was bad practice ## Online Payments with Square and React DevFeed: [Online Payments with Square and React]() Original publisher: [Read original article]() Author: Anthony Giuliano Published: 2022-11-17T05:00:00Z Content type: tutorial Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [Next.js](), [React](), [SDKs](), [API](), [Back end](), [Front end]() Tags: [api](), [apis](), [back-end](), [front-end](), [next-js](), [payments](), [react](), [sdk](), [tutorial]() ### AI overview This tutorial explains how to build an end-to-end online payment flow with Square and Next.js. It covers a React payment form, the Square Web Payments SDK, the Square Payments API, and processing on both the front end and back end. The described flow supports credit cards, Google Pay, and Apple Pay. ### Source excerpt Build an end-to-end payment flow with Square and Next.js. ## The Engineering Story Behind Flex Comp DevFeed: [The Engineering Story Behind Flex Comp]() Original publisher: [Read original article]() Author: Eric Poirier Published: 2022-10-05T18:00:02Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Shopify](), [Development](), [Back end](), [Code](), [ui]() Tags: [back-end](), [code](), [development](), [engineering](), [shopify](), [user-interface]() ### AI overview Shopify describes the engineering work behind Flex Comp, a compensation system that lets employees allocate their total rewards among base salary, Restricted Stock Units, and Stock Options. The article covers the product vision, employee-facing interface, delivery constraints, prioritized backlog, and the collaboration of front-end and back-end teams to solve technical challenges. ### Source excerpt How we built Flex Comp: Shopify's new approach to compensation that gives employees the ability to choose how they want to allocate their total reward between base salary, Restricted Stock Units (RSUs), and Stock Options today, with new features like Shop Cash in the future. [Next page]()