# ecosystems Published articles for ecosystems. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## The expanding threat landscape: Chainguard now scans source code for traditional malware and "greyware" DevFeed: [The expanding threat landscape: Chainguard now scans source code for traditional malware and "greyware"]() Original publisher: [Read original article]() Published: 2026-06-09T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [Malware](), [Code](), [Open Source](), [npm](), [npm packages](), [Security]() Tags: [chainguard](), [chainguard-libraries](), [ecosystems](), [greyware](), [greyware-scanner](), [hardening](), [javascript](), [malware](), [malware-prevention](), [malware-scanner](), [npm](), [npm-packages](), [open-source](), [packages](), [scanner](), [security](), [source](), [supply-chain-attacks]() ### AI overview Chainguard has introduced a source code scanner that detects traditional malware and "greyware," harmful packages that may perform actions such as credential theft, command interception, API key harvesting, or persistent remote access. The scanner currently protects npm packages, scans more than 100,000 packages daily, and has blocked more than 52,000 packages identified as malware or greyware. ### Source excerpt Chainguard's new scanner blocks malware and 'greyware' before it reaches developers, protecting 100,000+ packages daily across open source ecosystems. ## Transforming Capital One's Data Marketplace with Embedded Governance and a Product Mindset DevFeed: [Transforming Capital One's Data Marketplace with Embedded Governance and a Product Mindset]() Original publisher: [Read original article]() Author: Valeria Gomez Published: 2026-01-13T13:34:19Z Content type: article Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [Architecture & Design](), [Orchestration](), [Microservices](), [data]() Tags: [apis](), [apollo-federation](), [dashboards](), [data](), [ecosystems](), [events](), [governance](), [graphql](), [latency](), [low-latency](), [microservices](), [orchestration](), [performance](), [platform](), [product-mindset](), [reuse](), [router](), [scale]() ### AI overview A recap of GraphQL Summit 2025 describing how Capital One used GraphQL, Apollo Federation, and Apollo Router to build an enterprise data marketplace. The approach centralized orchestration across microservices, applied company standards, improved data discoverability and reuse, and was validated with a production-traffic rollout showing low latency, high throughput, and no disruption to live workloads. ### Source excerpt A recap from GraphQL Summit 2025 on how Capital One applied a product mindset to build an enterprise data marketplace powered by Apollo Large organizations with complex data ecosystems often face a familiar challenge. As systems evolve over time, data becomes harder to find, harder to trust, and harder to use. Teams build APIs independently, integrations multiply, and identifying the authoritative source of data can take significant effort. ## Building an Enterprise Data Warehouse on Heroku: From Complex ETL to Seamless Salesforce Integration DevFeed: [Building an Enterprise Data Warehouse on Heroku: From Complex ETL to Seamless Salesforce Integration]() Original publisher: [Read original article]() Author: Sudarshan Hiray Published: 2025-11-05T20:05:38Z Content type: article Language: en Sources: [Heroku]() Topics: [Heroku](), [data-architecture](), [Databases](), [Monitoring]() Tags: [analytics](), [applications](), [article](), [building](), [data](), [ecosystems](), [engineering](), [enterprise](), [etl](), [heroku](), [heroku-postgres](), [integration](), [platforms](), [salesforce](), [services](), [systems](), [tools](), [warehouse]() ### AI overview Heroku describes an enterprise data warehouse architecture that unifies Salesforce and data from multiple application databases for real-time analytics. The approach uses Heroku Connect, Heroku Postgres follower databases, and a unified analytics platform to address API limits, ETL complexity, production database load, and fragmented monitoring. ### Source excerpt Modern businesses don't just run on Salesforce--they run on entire ecosystems of applications. At Heroku, we operate dozens of services alongside our Salesforce instance such as billing systems, user management platforms, analytics engines, and support tools. Traditional approaches to unifying this data create more problems than they solve. In this article, we'll see how we [...] The post Building an Enterprise Data Warehouse on Heroku: From Complex ETL to Seamless Salesforce Integration appeared first on Heroku. ## Platform Strategy, JavaScript-First Development, and the Web's Mobile Constraints DevFeed: [Platform Strategy, JavaScript-First Development, and the Web's Mobile Constraints]() Original publisher: [Read original article]() Author: Alex Russell Published: 2024-10-27T00:00:00Z Content type: opinion Language: en Sources: [Alex Russell]() Topics: [JavaScript](), [Front end](), [Web Development](), [Development](), [Mobile](), [Web](), [React]() Tags: [browsers](), [competition](), [cost](), [development](), [ecosystems](), [frontend](), [javascript](), [legacy](), [mobile](), [performance](), [speed](), [strategy](), [web](), [web-developers](), [webdev]() ### AI overview The article argues that JavaScript-first frontend practices and desktop-oriented tools have contributed to increasingly costly failures to deliver usable web experiences on phones. It frames platform strategy around making the web easier, faster, and more secure for everyday tasks. ### Source excerpt This post is an edited and expanded version of a now-mangled Mastodon thread. Contents Platforms Are Competitions ...and We're Losing Win Condition You Do It To Yourself, And That's What Really Hurts Groundhog Day Reboot Some in the JavaScript community imagine that I harbour an irrational dislike of their tools when, in fact, I want nothing more than to stop thinking about them. Live-and-let-live is excellent guidance, and if it weren't for React et. al.'s predictably ruinous outcomes, the public side of my work wouldn't involve educating about the problems JS-first development has caused. But that's not what strategy demands, and strategy is my job.1 I've been holding my fire (and the confidences of consulting counterparties) for most of the last decade. Until this year, I only occasionally posted traces documenting the worsening rot. I fear this has only served to make things look better than they are. Over the past decade, my work helping teams deliver competitive PWAs gave me a front-row seat to a disturbing trend. The rate of failure to deliver usable experiences on phones was increasing over time, despite the eye-watering cost of JS-based stacks teams were reaching for. Worse and costlier is a bad combo, and the opposite of what competing ecosystems did. Native developers reset hard when moving from desktop to mobile, getting deeply in touch with the new constraints. Sure, developing a codebase multiple times is more expensive than the web's write-once-test-everywhere approach, but at least you got speed for the extra cost. That's not what web developers did. Contemporary frontend practice pretended that legacy-oriented, desktop-focused tools would perform fine in this new context, without ever checking if they did. When that didn't work, the toxic-positivity crowd blamed the messenger.2 Frontend's tragically timed turn towards JavaScript means the damage isn't limited to the public sector or "bad" developers. Some of the strongest engineers I know find thems ## Europe's cloud dependence and the case for specialized European cloud services DevFeed: [Europe's cloud dependence and the case for specialized European cloud services]() Original publisher: [Read original article]() Published: 2024-01-11T08:27:14Z Content type: opinion Language: en Sources: [Bert Hubert's writings]() Topics: [Cloud](), [Computing]() Tags: [article](), [business](), [cloud](), [collaboration](), [communication](), [computing](), [ecosystems](), [europe](), [hyperscaler](), [innovation](), [policy](), [procurement](), [providers]() ### AI overview This opinion article argues that Europe depends on major non-European hyperscaler cloud providers and cannot realistically create a competing mega-cloud through legislation, standardisation, procurement, or coordinated government action. It suggests that specialized European email, communication, and collaboration services could provide a more feasible starting point for a European cloud ecosystem. ### Source excerpt This article is part of a series on (European) innovation and capabilities. The very short version: All of computing is moving to the cloud at a rapid pace, including (government) parts you might want to keep under your own control Europe has no relevant 'hyperscaler' cloud providers at all, and there is a desire to change this by policy means Competing with the IKEA-concept is nearly impossible. Offering IKEA-like products but then with a smaller range is not an attractive proposition. ## Matter: Multi-Admin, Identifiers, and Fabrics DevFeed: [Matter: Multi-Admin, Identifiers, and Fabrics]() Original publisher: [Read original article]() Author: John Lee Published: 2022-01-18T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [Matter](), [configuration](), [Network]() Tags: [blog](), [certificates](), [configuration](), [devices](), [ecosystems](), [esp32](), [fabric](), [identity](), [iot](), [matter](), [network](), [node]() ### AI overview This article explains how Matter multi-admin devices identify and authenticate across multiple ecosystems. It covers operational credentials, Node Operational Certificates, node identifiers, Matter fabrics, Root CA certificates, and commissioning. ### Source excerpt [This is article #6 in the Espressif Matter Series of articles. You may read the first part here.] In the previous articles we talked about Matter devices communicating with each other by themselves, or Matter devices participating in multiple ecosystems simultaneously. As you can see in the image here, this lightbulb is part of 2 distinct ecosystems, green and red. Each of these ecosystems don't know about the other, and they are powered by 2 separate organisations (Org1 and Org2).