<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Firebase on Brave New Geek</title><link>https://bravenewgeek.com/tag/firebase/</link><description>Recent content in Firebase on Brave New Geek</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 11 Oct 2019 11:53:34 -0500</lastBuildDate><atom:link href="https://bravenewgeek.com/tag/firebase/index.xml" rel="self" type="application/rss+xml"/><item><title>Serverless on GCP</title><link>https://bravenewgeek.com/serverless-on-gcp/</link><pubDate>Tue, 20 Aug 2019 10:04:48 -0500</pubDate><guid>https://bravenewgeek.com/serverless-on-gcp/</guid><description>&lt;p&gt;Like many other marketing buzzwords, the concept of “serverless” has taken on a life of its own, which can make it difficult to understand what serverless actually &lt;em&gt;means&lt;/em&gt;. What it really means is that the cloud provider fully manages server infrastructure all the way up to the application layer. For example, GCE isn’t serverless because, while Google manages the &lt;em&gt;physical&lt;/em&gt; server infrastructure, we still have to deal with patching operating systems, managing load balancers, configuring firewall rules, and so on. Serverless means we merely worry about our application code and business logic and nothing else. This concept extends beyond pure compute though, including things like databases, message queues, stream processing, machine learning, and other types of systems.&lt;/p&gt;</description></item></channel></rss>