# fabric Published articles for fabric. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## AI-Ready Private Cloud with Cisco and VMware DevFeed: [AI-Ready Private Cloud with Cisco and VMware]() Original publisher: [Read original article]() Author: sabina anja Published: 2026-09-08T15:33:39Z Content type: article Language: en Sources: [VMware Blogs]() Topics: [Artificial Intelligence](), [Network](), [Cloud](), [networking](), [cloud-infrastructure](), [distributed-training](), [datacenter](), [GPU](), [Latency](), [Inference](), [model-deployment](), [inference-endpoints]() Tags: [ai](), [cisco](), [cloud](), [cloud-infrastructure](), [cloud-platform](), [data-center](), [distributed-training](), [fabric](), [gpu](), [home-page](), [inference](), [inference-endpoints](), [latency](), [networking](), [object-storage](), [pipelines](), [private-cloud](), [telemetry](), [vcf-9-1](), [vcf-networking](), [vmware](), [vmware-cloud-foundation]() ### AI overview This article explains why an AI-ready private cloud requires more than adding GPUs. It focuses on how Broadcom and Cisco are integrating VMware Cloud Foundation with Cisco Nexus One Fabric to address AI workload networking, including bandwidth-intensive east-west traffic, bursty north-south traffic, latency, congestion management, and telemetry across virtual and physical infrastructure. ### Source excerpt An AI-ready private cloud is not simply a private cloud with GPUs added to it. What determines whether a private cloud platform can actually serve AI workloads effectively is everything built around them: how the fabric carries traffic, how the tenancy model lets teams consume capacity, and how policy and telemetry stay coherent across the ... Continued The post AI-Ready Private Cloud with Cisco and VMware appeared first on VMware Blogs. ## Fat Rail vs Thin Rail in AI compute clusters DevFeed: [Fat Rail vs Thin Rail in AI compute clusters]() Original publisher: [Read original article]() Author: j2sw Published: 2026-07-01T07:30:18Z Content type: tutorial Language: en Sources: [Justin Wilson (j2sw)]() Topics: [Artificial Intelligence](), [Job](), [datasets]() Tags: [400g](), [ai](), [cluster](), [clusters](), [compute](), [data](), [fabric](), [fat-rail](), [internet-architecture](), [switching](), [thin-rail]() ### AI overview The article explains "fat" and "thin" rails in AI compute clusters. The terms describe whether a node's connection to the fabric provides sufficient bandwidth for the workload, with the practical distinction determined by node-to-node traffic rather than cable count alone. ### Source excerpt We are starting to hear about "Thin" and "Fat" rails in AI fabrics. These are just another way to say a connection from compute into the Fabric. The link either has sufficient capacity (Fat) or insufficient capacity (Thin). A thin rail provides the node with a single path into the fabric. That may be one ... Read more The post Fat Rail vs Thin Rail in AI compute clusters appeared first on Justin Wilson (j2sw). ## AWS's ShuffleBox Data Center Fabric Does Not Replace Leaf-and-Spine Networks DevFeed: [AWS's ShuffleBox Data Center Fabric Does Not Replace Leaf-and-Spine Networks]() Original publisher: [Read original article]() Published: 2026-06-10T05:42:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Networks](), [networking](), [Optimization](), [Amazon Web Services](), [datacenter]() Tags: [aws](), [blog](), [data-center](), [fabric](), [networks](), [optimization](), [routing]() ### AI overview This commentary examines an AWS proposal for aggregation fabrics using a prewired ShuffleBox and lane splitting instead of traditional spine switches. It argues that the approach resembles Plexxi's earlier data center fabric designs and that routing through randomness alone may not provide enough link utilization without traffic engineering. ### Source excerpt A friend of mine sent me links to a new paper published by AWS engineers, and an associated LinkedIn post which claims: We got lean, resilient, massive aggregation fabrics that provide 33% better throughput with 69% fewer routers, savings 27% of costs, cutting power usage by 40%, and reducing CO2 emissions. The obvious question one should ask after reading the hyperventilated Radical Network Redesign blog post is thus: is this the end of leaf-and-spine networks? Of course not. Let's go into the details. Read more ... ## A Critical Review of Rail-Optimized Networking for AI Training Workloads DevFeed: [A Critical Review of Rail-Optimized Networking for AI Training Workloads]() Original publisher: [Read original article]() Published: 2026-04-21T05:44:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [networking](), [Artificial Intelligence]() Tags: [ai](), [data-center](), [fabric](), [networking](), [worth-reading]() ### AI overview The article argues that rail-optimized networking for AI training may largely reflect smart workload placement within a conventional leaf-and-spine fabric rather than a novel networking design. It also questions whether some proposed intra-server traffic paths are networking solutions or application-level RDMA techniques, and notes that related ideas predate the current discussion. ### Source excerpt Phil Gervasi wrote an interesting article describing Rail-Optimized Networking for AI Training Workloads. Go read it first; I'll wait. Does it sound interesting? Were you able to see behind the curtain and figure out what it's really about? Read more ... ## ClickHouse Announces Integration with Microsoft OneLake for Federated Analytics DevFeed: [ClickHouse Announces Integration with Microsoft OneLake for Federated Analytics]() Original publisher: [Read original article]() Author: Melvyn Peignon Published: 2025-11-18T00:00:00Z Content type: release Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [interoperability](), [Microsoft](), [data lake](), [real-time](), [Apache Iceberg]() Tags: [apache-iceberg](), [clickhouse](), [data-lake](), [databases](), [fabric](), [integration](), [interoperability](), [latency](), [microsoft](), [real-time]() ### AI overview ClickHouse announced an integration with Microsoft OneLake, the unified data lake service within Microsoft Fabric. The integration exposes OneLake Iceberg tables to ClickHouse so users can query and analyze data across ClickHouse and Fabric, supporting real-time analytical workloads. ### Source excerpt ClickHouse today announced the availability of a powerful new integration with Microsoft OneLake, the unified data lake service within Microsoft Fabric. ## EVPN Designs: Scaling IBGP with Route Reflectors DevFeed: [EVPN Designs: Scaling IBGP with Route Reflectors]() Original publisher: [Read original article]() Published: 2024-09-05T09:47:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [evpn](), [BGP](), [Network](), [interoperability](), [GitHub]() Tags: [bgp](), [design](), [evpn](), [evpn-designs](), [fabric](), [github](), [netlab](), [network](), [route](), [vxlan]() ### AI overview This tutorial explains how to scale an IBGP-based EVPN leaf-and-spine fabric by using spine switches as BGP route reflectors. It discusses placement considerations, interoperability and control-plane limits, then demonstrates the design with a netlab lab topology and optional GitHub Codespaces support. ### Source excerpt In the previous blog posts, we explored the simplest possible IBGP-based EVPN design and tried to figure out whether BGP route reflectors do more harm than good. Ignoring that tiny detail for the moment, let's see how we could add route reflectors to our leaf-and-spine fabric. As before, this is the fabric we're working with: Read more ... ## Response: The Usability of VXLAN DevFeed: [Response: The Usability of VXLAN]() Original publisher: [Read original article]() Published: 2024-08-12T05:50:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [VXLAN](), [networking](), [datacenter](), [Scalability](), [IP routing]() Tags: [data-center](), [fabric](), [ip-routing](), [network](), [networking](), [routing](), [scalability](), [vxlan]() ### AI overview The article argues that VXLAN can be useful even when an enterprise network is not reaching VLAN scalability limits. It identifies VLAN-only data center fabrics' reliance on STP and MLAG as significant drawbacks, and explains that VXLAN fabric transport enables IP routing and ECMP load balancing. It also notes that small VXLAN fabrics do not necessarily need EVPN. ### Source excerpt Wes made an interesting comment to the Migrating a Data Center Fabric to VXLAN blog post: The benefit of VXLAN is mostly scalability, so if your enterprise network is not scaling... just don't. The migration path from VLANs is to just keep using VLANs. The (vendor-driven) networking industry has a huge blind spot about this. Paraphrasing the famous Dinesh Dutt's Autocon1 remark: I couldn't disagree with you more. Read more ... ## The Mythical Use Cases: Traffic Engineering for Data Center Backups DevFeed: [The Mythical Use Cases: Traffic Engineering for Data Center Backups]() Original publisher: [Read original article]() Published: 2024-06-11T10:41:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [networking](), [datacenter](), [Disk image]() Tags: [backups](), [cisco](), [data-center](), [fabric](), [ipv6](), [network](), [routing](), [server](), [storage](), [tcp](), [traffic-engineering]() ### AI overview This commentary argues that high-volume in-band backups are an overstated justification for complex traffic-engineering features in data center fabrics. It explains that backup-server and storage performance, TCP session distribution, link ratios, dynamic load balancing, and routing can limit or spread the resulting traffic. ### Source excerpt Vendor product managers love discussing mythical use cases to warrant complex functionality in their gear. Long-distance VM mobility was one of those (using it for disaster avoidance was Mission Impossible under any real-world assumptions), and high-volume network-based backups seems to be another. Here's what someone had to say about that particular unicorn in a LinkedIn comment when discussing whether we need traffic engineering in a data center fabric. When you're dealing with a large cluster on a fabric, you will see things like inband backup. The most common one I've seen is VEEAM. Those inband backups can flood a single link, and no amount of link scheduling really solves that; depending on the source, they can saturate 100G. There are a couple of solutions; IPv6 or eBGP SID has been used to avoid these links or schedule avoidance for other traffic. It is true that (A) in-band backups can be bandwidth intensive and that (B) well-written applications can saturate 100G server links. However: Read more ... ## MLAG Deep Dive: LAG Member Failures in VXLAN Fabrics DevFeed: [MLAG Deep Dive: LAG Member Failures in VXLAN Fabrics]() Original publisher: [Read original article]() Published: 2024-05-15T06:51:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [VXLAN](), [evpn]() Tags: [complexity](), [deep-dive](), [evpn](), [fabric](), [failover](), [flow](), [implementation](), [mac](), [switching](), [vxlan]() ### AI overview This article explains how MLAG handles LAG member failures in VXLAN fabrics, including behavior with EVPN. Traffic can fail over over the MLAG peer link without interrupting unicast forwarding, while EVPN convergence may require updated advertisements for an optimized path. The article notes that EVPN-only multihoming presents a less favorable situation. ### Source excerpt In the Dealing with LAG Member Failures blog post, we figured out how easy it is to deal with a LAG member failure in a traditional MLAG cluster. The failover could happen in hardware, and even if it's software-driven, it does not depend on the control plane. Let's add a bit of complexity and replace a traditional layer-2 fabric with a VXLAN fabric. The MLAG cluster members still use an MLAG peer link and an anycast VTEP IP address (more details). Read more ... ## Why Are We Using EVPN Instead of SPB or TRILL? DevFeed: [Why Are We Using EVPN Instead of SPB or TRILL?]() Original publisher: [Read original article]() Published: 2024-04-05T06:17:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [evpn](), [networking](), [VXLAN](), [IS-IS](), [Routing (disambiguation)](), [BGP]() Tags: [bgp](), [bridging](), [evpn](), [fabric](), [gre](), [is-is](), [mpls](), [network](), [routing](), [vxlan]() ### AI overview The article explains why EVPN, particularly with VXLAN encapsulation, became preferable to SPB and TRILL. It contrasts their encapsulation, control-plane, deployment, and transport requirements, and notes that VXLAN separates edge virtual networks from the physical transport core. ### Source excerpt Dan left an interesting comment on one of my previous blog posts: It strikes me that the entire industry lost out when we didn't do SPB or TRILL. Specifically, I like how Avaya did SPB. Oh, we did TRILL. Three vendors did it in different proprietary ways, but I'm digressing. Read more ... ## netlab: Building Leaf-and-Spine Fabrics with the Fabric Plugin DevFeed: [netlab: Building Leaf-and-Spine Fabrics with the Fabric Plugin]() Original publisher: [Read original article]() Published: 2024-03-25T08:43:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [networking](), [evpn](), [BGP](), [Ansible](), [Linux](), [Containers]() Tags: [ansible](), [bgp](), [containers](), [evpn](), [fabric](), [linux](), [netlab](), [ospf]() ### AI overview This tutorial explains how netlab 1.7.0's fabric plugin builds leaf-and-spine lab topologies. It covers generating and renaming leaf and spine nodes, adding EVPN with IBGP and OSPF, attaching Linux hosts, and running the example with Ubuntu, Ansible, containerlab, and Arista cEOS containers. ### Source excerpt netlab release 1.7.0 added the fabric plugin that simplifies building lab topologies with leaf-and-spine fabrics. All you have to do to build a full-blown leaf-and-spine fabric is: Specify the default device type Enable the fabric plugin Specify the number of leaves and spines in the fabric. For example, the following lab topology builds a fabric with Arista cEOS containers having two spines and four leaves: Read more ... ## Data Center Fabric Designs: Size Matters DevFeed: [Data Center Fabric Designs: Size Matters]() Original publisher: [Read original article]() Published: 2024-03-14T07:55:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [data centers](), [Architecture & Design](), [Networks](), [vendor lock-in](), [Streaming]() Tags: [architecture-design](), [data-center](), [design](), [evpn](), [fabric](), [networks](), [streaming](), [vendor-lock-in]() ### AI overview The article argues that the appropriate data center fabric design depends on network size and operational complexity. Mixing vendors may help large streaming services avoid vendor lock-in, reduce prices, and address supply-chain issues, but it is usually impractical for enterprise data centers because the operational costs of multiple operating systems, support centers, and tooling can outweigh acquisition savings. ### Source excerpt The "should we use the same vendor for fabric spines and leaves?" discussion triggered the expected counterexamples. Here's one: I actually have worked with a few orgs that mix vendors at both spine and leaf layer. Can't take names but they run fairly large streaming services. To me it seems like a play to avoid vendor lock-in, drive price points down and be in front of supply chain issues. As always, one has to keep two things in mind: Read more ... ## Elevating data fabric to data mesh: Solving data needs in hybrid data lakes DevFeed: [Elevating data fabric to data mesh: Solving data needs in hybrid data lakes]() Original publisher: [Read original article]() Author: Sajuman Joseph, Brian Olsen Published: 2022-12-07T00:00:00Z Content type: article Language: en Sources: [Trino Blog]() Topics: [data](), [migration](), [datasets](), [Data Quality](), [Architecture & Design](), [Security](), [audit trail](), [cloud-infrastructure]() Tags: [architecture](), [audit-trail](), [cloud](), [cloud-storage](), [compliance](), [data](), [fabric](), [governance](), [logs](), [mesh](), [migration](), [overview](), [policy](), [recap](), [retention](), [security](), [technical]() ### AI overview This article recaps a Comcast presentation about migrating from a data fabric architecture to a data mesh using Trino. It explains how domain ownership, data quality checks, metadata, access policies, catalogs, audit trails, and governance support data products across on-premises and cloud storage. ### Source excerpt Tune in for the next post in the Trino Summit 2022 recap series. In this post, we're joining Saj from Comcast, to talk about their migration from a data fabric to data mesh. Saj shows you that there is more to the buzzword than meets the eye. He gives a solid overview of why Comcast is taking data mesh to heart. ## 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). ## It's Time to Upgrade to the New Firebase Crashlytics SDK! DevFeed: [It's Time to Upgrade to the New Firebase Crashlytics SDK!]() Original publisher: [Read original article]() Author: Oleg Kodysh Published: 2020-10-22T00:00:00Z Content type: release Language: en Sources: [Firebase Blog]() Topics: [Crashlytics](), [Firebase](), [SDKs](), [Android](), [Android Gradle Plugin](), [Gradle](), [iOS](), [macOS](), [tvOS](), [watchOS]() Tags: [android](), [android-gradle-plugin](), [android-studio](), [build](), [crashlytics](), [fabric](), [firebase](), [gradle](), [ios](), [macos](), [news](), [sdk](), [tutorials](), [updates](), [upgrade](), [watchos]() ### AI overview Firebase encourages developers to migrate from the deprecated Fabric SDK to the Firebase Crashlytics SDK before the legacy SDK is sunset. The article describes crash-reporting, build-plugin, symbol-upload, and multi-platform improvements. ### Source excerpt News, tutorials, and updates from the Firebase team. ## How Twitter is using the new iOS SDK from Firebase App Distribution DevFeed: [How Twitter is using the new iOS SDK from Firebase App Distribution]() Original publisher: [Read original article]() Author: Alex Singer Published: 2020-09-30T00:00:00Z Content type: article Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [iOS](), [SDK]() Tags: [app-distribution](), [case-study](), [crashlytics](), [fabric](), [firebase](), [ios](), [news](), [sdk](), [updates]() ### AI overview The article explains how Twitter uses the Firebase App Distribution iOS SDK in nightly builds to help testers receive and install updated app versions directly within the test app. It also describes how the SDK reduces reliance on email notifications and supports a customizable testing experience. ### Source excerpt News, tutorials, and updates from the Firebase team. ## What's new at Firebase Summit 2019 DevFeed: [What's new at Firebase Summit 2019]() Original publisher: [Read original article]() Author: Francis Ma Published: 2019-09-26T00:00:00Z Content type: news Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [Mobile](), [Web](), [Google Cloud Platform (GCP)]() Tags: [android](), [app-distribution](), [app-quality](), [cloud-messaging](), [community](), [emulator-suite](), [extensions](), [fabric](), [fastlane](), [firebase](), [firebase-cli](), [firebase-summit](), [google-analytics](), [ios](), [machine-learning](), [mobile](), [news](), [open-source](), [predictions](), [react](), [react-native](), [realtime-database](), [remote-config](), [sdks](), [security-rules](), [test-lab](), [unity](), [updates](), [web]() ### AI overview Firebase Summit 2019 updates introduced Firebase Extensions, open-source bundles that automate common app development tasks, and expanded the Firebase Emulator Suite with hot reloading for Security Rules and broader client and server-side SDK support. ### Source excerpt News, tutorials, and updates from the Firebase team. ## What's new from Firebase at Google I/O 2019 DevFeed: [What's new from Firebase at Google I/O 2019]() Original publisher: [Read original article]() Author: Francis Ma Published: 2019-05-07T00:00:00Z Content type: release Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [ML Kit](), [API](), [Google](), [object-detection](), [Mobile]() Tags: [c-plus-plus](), [crashlytics](), [emulator-suite](), [fabric](), [firebase](), [firestore](), [google](), [google-analytics](), [google-i-o](), [launch](), [machine-learning](), [ml-kit](), [mobile](), [object-detection](), [on-device](), [performance-monitoring](), [test-lab](), [updates]() ### AI overview Firebase announces its biggest Google I/O 2019 updates, including new ML Kit beta capabilities for on-device translation, real-time object detection and tracking, and custom image classification with AutoML Vision Edge. ### Source excerpt News, tutorials, and updates from the Firebase team. ## Firebase launches In-App Messaging and announces Crashlytics integrations and other product updates DevFeed: [Firebase launches In-App Messaging and announces Crashlytics integrations and other product updates]() Original publisher: [Read original article]() Author: Francis Ma Published: 2018-08-16T00:00:00Z Content type: release Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [Messaging](), [Mobile](), [App](), [Google Analytics]() Tags: [android](), [app-quality](), [bigquery](), [cloud-functions](), [cloud-messaging](), [cloud-next](), [community](), [crash-reporting](), [crashlytics](), [data-studio](), [fabric](), [firebase](), [firebase-cli](), [firebase-summit](), [firestore](), [google-analytics](), [hosting](), [in-app-messaging](), [ios](), [machine-learning](), [mobile](), [predictions](), [realtime-database](), [remote-config](), [unity](), [web]() ### AI overview Firebase announces the launch of Firebase In-App Messaging, which lets app teams send targeted, contextual messages to users who are actively using their apps. The update also covers integrations with Google Analytics for Firebase and Firebase Predictions, along with improvements to Firebase Cloud Messaging reporting and APIs. ### Source excerpt News, tutorials, and updates from the Firebase team. ## Updates to the Firebase console DevFeed: [Updates to the Firebase console]() Original publisher: [Read original article]() Author: John Shriver-Blake Published: 2017-11-13T00:00:00Z Content type: news Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [dashboards](), [User Experience]() Tags: [analytics](), [dashboards](), [fabric](), [firebase](), [firebase-console](), [graphs](), [launch](), [metrics](), [navigation](), [updates]() ### AI overview Firebase describes improvements to its console, including redesigned navigation, a Project Home screen with key app metrics and trend graphs, a Latest Release dashboard, and an Analytics dashboard organized around user questions. ### Source excerpt News, tutorials, and updates from the Firebase team. ## What's new at Firebase Dev Summit 2017 DevFeed: [What's new at Firebase Dev Summit 2017]() Original publisher: [Read original article]() Author: Francis Ma Published: 2017-10-31T00:00:00Z Content type: news Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [Cloud Functions](), [Google](), [App]() Tags: [2017](), [a-b-testing](), [android](), [app-quality](), [cloud-functions](), [cloud-messaging](), [community](), [crashlytics](), [fabric](), [firebase](), [firebase-summit](), [games](), [google](), [hosting](), [ios](), [machine-learning](), [news](), [predictions](), [remote-config](), [summit](), [web]() ### AI overview Firebase announces updates presented at Firebase Dev Summit 2017, including Crashlytics integration, first-class A/B testing support, and Predictions, a product bringing Google machine learning capabilities to Firebase. ### Source excerpt News, tutorials, and updates from the Firebase team. ## Faster automated screenshots: fastlane's snapshot now supports multiple concurrent simulators DevFeed: [Faster automated screenshots: fastlane's snapshot now supports multiple concurrent simulators]() Original publisher: [Read original article]() Author: David Ohayon Published: 2017-08-29T00:00:00Z Content type: news Language: en Sources: [Firebase Blog]() Topics: [iOS](), [Xcode](), [Mobile](), [releases]() Tags: [automated](), [concurrent](), [fabric](), [fastlane](), [firebase](), [ios](), [launch](), [news](), [screenshots](), [updates](), [xcode]() ### AI overview The article announces that fastlane's snapshot tool supports multiple concurrent iOS simulators in Xcode 9, allowing screenshots for specified devices to be generated simultaneously. ### Source excerpt News, tutorials, and updates from the Firebase team. ## Firebase Dev Summit 2017 in Amsterdam! DevFeed: [Firebase Dev Summit 2017 in Amsterdam!]() Original publisher: [Read original article]() Author: Frank van Puffelen Published: 2017-08-09T00:00:00Z Content type: news Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [Development](), [App]() Tags: [2017](), [announcements](), [app-development](), [authentication](), [community](), [dev](), [fabric](), [firebase](), [firebase-summit](), [news](), [summit]() ### AI overview Firebase announces that registration is open for the Firebase Dev Summit in Amsterdam on October 31, 2017. The event will include talks, codelabs, office hours, an after-party, and opportunities for developers to provide feedback to the Firebase team. ### Source excerpt News, tutorials, and updates from the Firebase team. ## Relive the Firebase + Fabric party at WWDC17 DevFeed: [Relive the Firebase + Fabric party at WWDC17]() Original publisher: [Read original article]() Author: Megan Krilanovich Published: 2017-06-20T00:00:00Z Content type: news Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [iOS](), [Development](), [App]() Tags: [apple](), [community](), [developers](), [development](), [fabric](), [firebase](), [ios](), [iphone](), [multiplayer](), [news](), [wwdc]() ### AI overview Firebase recaps its WWDC17 party for the iOS developer community, describing the event's activities, including project showcases, a cooperative multiplayer game, an app live-coding demonstration, and attendee reactions. ### Source excerpt News, tutorials, and updates from the Firebase team. [Next page]()