SShortSingh.
TopTechnologyAI & MLStartupsProgrammingScienceBusinessFinanceCrypto & Web3World
Back to feed
Programming

Nx Plugin for AWS 1.0, AWS Blocks, and Amplify Gen 2 compared on real deployments

0
·2 views

A developer tested all three AWS application scaffolding tools — Nx Plugin for AWS 1.0, AWS Blocks (preview), and Amplify Gen 2 — by deploying the same file portal scope on each and then deleting the stacks. All three deployed successfully, but meaningful differences only emerged after deletion, including log groups and KMS keys that persisted beyond stack removal. Amplify Gen 2 creates no perimeter resources by default, AWS Blocks replaces Amazon Cognito with a custom DynamoDB-based auth system, while Nx Plugin for AWS adds WAF web ACLs, Cognito with MFA, and four KMS keys — each contributing to fixed monthly costs even at zero requests. The underlying FSx for ONTAP S3 Access Point data path remained identical and untouched across all three tools, meaning switching scaffolding does not require rebuilding the storage layer. The author concludes that tool choice is reversible, but teams should account for what survives a stack deletion before committing to any option.

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)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Developer builds free browser-based motion design studio with no account required

A developer has built AtomCut, a free, browser-based motion design studio that started as a simple text animation tool and evolved into a full-featured platform. The tool runs entirely offline without requiring an account, and supports keyframe animation, watercolour painting, motion tracking, auto-captions, and export to MP4, GIF, SVG, and Lottie formats. Its architecture is built around a single pure rendering function and a versioned JSON document format, meaning the preview and export renderers are identical and old project files remain fully compatible. The developer credits a clean separation between animation logic and UI code as the key architectural decision that allowed features to expand without proportional growth in complexity. The project, whose original folder is still named 'typomation', reached schema version 71 while maintaining backward compatibility with files from its earliest builds.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Go web scraper Cinder rebrands as Tomoshibi with monorepo restructure

Developer Michael Obele has renamed his open-source Go-based web scraper, Cinder, to Tomoshibi — a Japanese word meaning lamp light — citing poor searchability and name collisions with other projects. The tool, which converts HTML into clean markdown for use with large language models, retains all existing API endpoints and functionality with no breaking changes. The rebrand also consolidates three previously separate repositories into a single monorepo containing the API, MCP server, and Svelte web playground. Existing users need only two lines of code to migrate, and old GitHub URLs, Docker tags, and environment variables continue to work as redirects or fallbacks. The project benchmarks at roughly 560 requests per second with a median latency of 11 milliseconds in self-hosted testing.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Third-Party Listicles Drive 85% of AI Citations in GEO Experiments, Study Finds

Two generative engine optimization experiments published by Search Engine Land on September 14, 2026, found that external editorial sources — not brand-owned content — were the primary drivers of early AI search visibility. In a 30-day cold-start test for a SaaS link-building agency with no prior AI presence, third-party listicles accounted for 85.8% of citation mentions across six AI platforms, while the brand's own listicle contributed just 14% and PR a negligible 0.2%. A parallel test tracking an established consultant brand across ChatGPT, Claude, Gemini, and Perplexity logged 775 citation events and similarly found external listicles to be a leading source, with PR and listicles reinforcing each other. Researchers also observed that roughly half of cited sources dropped out within 30 days, indicating that AI visibility can be unstable and may not persist after a single placement. The findings suggest that for brands with little or no AI-search presence, earning placements on authoritative third-party sources is a more effective early strategy than publishing additional owned content.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

How a developer's frontmatter block grew organically across four origins and nine fields

A developer tracing the history of their Markdown frontmatter found that none of its nine metadata fields were centrally designed — each emerged from a different project, template, or automated hook between August and September. The fields originated in four distinct places, spread through separate mechanisms including scaffolds, sync scripts, and session-closing hooks. Gaps in adoption revealed silent failures: a regex bug swallowed start-date fields in 254 of 260 sessions, and a two-field classification system was never read by any script despite being defined as 'metadata'. By contrast, four note-identifying fields enforced their own presence by breaking the build when missing, ensuring they stayed accurate and in use. The author concludes that a metadata field survives not by design intent but by whether something or someone still reads it.

0 comments Read more at DEV Community