Podcasts about firestore

Arnaud et Emmanuel discutent des nouvelles de ce mois. On y parle intégrité de JVM, fetch size de JDBC, MCP, de prompt engineering, de DeepSeek bien sûr mais aussi de Maven 4 et des proxy de répository Maven. Et d'autres choses encore, bonne lecture. Enregistré le 7 février 2025 Téléchargement de l'épisode LesCastCodeurs-Episode-322.mp3 ou en vidéo sur YouTube. News Langages Les evolutions de la JVM pour augmenter l'intégrité https://inside.java/2025/01/03/evolving-default-integrity/ un article sur les raisons pour lesquelles les editeurs de frameworks et les utilisateurs s'arrachent les cheveux et vont continuer garantir l'integrite du code et des données en enlevant des APIs existantes historiquemnt agents dynamiques, setAccessible, Unsafe, JNI Article expliques les risques percus par les mainteneurs de la JVM Franchement c'est un peu leg sur les causes l'article, auto propagande JavaScript Temporal, enfin une API propre et moderne pour gérer les dates en JS https://developer.mozilla.org/en-US/blog/javascript-temporal-is-coming/ JavaScript Temporal est un nouvel objet conçu pour remplacer l'objet Date, qui présente des défauts. Il résout des problèmes tels que le manque de prise en charge des fuseaux horaires et la mutabilité. Temporal introduit des concepts tels que les instants, les heures civiles et les durées. Il fournit des classes pour gérer diverses représentations de date/heure, y compris celles qui tiennent compte du fuseau horaire et celles qui n'en tiennent pas compte. Temporal simplifie l'utilisation de différents calendriers (par exemple, chinois, hébreu). Il comprend des méthodes pour les comparaisons, les conversions et le formatage des dates et des heures. La prise en charge par les navigateurs est expérimentale, Firefox Nightly ayant l'implémentation la plus aboutie. Un polyfill est disponible pour essayer Temporal dans n'importe quel navigateur. Librairies Un article sur les fetch size du JDBC et les impacts sur vos applications https://in.relation.to/2025/01/24/jdbc-fetch-size/ qui connait la valeur fetch size par default de son driver? en fonction de vos use cases, ca peut etre devastateur exemple d'une appli qui retourne 12 lignes et un fetch size de oracle a 10, 2 a/r pour rien et si c'est 50 lignres retournées la base de donnée est le facteur limitant, pas Java donc monter sont fetch size est avantageux, on utilise la memoire de Java pour eviter la latence Quarkus annouce les MCP servers project pour collecter les servier MCP en Java https://quarkus.io/blog/introducing-mcp-servers/ MCP d'Anthropic introspecteur de bases JDBC lecteur de filke system Dessine en Java FX demarrables facilement avec jbang et testes avec claude desktop, goose et mcp-cli permet d'utliser le pouvoir des librarires Java de votre IA d'ailleurs Spring a la version 0.6 de leur support MCP https://spring.io/blog/2025/01/23/spring-ai-mcp-0 Infrastructure Apache Flink sur Kibernetes https://www.decodable.co/blog/get-running-with-apache-flink-on-kubernetes-2 un article tres complet ejn deux parties sur l'installation de Flink sur Kubernetes installation, setup mais aussi le checkpointing, la HA, l'observablité Data et Intelligence Artificielle 10 techniques de prompt engineering https://medium.com/google-cloud/10-prompt-engineering-techniques-every-beginner-should-know-bf6c195916c7 Si vous voulez aller plus loin, l'article référence un très bon livre blanc sur le prompt engineering https://www.kaggle.com/whitepaper-prompt-engineering Les techniques évoquées : Zero-Shot Prompting: On demande directement à l'IA de répondre à une question sans lui fournir d'exemple préalable. C'est comme si on posait une question à une personne sans lui donner de contexte. Few-Shot Prompting: On donne à l'IA un ou plusieurs exemples de la tâche qu'on souhaite qu'elle accomplisse. C'est comme montrer à quelqu'un comment faire quelque chose avant de lui demander de le faire. System Prompting: On définit le contexte général et le but de la tâche pour l'IA. C'est comme donner à l'IA des instructions générales sur ce qu'elle doit faire. Role Prompting: On attribue un rôle spécifique à l'IA (enseignant, journaliste, etc.). C'est comme demander à quelqu'un de jouer un rôle spécifique. Contextual Prompting: On fournit des informations supplémentaires ou un contexte pour la tâche. C'est comme donner à quelqu'un toutes les informations nécessaires pour répondre à une question. Step-Back Prompting: On pose d'abord une question générale, puis on utilise la réponse pour poser une question plus spécifique. C'est comme poser une question ouverte avant de poser une question plus fermée. Chain-of-Thought Prompting: On demande à l'IA de montrer étape par étape comment elle arrive à sa conclusion. C'est comme demander à quelqu'un d'expliquer son raisonnement. Self-Consistency Prompting: On pose plusieurs fois la même question à l'IA et on compare les réponses pour trouver la plus cohérente. C'est comme vérifier une réponse en la posant sous différentes formes. Tree-of-Thoughts Prompting: On permet à l'IA d'explorer plusieurs chemins de raisonnement en même temps. C'est comme considérer toutes les options possibles avant de prendre une décision. ReAct Prompting: On permet à l'IA d'interagir avec des outils externes pour résoudre des problèmes complexes. C'est comme donner à quelqu'un les outils nécessaires pour résoudre un problème. Les patterns GenAI the thoughtworks https://martinfowler.com/articles/gen-ai-patterns/ tres introductif et pre RAG le direct prompt qui est un appel direct au LLM: limitations de connaissance et de controle de l'experience eval: evaluer la sortie d'un LLM avec plusieurs techniques mais fondamentalement une fonction qui prend la demande, la reponse et donc un score numerique evaluation via un LLM (le meme ou un autre), ou evaluation humaine tourner les evaluations a partir de la chaine de build amis aussi en live vu que les LLMs puvent evoluer. Decrit les embedding notament d'image amis aussi de texte avec la notion de contexte DeepSeek et la fin de la domination de NVidia https://youtubetranscriptoptimizer.com/blog/05_the_short_case_for_nvda un article sur les raisons pour lesquelles NVIDIA va se faire cahllengert sur ses marges 90% de marge quand meme parce que les plus gros GPU et CUDA qui est proprio mais des approches ardware alternatives existent qui sont plus efficientes (TPU et gros waffle) Google, MS et d'autres construisent leurs GPU alternatifs CUDA devient de moins en moins le linga franca avec l'investissement sur des langages intermediares alternatifs par Apple, Google OpenAI etc L'article parle de DeepSkeek qui est venu mettre une baffe dans le monde des LLMs Ils ont construit un competiteur a gpt4o et o1 avec 5M de dollars et des capacites de raisonnements impressionnant la cles c'etait beaucoup de trick d'optimisation mais le plus gros est d'avoir des poids de neurores sur 8 bits vs 32 pour les autres. et donc de quatizer au fil de l'eau et au moment de l'entrainement beaucoup de reinforcemnt learning innovatifs aussi et des Mixture of Expert donc ~50x moins chers que OpenAI Donc plus besoin de GPU qui on des tonnes de vRAM ah et DeepSeek est open source un article de semianalytics change un peu le narratif le papier de DeepSkeek en dit long via ses omissions par ensemple les 6M c'est juste l'inference en GPU, pas les couts de recherches et divers trials et erreurs en comparaison Claude Sonnet a coute 10M en infererence DeepSeek a beaucoup de CPU pre ban et ceratins post bans evalués a 5 Milliards en investissement. leurs avancées et leur ouverture reste extremement interessante Une intro à Apache Iceberg http://blog.ippon.fr/2025/01/17/la-revolution-des-donnees-lavenement-des-lakehouses-avec-apache-iceberg/ issue des limites du data lake. non structuré et des Data Warehouses aux limites en diversite de données et de volume entrent les lakehouse Et particulierement Apache Iceberg issue de Netflix gestion de schema mais flexible notion de copy en write vs merge on read en fonction de besoins garantie atomicite, coherence, isoliation et durabilite notion de time travel et rollback partitions cachées (qui abstraient la partition et ses transfos) et evolution de partitions compatbile avec les moteurs de calcul comme spark, trino, flink etc explique la structure des metadonnées et des données Guillaume s'amuse à générer des histoires courtes de Science-Fiction en programmant des Agents IA avec LangChain4j et aussi avec des workflows https://glaforge.dev/posts/2025/01/27/an-ai-agent-to-generate-short-scifi-stories/ https://glaforge.dev/posts/2025/01/31/a-genai-agent-with-a-real-workflow/ Création d'un générateur automatisé de nouvelles de science-fiction à l'aide de Gemini et Imagen en Java, LangChain4j, sur Google Cloud. Le système génère chaque nuit des histoires, complétées par des illustrations créées par le modèle Imagen 3, et les publie sur un site Web. Une étape d'auto-réflexion utilise Gemini pour sélectionner la meilleure image pour chaque chapitre. L'agent utilise un workflow explicite, drivé par le code Java, où les étapes sont prédéfinies dans le code, plutôt que de s'appuyer sur une planification basée sur LLM. Le code est disponible sur GitHub et l'application est déployée sur Google Cloud. L'article oppose les agents de workflow explicites aux agents autonomes, en soulignant les compromis de chaque approche. Car parfois, les Agent IA autonomes qui gèrent leur propre planning hallucinent un peu trop et n'établissent pas un plan correctement, ou ne le suive pas comme il faut, voire hallucine des “function call”. Le projet utilise Cloud Build, le Cloud Run jobs, Cloud Scheduler, Firestore comme base de données, et Firebase pour le déploiement et l'automatisation du frontend. Dans le deuxième article, L'approche est différente, Guillaume utilise un outil de Workflow, plutôt que de diriger le planning avec du code Java. L'approche impérative utilise du code Java explicite pour orchestrer le workflow, offrant ainsi un contrôle et une parallélisation précis. L'approche déclarative utilise un fichier YAML pour définir le workflow, en spécifiant les étapes, les entrées, les sorties et l'ordre d'exécution. Le workflow comprend les étapes permettant de générer une histoire avec Gemini 2, de créer une invite d'image, de générer des images avec Imagen 3 et d'enregistrer le résultat dans Cloud Firestore (base de donnée NoSQL). Les principaux avantages de l'approche impérative sont un contrôle précis, une parallélisation explicite et des outils de programmation familiers. Les principaux avantages de l'approche déclarative sont des définitions de workflow peut-être plus faciles à comprendre (même si c'est un YAML, berk !) la visualisation, l'évolutivité et une maintenance simplifiée (on peut juste changer le YAML dans la console, comme au bon vieux temps du PHP en prod). Les inconvénients de l'approche impérative incluent le besoin de connaissances en programmation, les défis potentiels en matière de maintenance et la gestion des conteneurs. Les inconvénients de l'approche déclarative incluent une création YAML pénible, un contrôle de parallélisation limité, l'absence d'émulateur local et un débogage moins intuitif. Le choix entre les approches dépend des exigences du projet, la déclarative étant adaptée aux workflows plus simples. L'article conclut que la planification déclarative peut aider les agents IA à rester concentrés et prévisibles. Outillage Vulnérabilité des proxy Maven https://github.blog/security/vulnerability-research/attacks-on-maven-proxy-repositories/ Quelque soit le langage, la techno, il est hautement conseillé de mettre en place des gestionnaires de repositories en tant que proxy pour mieux contrôler les dépendances qui contribuent à la création de vos produits Michael Stepankin de l'équipe GitHub Security Lab a cherché a savoir si ces derniers ne sont pas aussi sources de vulnérabilité en étudiant quelques CVEs sur des produits comme JFrog Artifactory, Sonatype Nexus, et Reposilite Certaines failles viennent de la UI des produits qui permettent d'afficher les artifacts (ex: mettez un JS dans un fichier POM) et même de naviguer dedans (ex: voir le contenu d'un jar / zip et on exploite l'API pour lire, voir modifier des fichiers du serveur en dehors des archives) Les artifacts peuvent aussi être compromis en jouant sur les paramètres propriétaires des URLs ou en jouant sur le nomage avec les encodings. Bref, rien n'est simple ni niveau. Tout système rajoute de la compléxité et il est important de les tenir à mettre à jour. Il faut surveiller activement sa chaine de distribution via différents moyens et ne pas tout miser sur le repository manager. L'auteur a fait une présentation sur le sujet : https://www.youtube.com/watch?v=0Z_QXtk0Z54 Apache Maven 4… Bientôt, c'est promis …. qu'est ce qu'il y aura dedans ? https://gnodet.github.io/maven4-presentation/ Et aussi https://github.com/Bukama/MavenStuff/blob/main/Maven4/whatsnewinmaven4.md Apache Maven 4 Doucement mais surement …. c'est le principe d'un projet Maven 4.0.0-rc-2 est dispo (Dec 2024). Maven a plus de 20 ans et est largement utilisé dans l'écosystème Java. La compatibilité ascendante a toujours été une priorité, mais elle a limité la flexibilité. Maven 4 introduit des changements significatifs, notamment un nouveau schéma de construction et des améliorations du code. Changements du POM Séparation du Build-POM et du Consumer-POM : Build-POM : Contient des informations propres à la construction (ex. plugins, configurations). Consumer-POM : Contient uniquement les informations nécessaires aux consommateurs d'artefacts (ex. dépendances). Nouveau Modèle Version 4.1.0 : Utilisé uniquement pour le Build-POM, alors que le Consumer-POM reste en 4.0.0 pour la compatibilité. Introduit de nouveaux éléments et en marque certains comme obsolètes. Modules renommés en sous-projets : “Modules” devient “Sous-projets” pour éviter la confusion avec les Modules Java. L'élément remplace (qui reste pris en charge). Nouveau type de packaging : “bom” (Bill of Materials) : Différencie les POMs parents et les BOMs de gestion des dépendances. Prend en charge les exclusions et les imports basés sur les classifiers. Déclaration explicite du répertoire racine : permet de définir explicitement le répertoire racine du projet. Élimine toute ambiguïté sur la localisation des racines de projet. Nouvelles variables de répertoire : ${project.rootDirectory}, ${session.topDirectory} et ${session.rootDirectory} pour une meilleure gestion des chemins. Remplace les anciennes solutions non officielles et variables internes obsolètes. Prise en charge de syntaxes alternatives pour le POM Introduction de ModelParser SPI permettant des syntaxes alternatives pour le POM. Apache Maven Hocon Extension est un exemple précoce de cette fonctionnalité. Améliorations pour les sous-projets Versioning automatique des parents Il n'est plus nécessaire de définir la version des parents dans chaque sous-projet. Fonctionne avec le modèle de version 4.1.0 et s'étend aux dépendances internes au projet. Support complet des variables compatibles CI Le Flatten Maven Plugin n'est plus requis. Prend en charge les variables comme ${revision} pour le versioning. Peut être défini via maven.config ou la ligne de commande (mvn verify -Drevision=4.0.1). Améliorations et corrections du Reactor Correction de bug : Gestion améliorée de --also-make lors de la reprise des builds. Nouvelle option --resume (-r) pour redémarrer à partir du dernier sous-projet en échec. Les sous-projets déjà construits avec succès sont ignorés lors de la reprise. Constructions sensibles aux sous-dossiers : Possibilité d'exécuter des outils sur des sous-projets sélectionnés uniquement. Recommandation : Utiliser mvn verify plutôt que mvn clean install. Autres Améliorations Timestamps cohérents pour tous les sous-projets dans les archives packagées. Déploiement amélioré : Le déploiement ne se produit que si tous les sous-projets sont construits avec succès. Changements de workflow, cycle de vie et exécution Java 17 requis pour exécuter Maven Java 17 est le JDK minimum requis pour exécuter Maven 4. Les anciennes versions de Java peuvent toujours être ciblées pour la compilation via Maven Toolchains. Java 17 a été préféré à Java 21 en raison d'un support à long terme plus étendu. Mise à jour des plugins et maintenance des applications Suppression des fonctionnalités obsolètes (ex. Plexus Containers, expressions ${pom.}). Mise à jour du Super POM, modifiant les versions par défaut des plugins. Les builds peuvent se comporter différemment ; définissez des versions fixes des plugins pour éviter les changements inattendus. Maven 4 affiche un avertissement si des versions par défaut sont utilisées. Nouveau paramètre “Fail on Severity” Le build peut échouer si des messages de log atteignent un niveau de gravité spécifique (ex. WARN). Utilisable via --fail-on-severity WARN ou -fos WARN. Maven Shell (mvnsh) Chaque exécution de mvn nécessitait auparavant un redémarrage complet de Java/Maven. Maven 4 introduit Maven Shell (mvnsh), qui maintient un processus Maven résident unique ouvert pour plusieurs commandes. Améliore la performance et réduit les temps de build. Alternative : Utilisez Maven Daemon (mvnd), qui gère un pool de processus Maven résidents. Architecture Un article sur les feature flags avec Unleash https://feeds.feedblitz.com//911939960/0/baeldungImplement-Feature-Flags-in-Java-With-Unleash Pour A/B testing et des cycles de développements plus rapides pour « tester en prod » Montre comment tourner sous docker unleash Et ajouter la librairie a du code java pour tester un feature flag Sécurité Keycloak 26.1 https://www.keycloak.org/2025/01/keycloak-2610-released.html detection des noeuds via la proble base de donnée aulieu echange reseau virtual threads pour infinispan et jgroups opentelemetry tracing supporté et plein de fonctionalités de sécurité Loi, société et organisation Les grands morceaux du coût et revenus d'une conférence. Ici http://bdx.io|bdx.io https://bsky.app/profile/ameliebenoit33.bsky.social/post/3lgzslhedzk2a 44% le billet 52% les sponsors 38% loc du lieu 29% traiteur et café 12% standiste 5% frais speaker (donc pas tous) Ask Me Anything Julien de Provin: J'aime beaucoup le mode “continuous testing” de Quarkus, et je me demandais s'il existait une alternative en dehors de Quarkus, ou à défaut, des ressources sur son fonctionnement ? J'aimerais beaucoup avoir un outil agnostique utilisable sur les projets non-Quarkus sur lesquels j'intervient, quitte à y metttre un peu d'huile de coude (ou de phalange pour le coup). https://github.com/infinitest/infinitest/ Conférences La liste des conférences provenant de Developers Conferences Agenda/List par Aurélie Vache et contributeurs : 6-7 février 2025 : Touraine Tech - Tours (France) 21 février 2025 : LyonJS 100 - Lyon (France) 28 février 2025 : Paris TS La Conf - Paris (France) 6 mars 2025 : DevCon #24 : 100% IA - Paris (France) 13 mars 2025 : Oracle CloudWorld Tour Paris - Paris (France) 14 mars 2025 : Rust In Paris 2025 - Paris (France) 19-21 mars 2025 : React Paris - Paris (France) 20 mars 2025 : PGDay Paris - Paris (France) 20-21 mars 2025 : Agile Niort - Niort (France) 25 mars 2025 : ParisTestConf - Paris (France) 26-29 mars 2025 : JChateau Unconference 2025 - Cour-Cheverny (France) 27-28 mars 2025 : SymfonyLive Paris 2025 - Paris (France) 28 mars 2025 : DataDays - Lille (France) 28-29 mars 2025 : Agile Games France 2025 - Lille (France) 3 avril 2025 : DotJS - Paris (France) 3 avril 2025 : SoCraTes Rennes 2025 - Rennes (France) 4 avril 2025 : Flutter Connection 2025 - Paris (France) 4 avril 2025 : aMP Orléans 04-04-2025 - Orléans (France) 10-11 avril 2025 : Android Makers - Montrouge (France) 10-12 avril 2025 : Devoxx Greece - Athens (Greece) 16-18 avril 2025 : Devoxx France - Paris (France) 23-25 avril 2025 : MODERN ENDPOINT MANAGEMENT EMEA SUMMIT 2025 - Paris (France) 24 avril 2025 : IA Data Day 2025 - Strasbourg (France) 29-30 avril 2025 : MixIT - Lyon (France) 7-9 mai 2025 : Devoxx UK - London (UK) 15 mai 2025 : Cloud Toulouse - Toulouse (France) 16 mai 2025 : AFUP Day 2025 Lille - Lille (France) 16 mai 2025 : AFUP Day 2025 Lyon - Lyon (France) 16 mai 2025 : AFUP Day 2025 Poitiers - Poitiers (France) 24 mai 2025 : Polycloud - Montpellier (France) 24 mai 2025 : NG Baguette Conf 2025 - Nantes (France) 5-6 juin 2025 : AlpesCraft - Grenoble (France) 5-6 juin 2025 : Devquest 2025 - Niort (France) 10-11 juin 2025 : Modern Workplace Conference Paris 2025 - Paris (France) 11-13 juin 2025 : Devoxx Poland - Krakow (Poland) 12-13 juin 2025 : Agile Tour Toulouse - Toulouse (France) 12-13 juin 2025 : DevLille - Lille (France) 13 juin 2025 : Tech F'Est 2025 - Nancy (France) 17 juin 2025 : Mobilis In Mobile - Nantes (France) 24 juin 2025 : WAX 2025 - Aix-en-Provence (France) 25-26 juin 2025 : Agi'Lille 2025 - Lille (France) 25-27 juin 2025 : BreizhCamp 2025 - Rennes (France) 26-27 juin 2025 : Sunny Tech - Montpellier (France) 1-4 juillet 2025 : Open edX Conference - 2025 - Palaiseau (France) 7-9 juillet 2025 : Riviera DEV 2025 - Sophia Antipolis (France) 18-19 septembre 2025 : API Platform Conference - Lille (France) & Online 2-3 octobre 2025 : Volcamp - Clermont-Ferrand (France) 6-10 octobre 2025 : Devoxx Belgium - Antwerp (Belgium) 9-10 octobre 2025 : Forum PHP 2025 - Marne-la-Vallée (France) 16-17 octobre 2025 : DevFest Nantes - Nantes (France) 4-7 novembre 2025 : NewCrafts 2025 - Paris (France) 6 novembre 2025 : dotAI 2025 - Paris (France) 7 novembre 2025 : BDX I/O - Bordeaux (France) 12-14 novembre 2025 : Devoxx Morocco - Marrakech (Morocco) 28-31 janvier 2026 : SnowCamp 2026 - Grenoble (France) 23-25 avril 2026 : Devoxx Greece - Athens (Greece) 17 juin 2026 : Devoxx Poland - Krakow (Poland) Nous contacter Pour réagir à cet épisode, venez discuter sur le groupe Google https://groups.google.com/group/lescastcodeurs Contactez-nous via X/twitter https://twitter.com/lescastcodeurs ou Bluesky https://bsky.app/profile/lescastcodeurs.com Faire un crowdcast ou une crowdquestion Soutenez Les Cast Codeurs sur Patreon https://www.patreon.com/LesCastCodeurs Tous les épisodes et toutes les infos sur https://lescastcodeurs.com/

Tom se rozhodl, že do světa recruitmentu a HR managementu přinese umělou inteligenci. Založil Talentpilot, začal spolupracovat s OpenAI, FF UK i Akademií věd ČR a vytvořil vědou a daty poháněný model. Klienti díky němu mohou stavět lepší, kompatibilnější, stabilnější a spokojenější týmy

Fredrik is again joined by Malin Sundberg and Kai Dombrowski for a review of attending this year’s WWDC, working with “AI”, and more. The experience of attending - a lot about the great community. News from the conference - a Snow leopard year, in a good way. Lots of nice fixes and additions - Swiftui, fun widgets, and of course lots of question marks around whatever Apple intelligence will grow up to be. And of course a little side of the ongoing story of Apple versus the EU. Apple intelligence also leads naturally into a discussion on how everyone works with language models, copilots, and so on. There is also some discussion of summer development plans, localization, and the snobbiest coffee country in the world. Thank you Cloudnet for sponsoring our VPS! Comments, questions or tips? We a re @kodsnack, @tobiashieta, @oferlund and @bjoreman on Twitter, have a page on Facebook and can be emailed at info@kodsnack.se if you want to write longer. We read everything we receive. If you enjoy Kodsnack we would love a review in iTunes! You can also support the podcast by buying us a coffee (or two!) through Ko-fi. Links Support us on Ko-fi! Malin Kai Previous episodes with Malin and Kai Uppleva Izotope RX Deep dish Swift Slices - the Deep dish Swift podcast Auphonic Adobe’s podcast enhance WWDC The WWDC keynote and other videos Infinite loop - used to be Apple’s main campus Apple park - Apple’s current main campus Apple design awards iOS dev happy hour One more thing Altconf The talk show live James Dempsey and the breakpoints James Dempsey on Slices Snow leopard Swift charts UIKit Live activities Apple versus EU:s digital markets act Meta’s Ray-ban glasses Fika Gemini Apple Mail Apple intelligence Intents Intents domains Apple private cloud compute Dynamic island Claude 3.5 sonnet Jack Cheng, author and developer of Bebop Apple localizations website Bankid Swish Kanban Firestore Pixelmator Quick notes Orbit Mimestream Swift island on Texel, the Netherlands Core coffee Titles Talking about IKEA furniture The biggest watch party in the world Essentially run by the community The community aspect The best Apple stories Open-ended on purpose A Snow leopard year Pop to the root view (Further) Into the view hierarchy Forgotten behavior Crisis averted Spiteful of the EU Grab a coffee together More spiteful than necessary Embrace fika culture Often not where people live All the timelines Lots of different laters Playful but also elegant I know what I want to convey Add small things to your home screen I said no bears I can not generate app icons that do not contain bears Plain Mail again The snobbiest coffee country in the world

2023-09-19 Weekly News — Episode 204Watch the video version on YouTube at https://youtube.com/live/QR78EAolYQo?feature=share Hosts:  Gavin Pickin - Senior Developer at Ortus Solutions Dan Card- Senior Developer at Ortus Solutions Thanks to our Sponsor - Ortus SolutionsThe makers of ColdBox, CommandBox, ForgeBox, TestBox and all your favorite box-es out there. A few ways  to say thanks back to Ortus Solutions: Like and subscribe to our videos on YouTube.  Help ORTUS reach for the Stars - Star and Fork our ReposStar all of your Github Box Dependencies from CommandBox with https://www.forgebox.io/view/commandbox-github  Subscribe to our Podcast on your Podcast Apps and leave us a review AND WE WILL READ IT ON THE SHOW Sign up for a free or paid account on CFCasts, which is releasing new content every week BOXLife store: https://www.ortussolutions.com/about-us/shop Buy Ortus's Books 102 ColdBox HMVC Quick Tips and Tricks on GumRoad (http://gum.co/coldbox-tips) Learn Modern ColdFusion (CFML) in 100+ Minutes - Free online https://modern-cfml.ortusbooks.com/ or buy an EBook or Paper copy https://www.ortussolutions.com/learn/books/coldfusion-in-100-minutes   Patreon SupportWe have 38 patreons: https://www.patreon.com/ortussolutions. News and AnnouncementsSept 13th - Happy Programmers DayHacktoberfest is comingCELEBRATE OUR 10TH YEAR SUPPORTING OPEN SOURCE!This year marks the 10th anniversary of Hacktoberfest, and we're calling on your support! Whether it's your first time participating—or your tenth—it's almost time to hack out four pristine pull/merge requests as we continue our month of support for open source.Hacktoberfest has grown from 676 participants in 2014 to nearly 147,000 participants last year. To help ensure Hacktoberfest can be sustained for another decade, this year we're moving away from a free t-shirt reward to a digital reward.PREPTEMBERSeptember is the perfect time to prepare for Hacktoberfest. Get a jump start by finding projects to contribute to, adding the ‘hacktoberfest' tag to your projects, or familiarizing yourself with Git.Discord: https://discord.gg/hacktoberfest https://hacktoberfest.com/ CFMLers get AWS CertifiedDaniel Garcia from Ortus, and a few other CFML Community members created a study group to complete the AWS Cloud Practitioner Certification, the first on many AWS tracks.All of the group members who took the Certification exam passed, which is great for these developers, their employers, and the community.If you are considering a certification, create a study group with friends or community members, it helps with learning, accountability and it's great to socialize with like minded people.https://d1.awsstatic.com/training-and-certification/docs/AWS_certification_paths.pdfhttps://aws.amazon.com/certification/?nc2=sb_ce_co New Releases and UpdatesLucee 5.4.3.7-Snapshot ready for TestingHey everyone, we have a new 5.4.3.7-SNAPSHOT out which addresses all the known regressions with 5.4.3LDEV-4675 Admin: requested action doesn't exist 1LDEV-3854 a fix for the pagePool locking problem 7LDEV-4480 “.” should not be accepted/converted as/to a number 2LDEV-4676 SerializeJSON() produces invalid JSON when serializing some CFC instances 5Builds are up, including docker images, It would be great if people can test this out and let us knowhttps://dev.lucee.org/t/5-4-3-7-snapshot-ready-for-testing/13001 Webinar / Meetups and WorkshopsOOP & ColdFusionNolan ErckFriday, September 29, 2023 @ 12 PM HAST (Hawaii Standard Time)Object-Oriented Programming is a common term in programming languages. It's a vast concept but to sum it up in a single line, it is a set of concepts and techniques that make use of the “object” construct, to write more reusable, maintainable, and organized code. Objects are implemented differently in every language. In ColdFusion, we have ColdFusion Components (CFCs) that can be instantiated to create objects.Anyone who has ever studied OOP must know that there are four main concepts, which are: Abstraction Encapsulation Inheritance Polymorphism https://www.meetup.com/hawaii-coldfusion-meetup-group/events/294629892/ICYMI - Hawaii CF User Group Meetup - Mark Takata on Graph QL & ColdFusionGraphQL is a query language for APIs and a runtime for fulfilling those queries with your existing data. GraphQL provides a complete and understandable description of the data in your API, gives clients the power to ask for exactly what they need and nothing more, makes it easier to evolve APIs over time, and enables powerful developer tools.https://hawaiicoldfusionusergroup.adobeconnect.com/p6cwiyco0hx7/ ICYMI - Sac Interactive - Mark Takata - ColdFusion 2023 Modern CFML Development EcosystemJoin Mark Takata, Global Technical Evangelist for Adobe ColdFusion as he delves into all of the new incredible feature additions for ColdFusion 2023. We will discuss GraphQL, a variety of GCP native features (including storage, FireStore and Pub/Sub), JWT and security additions for single sign-on for the ColdFusion administrator. Both high level overview and code samples will be highlighted, and all code will be available on GitHub for download after the talk.https://www.youtube.com/watch?v=rdRtN2YEUnE CFCasts Content Updateshttps://www.cfcasts.comRecent Releases Into the Box 2023 Videos is available for purchase as an EXCLUSIVE PREMIUM package. https://cfcasts.com/series/itb-2023  Subscribers will get access to premium packages after a 6 month exclusive window. Into the Box Attendees should have their coupon code in the email already!!!! 2023 ForgeBox Module of the Week Series - 1 new Video https://cfcasts.com/series/2023-forgebox-modules-of-the-week  2023 VS Code Hint tip and Trick of the Week Series - 1 new Video https://cfcasts.com/series/2023-vs-code-hint-tip-and-trick-of-the-week  Coming Soon More ForgeBox and VS Code Podcast snippet videos Mastering CBWIRE v3 from Grant ColdBox Elixir from Eric Conferences and TrainingAdobe CF Summit WestLas Vegas 2-4th of October.Session passes @ $199 Professional passes @ $299. Speakers have been announced - with some great sessionshttps://cfsummit.adobeevents.com/ Andy Bucklee will be there (David Wallace from The Office)Ortus CF Summit Training - ColdBox 7 Zero to Hero - SOLD OUTDate: October 4th - 5th, 2023 | Right after Adobe CFSummit, 2023Speakers: Luis Majano & Gavin PickinLocation: Las Vegas, NevadaVenue: Regus - Las Vegas - 3960 Howard Hughes Parkway Paradise #Suite 500 Las Vegas, NV 89169 United StatesSpotlight Less than 2 miles from the Mirage - 30 mins walk Next to Marriot hotel - 2 min walk 1 mile to Top Golf - 20 min walk 5 min walk to Fogo de Chão Brazilian Steakhouse 5 min walk to starbucks 5 min walk to Lo-los chicken and waffles WIN WIN WIN WINhttps://www.eventbrite.com/e/workshop-coldbox-from-zero-to-hero-tickets-659169262007?aff=oddtdtcreator Into the Box LATAMNovember 30thUniversity of Business in El Salvador.https://latam.intothebox.org/ITB 2024Location: Optica in Washington, DCAnnouncement Blog Post: https://www.ortussolutions.com/blog/our-into-the-box-2024-venue-and-dates-are-setDates: May 15-17, 2024Get Blind Tickets Now: https://www.eventbrite.com/e/into-the-box-2024-the-new-era-of-modernization-tickets-663126347757https://www.ortussolutions.com/blog/call-for-speakers-into-the-box-2024-share-your-expertiseMore conferencesNeed more conferences, this site has a huge list of conferences for almost any language/community.https://confs.tech/Blogs, Tweets, and Videos of the Week9/19/2023 - Blog - Ben Nadel - Which Whitespace Characters Does trim() Remove In ColdFusionYesterday, an external API call that I was making failed because one of the values that I was posting contained a trailing "Zero width space" character (u200b). The value in question was being passed-through ColdFusion's native trim() function; which was clearly not removing this whitespace character. As such, it occurred to me that I didn't really know which characters are (and are not) handled by the trim() function. And so, I wanted to run a test.https://www.bennadel.com/blog/4516-which-whitespace-characters-does-trim-remove-in-coldfusion.htm 9/13/2023 - Blog - Ben Nadel - Using FileReadLine() With Seekable Files In ColdFusion Last week, I started to explore seekable files in ColdFusion. A seekable file allows us to jump to an arbitrary offset within the file contents (which I believe can be done without having to read the entire file into memory). I've recently been dealing with consuming large text-files at work; and, I'm wondering if a seekable file might be something I can use to create a "resumable" consumption process. As such, I wanted to play around with using the fileReadLine() function in conjunction with seekable files in ColdFusion.https://www.bennadel.com/blog/4515-using-filereadline-with-seekable-files-in-coldfusion.htm 9/11/2023 - Tweet - Ben Nadel - Weird Application Datasource ErrorHas anyone had any luck getting per-application datasources (ie, `this.datasources`) to work in #ColdFusion 2023? My code works fine in ACF 2021; but, when I build the same Docker image using 2023, the code breaks.https://x.com/BenNadel/status/1701181955578986946?s=20 CFML JobsSeveral positions available on https://www.getcfmljobs.com/Listing over 98 ColdFusion positions from 65 companies across 43 locations in 5 Countries.3 new jobs listed in the last two weeksFull-Time - Fully Insured End of Lease Cleaners in Melbourne at Melbourn.. - Australia Posted Sep 18 for Bond Cleaning in MelbourneAs your trusted partner for end of lease cleaning, Bond Cleaning in Melbourne is dedicated to exceeding your expectations. With years of experience, we understand the critical details that ensure a successful clean. Our team works diligently to restore your rental property to its original glory, ensuring the swift return of your security deposit. Property owners and real estate agents have come to rely on our expertise, backed by the REIV-approved checklist. We offer flexible packages at affordable rates, tailored to your convenience. Don't leave your deposit to chance - contact us at 03 9068 8186 or reach out through our website. https://www.getcfmljobs.com/viewjob.cfm?jobid=11605 Full-Time - ColdFusion Developer 2 (Remote) at Remote - United States Posted: Sep 18 for Community BrandsThe Developer position is responsible for writing application code to contribute to the full lifecycle of development from concept to post-production support and maintenance of server / OS / desktop / web / mobile applications and services. This position will develop application code, contribute to version-controlled source code repositories and will managed assigned tasks to create measurable value and deliver software to market using industry recognized agile methodologies and best practices. The Developer will be responsible for coding according to prescribed standards and guidelines set forth by the architects and leadership teams and must demonstrate quality, brevity and timeliness in all deliverables.https://www.getcfmljobs.com/jobs/index.cfm/united-states/coldfusion-developer-2-remote-at-community-brands/11604 Full-Time - ColdFusion Developer at Washington, DC - United States Sep 08 for TamminaUS Citizen. Must be clearable. A clearance or an inactive clearance preferred. Government agency experience required.We are seeking an Application Developer to join our team. The developer shall perform and/or support requirements definition, design and prototyping, implementation, unit testing, debugging, verification, deployment, and maintenance activities throughout the software development life cycle (SDLC) for current and future software modules of a comprehensive web portal environment.https://www.getcfmljobs.com/jobs/index.cfm/united-states/ColdFusionDev-at-Washington-DC/11603 Other Job LinksThere is a jobs channel in the CFML slack team, and in the Box team slack now tooForgeBox Module of the WeekOrtus ORM Extension for LuceeThe Ortus ORM Extension is a native Lucee Extension that allows your CFML application to integrate with the powerful Hibernate ORM. With Hibernate, you can interact with your database records in an object oriented fashion, using components to denote each record and simple getters and setters for each field Add Object Relational Mapping to any CFML app with Hibernate ORM Use native CFML methods to update and persist entities to the database (entityNew(), entitySave(), ormFlush(), etc.) Supports 80+ database dialects, from SQLServer2005 to MySQL8 and PostgreSQL 60% faster startup than the Lucee Hibernate extension Generate your mapping XML once and never again with the autoGenMap=false ORM configuration setting React to entity changes with pre and post event listeners such as onPreInsert(), onPreUpdate() and onPreDelete() Over 20 native CFML functions: $ install D062D72F-F8A2-46F0-8CBC91325B2F067B https://orm-extension.ortusbooks.com/ https://www.forgebox.io/view/D062D72F-F8A2-46F0-8CBC91325B2F067BVS Code Hint Tips and Tricks of the WeekCSS PeekAllow peeking to css ID and class strings as definitions from html files to respective CSS. Allows peek and goto definition.This extension extends HTML and ejs code editing with Go To Definition and Go To Symbol in Workspace support for css/scss/less (classes and IDs) found in strings within the source code.This was heavily inspired by a similar feature in Brackets called CSS Inline Editors.https://marketplace.visualstudio.com/items?itemName=pranaygp.vscode-css-peek Thank you to all of our Patreon SupportersThese individuals are personally supporting our open source initiatives to ensure the great toolings like CommandBox, ForgeBox, ColdBox,  ContentBox, TestBox and all the other boxes keep getting the continuous development they need, and funds the cloud infrastructure at our community relies on like ForgeBox for our Package Management with CommandBox. You can support us on Patreon here https://www.patreon.com/ortussolutionsDon't forget, we have Annual Memberships, pay for the year and save 10% - great for businesses everyone. Bronze Packages and up, now get a ForgeBox Pro and CFCasts subscriptions as a perk for their Patreon Subscription. All Patreon supporters have a Profile badge on the Community Website All Patreon supporters have their own Private Forum access on the Community Website All Patreon supporters have their own Private Channel access BoxTeam Slack https://community.ortussolutions.com/Top Patreons (mind-boggling) John Wilson - Synaptrix Tomorrows Guides Jordan Clark Gary Knight Giancarlo Gomez  David Belanger  Dan Card Jeffry McGee - Sunstar Media Dean Maunder Kevin Wright Doug Cain  Nolan Erck  Abdul Raheen And many more PatreonsYou can see an up to date list of all sponsors on Ortus Solutions' Websitehttps://ortussolutions.com/about-us/sponsors Thanks everyone!!! ★ Support this podcast on Patreon ★

Summary The promise of streaming data is that it allows you to react to new information as it happens, rather than introducing latency by batching records together. The peril is that building a robust and scalable streaming architecture is always more complicated and error-prone than you think it's going to be. After experiencing this unfortunate reality for themselves, Abhishek Chauhan and Ashish Kumar founded Grainite so that you don't have to suffer the same pain. In this episode they explain why streaming architectures are so challenging, how they have designed Grainite to be robust and scalable, and how you can start using it today to build your streaming data applications without all of the operational headache. Announcements Hello and welcome to the Data Engineering Podcast, the show about modern data management Businesses that adapt well to change grow 3 times faster than the industry average. As your business adapts, so should your data. RudderStack Transformations lets you customize your event data in real-time with your own JavaScript or Python code. Join The RudderStack Transformation Challenge today for a chance to win a $1,000 cash prize just by submitting a Transformation to the open-source RudderStack Transformation library. Visit dataengineeringpodcast.com/rudderstack (https://www.dataengineeringpodcast.com/rudderstack) today to learn more Hey there podcast listener, are you tired of dealing with the headache that is the 'Modern Data Stack'? We feel your pain. It's supposed to make building smarter, faster, and more flexible data infrastructures a breeze. It ends up being anything but that. Setting it up, integrating it, maintaining it—it's all kind of a nightmare. And let's not even get started on all the extra tools you have to buy to get it to do its thing. But don't worry, there is a better way. TimeXtender takes a holistic approach to data integration that focuses on agility rather than fragmentation. By bringing all the layers of the data stack together, TimeXtender helps you build data solutions up to 10 times faster and saves you 70-80% on costs. If you're fed up with the 'Modern Data Stack', give TimeXtender a try. Head over to dataengineeringpodcast.com/timextender (https://www.dataengineeringpodcast.com/timextender) where you can do two things: watch us build a data estate in 15 minutes and start for free today. Join in with the event for the global data community, Data Council Austin. From March 28-30th 2023, they'll play host to hundreds of attendees, 100 top speakers, and dozens of startups that are advancing data science, engineering and AI. Data Council attendees are amazing founders, data scientists, lead engineers, CTOs, heads of data, investors and community organizers who are all working together to build the future of data. As a listener to the Data Engineering Podcast you can get a special discount of 20% off your ticket by using the promo code dataengpod20. Don't miss out on their only event this year! Visit: dataengineeringpodcast.com/data-council (https://www.dataengineeringpodcast.com/data-council) today Your host is Tobias Macey and today I'm interviewing Ashish Kumar and Abhishek Chauhan about Grainite, a platform designed to give you a single place to build streaming data applications Interview Introduction How did you get involved in the area of data management? Can you describe what Grainite is and the story behind it? What are the personas that you are focused on addressing with Grainite? What are some of the most complex aspects of building streaming data applications in the absence of something like Grainite? How does Grainite work to reduce that complexity? What are some of the commonalities that you see in the teams/organizations that find their way to Grainite? What are some of the higher-order projects that teams are able to build when they are using Grainite as a starting point vs. where they would be spending effort on a fully managed streaming architecture? Can you describe how Grainite is architected? How have the design and goals of the platform changed/evolved since you first started working on it? What does your internal build vs. buy process look like for identifying where to spend your engineering resources? What is the process for getting Grainite set up and integrated into an organizations technical environment? What is your process for determining which elements of the platform to expose as end-user features and customization options vs. keeping internal to the operational aspects of the product? Once Grainite is running, can you describe the day 0 workflow of building an application or data flow? What are the day 2 - N capabilities that Grainite offers for ongoing maintenance/operation/evolution of those applications? What are the most interesting, innovative, or unexpected ways that you have seen Grainite used? What are the most interesting, unexpected, or challenging lessons that you have learned while working on Grainite? When is Grainite the wrong choice? What do you have planned for the future of Grainite? Contact Info Ashish LinkedIn (https://www.linkedin.com/in/ashishkumarprofile/) Abhishek LinkedIn (https://www.linkedin.com/in/abhishekchauhan/) Parting Question From your perspective, what is the biggest gap in the tooling or technology for data management today? Closing Announcements Thank you for listening! Don't forget to check out our other shows. Podcast.__init__ (https://www.pythonpodcast.com) covers the Python language, its community, and the innovative ways it is being used. The Machine Learning Podcast (https://www.themachinelearningpodcast.com) helps you go from idea to production with machine learning. Visit the site (https://www.dataengineeringpodcast.com) to subscribe to the show, sign up for the mailing list, and read the show notes. If you've learned something or tried out a project from the show then tell us about it! Email hosts@dataengineeringpodcast.com (mailto:hosts@dataengineeringpodcast.com)) with your story. To help other people find the show please leave a review on Apple Podcasts (https://podcasts.apple.com/us/podcast/data-engineering-podcast/id1193040557) and tell your friends and co-workers Links Grainite (https://www.grainite.com/) Blog about the challenges of streaming architectures (https://www.grainite.com/blog/there-was-an-old-lady-who-swallowed-a-fly) Getting Started Docs (https://gitbook.grainite.com/developers/getting-started) BigTable (https://research.google/pubs/pub27898/) Spanner (https://research.google/pubs/pub39966/) Firestore (https://cloud.google.com/firestore) OpenCensus (https://opencensus.io/) Citrix (https://www.citrix.com/) NetScaler (https://www.citrix.com/blogs/2022/10/03/netscaler-is-back/) J2EE (https://www.oracle.com/java/technologies/appmodel.html) RocksDB (https://rocksdb.org/) Pulsar (https://pulsar.apache.org/) SQL Server (https://en.wikipedia.org/wiki/Microsoft_SQL_Server) MySQL (https://www.mysql.com/) RAFT Protocol (https://raft.github.io/) The intro and outro music is from The Hug (http://freemusicarchive.org/music/The_Freak_Fandango_Orchestra/Love_death_and_a_drunken_monkey/04_-_The_Hug) by The Freak Fandango Orchestra (http://freemusicarchive.org/music/The_Freak_Fandango_Orchestra/) / CC BY-SA (http://creativecommons.org/licenses/by-sa/3.0/)

Firestoreの課金額50%削減した話 ChatGPTについて

About AndiAndi Gutmans is the General Manager and Vice President for Databases at Google. Andi's focus is on building, managing and scaling the most innovative database services to deliver the industry's leading data platform for businesses. Before joining Google, Andi was VP Analytics at AWS running services such as Amazon Redshift. Before his tenure at AWS, Andi served as CEO and co-founder of Zend Technologies, the commercial backer of open-source PHP.Andi has over 20 years of experience as an open source contributor and leader. He co-authored open source PHP. He is an emeritus member of the Apache Software Foundation and served on the Eclipse Foundation's board of directors. He holds a bachelor's degree in Computer Science from the Technion, Israel Institute of Technology.Links Referenced: LinkedIn: https://www.linkedin.com/in/andigutmans/ Twitter: https://twitter.com/andigutmans TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is sponsored in part by our friends at Sysdig. Sysdig secures your cloud from source to run. They believe, as do I, that DevOps and security are inextricably linked. If you wanna learn more about how they view this, check out their blog, it's definitely worth the read. To learn more about how they are absolutely getting it right from where I sit, visit Sysdig.com and tell them that I sent you. That's S Y S D I G.com. And my thanks to them for their continued support of this ridiculous nonsense.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. This promoted episode is brought to us by our friends at Google Cloud, and in so doing, they have gotten a guest to appear on this show that I have been low-key trying to get here for a number of years. Andi Gutmans is VP and GM of Databases at Google Cloud. Andi, thank you for joining me.Andi: Corey, thanks so much for having me.Corey: I have to begin with the obvious. Given that one of my personal passion projects is misusing every cloud service I possibly can as a database, where do you start and where do you stop as far as saying, “Yes, that's a database,” so it rolls up to me and, “No, that's not a database, so someone else can deal with the nonsense?”Andi: I'm in charge of the operational databases, so that includes both the managed third-party databases such as MySQL, Postgres, SQL Server, and then also the cloud-first databases, such as Spanner, Big Table, Firestore, and AlloyDB. So, I suggest that's where you start because those are all awesome services. And then what doesn't fall underneath, kind of, that purview are things like BigQuery, which is an analytics, you know, data warehouse, and other analytics engines. And of course, there's always folks who bring in their favorite, maybe, lesser-known or less popular database and self-manage it on GCE, on Compute.Corey: Before you wound up at Google Cloud, you spent roughly four years at AWS as VP of Analytics, which is, again, one of those very hazy type of things. Where does it start? Where does it stop? It's not at all clear from the outside. But even before that, you were, I guess, something of a legendary figure, which I know is always a weird thing for people to hear.But you were partially at least responsible for the Zend Framework in the PHP world, which I didn't realize what the heck that was, despite supporting it in production at a couple of jobs, until after I, for better or worse, was no longer trusted to support production environments anymore. Which, honestly, if you can get out, I'm a big proponent of doing that. You sleep so much better without a pager. How did you go from programming languages all the way on over to databases? It just seems like a very odd mix.Andi: Yeah. No, that's a great question. So, I was one of the core developers of PHP, and you know, I had been in the PHP community for quite some time. I also helped ideate. The Zend Framework, which was the company that, you know, I co-founded Zend Technologies was kind of the company behind PHP.So, like Red Hat supports Linux commercially, we supported PHP. And I was very much focused on developers, programming languages, frameworks, IDEs, and that was, you know, really exciting. I had also done quite a bit of work on interoperability with databases, right, because behind every application, there's a database, and so a lot of what we focused on is a great connectivity to MySQL, to Postgres, to other databases, and I got to kind of learn the database world from the outside from the application builders. We sold our company in I think it was 2015 and so I had to kind of figure out what's next. And so, one option would have been, hey, stay in programming languages, but what I learned over the many years that I worked with application developers is that there's a huge amount of value in data.And frankly, I'm a very curious person; I always like to learn, so there was this opportunity to join Amazon, to join the non-relational database side, and take myself completely out of my comfort zone. And actually, I joined AWS to help build the graph database Amazon Neptune, which was even more out of my comfort zone than even probably a relational database. So, I kind of like to do different things and so I joined and I had to learn, you know how to build a database pretty much from the ground up. I mean, of course, I didn't do the coding, but I had to learn enough to be dangerous, and so I worked on a bunch of non-relational databases there such as, you know, Neptune, Redis, Elasticsearch, DynamoDB Accelerator. And then there was the opportunity for me to actually move over from non-relational databases to analytics, which was another way to get myself out of my comfort zone.And so, I moved to run the analytic space, which included services like Redshift, like EMR, Athena, you name it. So, that was just a great experience for me where I got to work with a lot of awesome people and learn a lot. And then the opportunity arose to join Google and actually run the Google transactional databases including their older relational databases. And by the way, my job actually have two jobs. One job is running Spanner and Big Table for Google itself—meaning, you know, search ads and YouTube and everything runs on these databases—and then the second job is actually running external-facing databases for external customers.Corey: How alike are those two? Is it effectively the exact same thing, just with different API endpoints? Are they two completely separate universes? It's always unclear from the outside when looking at large companies that effectively eat versions of their own dog food, where their internal usage of these things starts and stops.Andi: So, great question. So, Cloud Spanner and Cloud Big Table do actually use the internal Spanner and Big Table. So, at the core, it's exactly the same engine, the same runtime, same storage, and everything. However, you know, kind of, internally, the way we built the database APIs was kind of good for scrappy, you know, Google engineers, and you know, folks are kind of are okay, learning how to fit into the Google ecosystem, but when we needed to make this work for enterprise customers, we needed a cleaner APIs, we needed authentication that was an external, right, and so on, so forth. So, think about we had to add an additional set of APIs on top of it, and management, right, to really make these engines accessible to the external world.So, it's running the same engine under the hood, but it is a different set of APIs, and a big part of our focus is continuing to expose to enterprise customers all the goodness that we have on the internal system. So, it's really about taking these very, very unique differentiated databases and democratizing access to them to anyone who wants to.Corey: I'm curious to get your position on the idea that seems to be playing it's—I guess, a battle that's been playing itself out in a number of different customer conversations. And that is, I guess, the theoretical decision between, do we go towards general-purpose databases and more or less treat every problem as a nail in search of a hammer or do you decide that every workload gets its own custom database that aligns the best with that particular workload? There are trade-offs in either direction, but I'm curious where you land on that given that you tend to see a lot more of it than I do.Andi: No, that's a great question. And you know, just for the viewers who maybe aren't aware, there's kind of two extreme points of view, right? There's one point of view that says, purpose-built for everything, like, every specific pattern, like, build bespoke databases, it's kind of a best-of-breed approach. The problem with that approach is it becomes extremely complex for customers, right? Extremely complex to decide what to use, they might need to use multiple for the same application, and so that can be a bit daunting as a customer. And frankly, there's kind of a law of diminishing returns at some point.Corey: Absolutely. I don't know what the DBA role of the future is, but I don't think anyone really wants it to be, “Oh, yeah. We're deciding which one of these three dozen manage database services is the exact right fit for each and every individual workload.” I mean, at some point it feels like certain cloud providers believe that not only every workload should have its own database, but almost every workload should have its own database service. It's at some point, you're allowed to say no and stop building these completely, what feel like to me, Byzantine, esoteric database engines that don't seem to have broad applicability to a whole lot of problems.Andi: Exactly, exactly. And maybe the other extreme is what folks often talk about as multi-model where you say, like, “Hey, I'm going to have a single storage engine and then map onto that the relational model, the document model, the graph model, and so on.” I think what we tend to see is if you go too generic, you also start having performance issues, you may not be getting the right level of abilities and trade-offs around consistency, and replication, and so on. So, I would say Google, like, we're taking a very pragmatic approach where we're saying, “You know what? We're not going to solve all of customer problems with a single database, but we're also not going to have two dozen.” Right?So, we're basically saying, “Hey, let's understand that the main characteristics of the workloads that our customers need to address, build the best services around those.” You know, obviously, over time, we continue to enhance what we have to fit additional models. And then frankly, we have a really awesome partner ecosystem on Google Cloud where if someone really wants a very specialized database, you know, we also have great partners that they can use on Google Cloud and get great support and, you know, get the rest of the benefits of the platform.Corey: I'm very curious to get your take on a pattern that I've seen alluded to by basically every vendor out there except the couple of very obvious ones for whom it does not serve their particular vested interests, which is that there's a recurring narrative that customers are demanding open-source databases for their workloads. And when you hear that, at least, people who came up the way that I did, spending entirely too much time on Freenode, back when that was not a deeply problematic statement in and of itself, where, yes, we're open-source, I guess, zealots is probably the best terminology, and yeah, businesses are demanding to participate in the open-source ecosystem. Here in reality, what I see is not ideological purity or anything like that and much more to do with, “Yeah, we don't like having a single commercial vendor for our databases that basically plays the insert quarter to continue dance whenever we're trying to wind up doing something new. We want the ability to not have licensing constraints around when, where, how, and how quickly we can run databases.” That's what I hear when customers are actually talking about open-source versus proprietary databases. Is that what you see or do you think that plays out differently? Because let's be clear, you do have a number of database services that you offer that are not open-source, but are also absolutely not tied to weird licensing restrictions either?Andi: That's a great question, and I think for years now, customers have been in a difficult spot because the legacy proprietary database vendors, you know, knew how sticky the database is, and so as a result, you know, the prices often went up and was not easy for customers to kind of manage costs and agility and so on. But I would say that's always been somewhat of a concern. I think what I'm seeing changing and happening differently now is as customers are moving into the cloud and they want to run hybrid cloud, they want to run multi-cloud, they need to prove to their regulator that it can do a stressed exit, right, open-source is not just about reducing cost, it's really about flexibility and kind of being in control of when and where you can run the workloads. So, I think what we're really seeing now is a significant surge of customers who are trying to get off legacy proprietary database and really kind of move to open APIs, right, because they need that freedom. And that freedom is far more important to them than even the cost element.And what's really interesting is, you know, a lot of these are the decision-makers in these enterprises, not just the technical folks. Like, to your point, it's not just open-source advocates, right? It's really the business people who understand they need the flexibility. And by the way, even the regulators are asking them to show that they can flexibly move their workloads as they need to. So, we're seeing a huge interest there and, as you said, like, some of our services, you know, are open-source-based services, some of them are not.Like, take Spanner, as an example, it is heavily tied to how we build our infrastructure and how we build our systems. Like, I would say, it's almost impossible to open-source Spanner, but what we've done is we've basically embraced open APIs and made sure if a customer uses these systems, we're giving them control of when and where they want to run their workloads. So, for example, Big Table has an HBase API; Spanner now has a Postgres interface. So, our goal is really to give customers as much flexibility and also not lock them into Google Cloud. Like, we want them to be able to move out of Google Cloud so they have control of their destiny.Corey: I'm curious to know what you see happening in the real world because I can sit here and come up with a bunch of very well-thought-out logical reasons to go towards or away from certain patterns, but I spent years building things myself. I know how it works, you grab the closest thing handy and throw it in and we all know that there is nothing so permanent as a temporary fix. Like, that thing is load-bearing and you'll retire with that thing still in place. In the idealized world, I don't think that I would want to take a dependency on something like—easy example—Spanner or AlloyDB because despite the fact that they have Postgres-squeal—yes, that's how I pronounce it—compatibility, the capabilities of what they're able to do under the hood far exceed and outstrip whatever you're going to be able to build yourself or get anywhere else. So, there's a dataflow architectural dependency lock-in, despite the fact that it is at least on its face, Postgres compatible. Counterpoint, does that actually matter to customers in what you are seeing?Andi: I think it's a great question. I'll give you a couple of data points. I mean, first of all, even if you take a complete open-source product, right, running them in different clouds, different on-premises environments, and so on, fundamentally, you will have some differences in performance characteristics, availability characteristics, and so on. So, the truth is, even if you use open-source, right, you're not going to get a hundred percent of the same characteristics where you run that. But that said, you still have the freedom of movement, and with I would say and not a huge amount of engineering investment, right, you're going to make sure you can run that workload elsewhere.I kind of think of Spanner in the similar way where yes, I mean, you're going to get all those benefits of Spanner that you can't get anywhere else, like unlimited scale, global consistency, right, no maintenance downtime, five-nines availability, like, you can't really get that anywhere else. That said, not every application necessarily needs it. And you still have that option, right, that if you need to, or want to, or we're not giving you a reasonable price or reasonable price performance, but we're starting to neglect you as a customer—which of course we wouldn't, but let's just say hypothetically, that you know, that could happen—that you still had a way to basically go and run this elsewhere. Now, I'd also want to talk about some of the upsides something like Spanner gives you. Because you talked about, you want to be able to just grab a few things, build something quickly, and then, you know, you don't want to be stuck.The counterpoint to that is with Spanner, you can start really, really small, and then let's say you're a gaming studio, you know, you're building ten titles hoping that one of them is going to take off. So, you can build ten of those, you know, with very minimal spend on Spanner and if one takes off overnight, it's really only the database where you don't have to go and re-architect the application; it's going to scale as big as you need it to. And so, it does enable a lot of this innovation and a lot of cost management as you try to get to that overnight success.Corey: Yeah, overnight success. I always love that approach. It's one of those, “Yeah, I became an overnight success after only ten short years.” It becomes this idea people believe it's in fits and starts, but then you see, I guess, on some level, the other side of it where it's a lot of showing up and doing the work. I have to confess, I didn't do a whole lot of admin work in my production years that touched databases because I have an aura and I'm unlucky, and it turns out that when you blow away some web servers, everyone can laugh and we'll reprovision stateless things.Get too close to the data warehouse, for example, and you don't really have a company left anymore. And of course, in the world of finance that I came out of, transactional integrity is also very much a thing. A question that I had [centers 00:17:51] really around one of the predictions you gave recently at Google Cloud Next, which is your prediction for the future is that transactional and analytical workloads from a database perspective will converge. What's that based on?Andi: You know, I think we're really moving from a world where customers are trying to make real-time decisions, right? If there's model drift from an AI and ML perspective, want to be able to retrain their models as quickly as possible. So, everything is fast moving into streaming. And I think what you're starting to see is, you know, customers don't have that time to wait for analyzing their transactional data. Like in the past, you do a batch job, you know, once a day or once an hour, you know, move the data from your transactional system to analytical system, but that's just not how it is always-on businesses run anymore, and they want to have those real-time insights.So, I do think that what you're going to see is transactional systems more and more building analytical capabilities, analytical systems building, and more transactional, and then ultimately, cloud platform providers like us helping fill that gap and really making data movement seamless across transactional analytical, and even AI and ML workloads. And so, that's an area that I think is a big opportunity. I also think that Google is best positioned to solve that problem.Corey: Forget everything you know about SSH and try Tailscale. Imagine if you didn't need to manage PKI or rotate SSH keys every time someone leaves. That'd be pretty sweet, wouldn't it? With Tailscale SSH, you can do exactly that. Tailscale gives each server and user device a node key to connect to its VPN, and it uses the same node key to authorize and authenticate SSH.Basically you're SSHing the same way you manage access to your app. What's the benefit here? Built-in key rotation, permissions as code, connectivity between any two devices, reduce latency, and there's a lot more, but there's a time limit here. You can also ask users to reauthenticate for that extra bit of security. Sounds expensive?Nope, I wish it were. Tailscale is completely free for personal use on up to 20 devices. To learn more, visit snark.cloud/tailscale. Again, that's snark.cloud/tailscaleCorey: On some level, I've found that, at least in my own work, that once I wind up using a database for something, I'm inclined to try and stuff as many other things into that database as I possibly can just because getting a whole second data store, taking a dependency on it for any given workload tends to be a little bit on the, I guess, challenging side. Easy example of this. I've talked about it previously in various places, but I was talking to one of your colleagues, [Sarah Ellis 00:19:48], who wound up at one point making a joke that I, of course, took way too far. Long story short, I built a Twitter bot on top of Google Cloud Functions that every time the Azure brand account tweets, it simply quote-tweets that translates their tweet into all caps, and then puts a boomer-style statement in front of it if there's room. This account is @cloudboomer.Now, the hard part that I had while doing this is everything stateless works super well. Where do I wind up storing the ID of the last tweet that it saw on his previous run? And I was fourth and inches from just saying, “Well, I'm already using Twitter so why don't we use Twitter as a database?” Because everything's a database if you're either good enough or bad enough at programming. And instead, I decided, okay, we'll try this Firebase thing first.And I don't know if it's Firestore, or Datastore or whatever it's called these days, but once I wrap my head around it incredibly effective, very fast to get up and running, and I feel like I made at least a good decision, for once in my life, involving something touching databases. But it's hard. I feel like I'm consistently drawn toward the thing I'm already using as a default database. I can't shake the feeling that that's the wrong direction.Andi: I don't think it's necessarily wrong. I mean, I think, you know, with Firebase and Firestore, that combination is just extremely easy and quick to build awesome mobile applications. And actually, you can build mobile applications without a middle tier which is probably what attracted you to that. So, we just see, you know, huge amount of developers and applications. We have over 4 million databases in Firestore with just developers building these applications, especially mobile-first applications. So, I think, you know, if you can get your job done and get it done effectively, absolutely stick to them.And by the way, one thing a lot of people don't know about Firestore is it's actually running on Spanner infrastructure, so Firestore has the same five-nines availability, no maintenance downtime, and so on, that has Spanner, and the same kind of ability to scale. So, it's not just that it's quick, it will actually scale as much as you need it to and be as available as you need it to. So, that's on that piece. I think, though, to the same point, you know, there's other databases that we're then trying to make sure kind of also extend their usage beyond what they've traditionally done. So, you know, for example, we announced AlloyDB, which I kind of call it Postgres on steroids, we added analytical capabilities to this transactional database so that as customers do have more data in their transactional database, as opposed to having to go somewhere else to analyze it, they can actually do real-time analytics within that same database and it can actually do up to 100 times faster analytics than open-source Postgres.So, I would say both Firestore and AlloyDB, are kind of good examples of if it works for you, right, we'll also continue to make investments so the amount of use cases you can use these databases for continues to expand over time.Corey: One of the weird things that I noticed just looking around this entire ecosystem of databases—and you've been in this space long enough to, presumably, have seen the same type of evolution—back when I was transiting between different companies a fair bit, sometimes because I was consulting and other times because I'm one of the greatest in the world at getting myself fired from jobs based upon my personality, I found that the default standard was always, “Oh, whatever the database is going to be, it started off as MySQL and then eventually pivots into something else when that starts falling down.” These days, I can't shake the feeling that almost everywhere I look, Postgres is the answer instead. What changed? What did I miss in the ecosystem that's driving that renaissance, for lack of a better term?Andi: That's a great question. And, you know, I have been involved in—I'm going to date myself a bit—but in PHP since 1997, pretty much, and one of the things we kind of did is we build a really good connector to MySQL—and you know, I don't know if you remember, before MySQL, there was MS SQL. So, the MySQL API actually came from MS SQL—and we bundled the MySQL driver with PHP. And so, kind of that LAMP stack really took off. And kind of to your point, you know, the default in the web, right, was like, you're going to start with MySQL because it was super easy to use, just fun to use.By the way, I actually wrote—co-authored—the tab completion in the MySQL client. So like, a lot of these kinds of, you know, fun, simple ways of using MySQL were there, and frankly, was super fast, right? And so, kind of those fast reads and everything, it just was great for web and for content. And at the time, Postgres kind of came across more like a science project. Like the folks who were using Postgres were kind of the outliers, right, you know, the less pragmatic folks.I think, what's changed over the past, how many years has it been now, 25 years—I'm definitely dating myself—is a few things: one, MySQL is still awesome, but it didn't kind of go in the direction of really, kind of, trying to catch up with the legacy proprietary databases on features and functions. Part of that may just be that from a roadmap perspective, that's not where the owner wanted it to go. So, MySQL today is still great, but it didn't go into that direction. In parallel, right, customers wanting to move more to open-source. And so, what they found this, the thing that actually looks and smells more like legacy proprietary databases is actually Postgres, plus you saw an increase of investment in the Postgres ecosystem, also very liberal license.So, you have lots of other databases including commercial ones that have been built off the Postgres core. And so, I think you are today in a place where, for mainstream enterprise, Postgres is it because that is the thing that has all the features that the enterprise customer is used to. MySQL is still very popular, especially in, like, content and web, and mobile applications, but I would say that Postgres has really become kind of that de facto standard API that's replacing the legacy proprietary databases.Corey: I've been on the record way too much as saying, with some justification, that the best database in the world that should be used for everything is Route 53, specifically, TXT records. It's a key-value store and then anyone who's deep enough into DNS or databases generally gets a slightly greenish tinge and feels ill. That is my simultaneous best and worst database. I'm curious as to what your most controversial opinion is about the worst database in the world that you've ever seen.Andi: This is the worst database? Or—Corey: Yeah. What is the worst database that you've ever seen? I know, at some level, since you manage all things database, I'm asking you to pick your least favorite child, but here we are.Andi: Oh, that's a really good question. No, I would say probably the, “Worst database,” double-quotes is just the file system, right? When folks are basically using the file system as regular database. And that can work for, you know, really simple apps, but as apps get more complicated, that's not going to work. So, I've definitely seen some of that.I would say the most awesome database that is also file system-based kind of embedded, I think was actually SQLite, you know? And SQLite is actually still very, very popular. I think it sits on every mobile device pretty much on the planet. So, I actually think it's awesome, but it's, you know, it's on a database server. It's kind of an embedded database, but it's something that I, you know, I've always been pretty excited about. And, you know, their stuff [unintelligible 00:27:43] kind of new, interesting databases emerging that are also embedded, like DuckDB is quite interesting. You know, it's kind of the SQLite for analytics.Corey: We've been using it for a few things around a bill analysis ourselves. It's impressive. I've also got to say, people think that we had something to do with it because we're The Duckbill Group, and it's DuckDB. “Have you done anything with this?” And the answer is always, “Would you trust me with a database? I didn't think so.” So no, it's just a weird coincidence. But I liked that a lot.It's also counterintuitive from where I sit because I'm old enough to remember when Microsoft was teasing the idea of WinFS where they teased a future file system that fundamentally was a database—I believe it's an index or journal for all of that—and I don't believe anything ever came of it. But ugh, that felt like a really weird alternate world we could have lived in.Andi: Yeah. Well, that's a good point. And by the way, you know, if I actually take a step back, right, and I kind of half-jokingly said, you know, file system and obviously, you know, all the popular databases persist on the file system. But if you look at what's different in cloud-first databases, right, like, if you look at legacy proprietary databases, the typical setup is wright to the local disk and then do asynchronous replication with some kind of bounded replication lag to somewhere else, to a different region, or so on. If you actually start to look at what the cloud-first databases look like, they actually write the data in multiple data centers at the same time.And so, kind of joke aside, as you start to think about, “Hey, how do I build the next generation of applications and how do I really make sure I get the resiliency and the durability that the cloud can offer,” it really does take a new architecture. And so, that's where things like, you know, Spanner and Big Table, and kind of, AlloyDB databases are truly architected for the cloud. That's where they actually think very differently about durability and replication, and what it really takes to provide the highest level of availability and durability.Corey: On some level, I think one of the key things for me to realize was that in my own experiments, whenever I wind up doing something that is either for fun or I just want see how it works in what's possible, the scale of what I'm building is always inherently a toy problem. It's like the old line that if it fits in RAM, you don't have a big data problem. And then I'm looking at things these days that are having most of a petabyte's worth of RAM sometimes it's okay, that definition continues to extend and get ridiculous. But I still find that most of what I do in a database context can be done with almost any database. There's no reason for me not to, for example, uses a SQLite file or to use an object store—just there's a little latency, but whatever—or even a text file on disk.The challenge I find is that as you start scaling and growing these things, you start to run into limitations left and right, and only then it's one of those, oh, I should have made different choices or I should have built-in abstractions. But so many of these things comes to nothing; it just feels like extra work. What guidance do you have for people who are trying to figure out how much effort to put in upfront when they're just more or less puttering around to see what comes out of it?Andi: You know, we like to think about ourselves at Google Cloud as really having a unique value proposition that really helps you future-proof your development. You know, if I look at both Spanner and I look at BigQuery, you can actually start with a very, very low cost. And frankly, not every application has to scale. So, you can start at low cost, you can have a small application, but everyone wants two things: one is availability because you don't want your application to be down, and number two is if you have to scale you want to be able to without having to rewrite your application. And so, I think this is where we have a very unique value proposition, both in how we built Spanner and then also how we build BigQuery is that you can actually start small, and for example, on Spanner, you can go from one-tenth of what we call an instance, like, a small instance, that is, you know, under $65 a month, you can go to a petabyte scale OLTP environment with thousands of instances in Spanner, with zero downtime.And so, I think that is really the unique value proposition. We're basically saying you can hold the stick at both ends: you can basically start small and then if that application doesn't need to scale, does need to grow, you're not reengineering your application and you're not taking any downtime for reprovisioning. So, I think that's—if I had to give folks, kind of, advice, I say, “Look, what's done is done. You have workloads on MySQL, Postgres, and so on. That's great.”Like, they're awesome databases, keep on using them. But if you're truly building a new app, and you're hoping that app is going to be successful at some point, whether it's, like you said, all overnight successes take at least ten years, at least you built in on something like Spanner, you don't actually have to think about that anymore or worry about it, right? It will scale when you need it to scale and you're not going to have to take any downtime for it to scale. So, that's how we see a lot of these industries that have these potential spikes, like gaming, retail, also some use cases in financial services, they basically gravitate towards these databases.Corey: I really want to thank you for taking so much time out of your day to talk with me about databases and your perspective on them, especially given my profound level of ignorance around so many of them. If people want to learn more about how you view these things, where's the best place to find you?Andi: Follow me on LinkedIn. I tend to post quite a bit on LinkedIn, I still post a bit on Twitter, but frankly, I've moved more of my activity to LinkedIn now. I find it's—Corey: That is such a good decision. I envy you.Andi: It's a more curated [laugh], you know, audience and so on. And then also, you know, we just had Google Cloud Next. I recorded a session there that kind of talks about database and just some of the things that are new in database-land at Google Cloud. So, that's another thing that if folks more interested to get more information, that may be something that could be appealing to you.Corey: We will, of course, put links to all of this in the [show notes 00:34:03]. Thank you so much for your time. I really appreciate it.Andi: Great. Corey, thanks so much for having me.Corey: Andi Gutmans, VP and GM of Databases at Google Cloud. I'm Cloud Economist Corey Quinn and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice along with an angry, insulting comment, then I'm going to collect all of those angry, insulting comments and use them as a database.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

Navati Jain (she/her), iOS Developer @ Loblaw Digital, in Toronto and Evangelist at Women Who Code Mobile Track, shares “Let's Get Fired Up: Getting started with Firebase Firestore.” She discusses some ways to use Firebase, compares relational and SQL databases, and gives examples of building these databases.

A high school class on Pascal launched Andi's interest in programming (starting on an Apple IIc).Andi was bored with his university studies and took on an extra-credit programming project that turned into PHP3, the version that built a million websites.PHP gets a lot of hate, and we have two theories about why. First, it's primarily brownfield development, and we all know that hell is other people's code. Second, it democratized development—a great thing in many ways - that nevertheless led to a lot of less than professional code making it's way to production.Andi cofounded Zend Technologies to oversee PHP advances and served as CEO from 2009 until the company's acquisition in 2015. After Zend Technology, Andi became one of what he jokes was “five folks in a garage” building a new graph database for Amazon.Now, at Google, Andi runs the operational database for Google Cloud Platform, including managed third parties and cloud-native databases Spanner, Bigtable, and Firestore.His background in programming makes Andi sensitive to the importance of prioritizing developer experience: “the number-one person using our services are our developers. And so we need to make [our technology] super-productive and simple and easy and fun for developers to use.”Connect with Andi on LinkedIn.

On The Cloud Pod this week, the team decides 2022 is already a long, cursed year — bring on 2023. Plus nuggets of wisdom from Gartner, Orca discovers breaksformation and Glue vulnerabilities, and 10 questions to help boards (and others) maximize cloud opportunities. A big thanks to this week's sponsors: Foghorn Consulting, which provides full-stack cloud solutions with a focus on strategy, planning and execution for enterprises seeking to take advantage of the transformative capabilities of AWS, Google Cloud and Azure. JumpCloud, which offers a complete platform for identity, access, and device management — no matter where your users and devices are located.  This week's highlights

Genre: Cloud Services, Career Development. Cloud services are services provided by certain companies which allows remote accessibility of data with the help of internet. These services are very important as many companies have branches overseas which makes it difficult for employees to collaborate and work on certain projects. One of the emerging companies who provide reliable cloud resources is google cloud services which will be discussed in detail in this episode.   In the episode: Start 0:00:00 Pritam's career so far and top 3 things that helped him in his career. 0:02:55 What are different types of databases and how do they help the businesses? 0:04:22 What does google cloud offer to meet various DB requirements? 0:06:07 Data Warehousing options available on Google Cloud. 0:09:21 Google Cloud BigTable 0:12:56 How to get started with Database Migrations for homogeneous and heterogeneous scenarios? 0:15:51 Rapid fire questions 0:19:10 What would be your advice for those aspiring to make big in their careers? 0:23:21 Trivia on Websites 0:25:48  About the guest: Pritam has 15 years of IT industry experience, with Specialization on Cloud (IaaS, PaaS), & pre-sales experience in various geographies and market segments. His specialities include Google Cloud, AWS, Oracle Public Cloud, PaaS, IaaS, Hybrid Cloud, Cloud Security, Oracle Identity & Access Management, Oracle Database Technology related products, SAP Databases, SAP HANA. Important Links: Google Cloud Databases  https://cloud.google.com/products/databases Relational Databases           Cloud SQL https://cloud.google.com/sql          Cloud Spanner https://cloud.google.com/spanner Non relational Databases           BigTable https://cloud.google.com/bigtable          Firestore https://cloud.google.com/firestore Relational DB Migrations i.e. Database Migration Service https://cloud.google.com/database-migration Serverless Multicloud Datawarehouse Service on Google Cloud https://cloud.google.com/bigquery/   Connect with Pritam on LinkedIn: https://www.linkedin.com/in/pritam-sahoo-77a438a/ Naveen Samala https://www.linkedin.com/mwlite/in/naveensamala Sudhakar Nagandla: https://www.linkedin.com/in/nvsudhakar   Watch the video interview on YouTube: https://youtu.be/PO7Kk_yNkzM  

We're finishing out 2021 with a celebration of our favorite episodes and topics from the year! From new tools for Cost Optimization in GKE and advances in AI to tips for improving feelings of imposter syndrome, Carter Morgan, Stephanie Wong, and Mark Mirchandani share memorable moments from 2021 and look forward to future episodes. Carter Morgan Carter Morgan is Developer Advocate for Google Cloud, where he creates and hosts content on Google's Youtube channel, co-hosts several Google Cloud podcasts, and designs courses like the Udacity course “Scalable Microservices with Kubernetes” he co-created with Kelsey Hightower. Carter Morgan is an international standup comedian, who's approach of creating unique moments with the audience in front of him has seen him perform all over the world, including in Paris, London, the Melbourne International Comedy Festival with Joe White. And in 2019, and the 2019 Edinburgh Fringe Festival. Previously, he was a programmer for the USAF and Microsoft. Stephanie Wong Stephanie Wong is a Developer Advocate focusing on online content across all Google Cloud products. She's a host of the GCP Podcast and the Where the Internet Lives podcast, along with many GCP Youtube video series. She is the winner of a 2021 Webby Award for her content about data centers. Previously she was a Customer Engineer at Google and at Oracle. Outside of her tech life she is a former pageant queen and hip hop dancer and has an unhealthy obsession with dogs. Mark Mirchandani Mark Mirchandani is a developer advocate for Google Cloud, occasional host of the Google Cloud Platform podcast, and helps create content for users. Cool things of the week Anthos Multi-Cloud v2 is generally available docs Machine learning, Google Kubernetes Engine, and more: 10 free training offers to take advantage of before 2022 blog The past, present, and future of Kubernetes with Eric Brewer blog GCP Podcast Episode 124: VP of Infrastructure Eric Brewer podcast Our Favorite Episodes of 2021 Mark's Favorites GCP Podcast Episode 252: GKE Cost Optimization with Kaslin Fields and Anthony Bushong podcast GCP Podcast Episode 267: Cloud Firestore for Users who are new to Firestore podcast GKE Essentials videos Beyond Your Bill vidoes Stephanie's Favorites GCP Podcast Episode 270: Traditional vs. Service Networking with Ryan Przybyl podcast GCP Podcast Episode 271: The Future of Service Networking with Ryan Przybyl podcast GCP Podcast Episode 279: MLB with Perry Pierce and JoAnn Brereton podcast Carter's Favorites GCP Podcast Episode 284: State of DevOps Report 2021 with Nathen Harvey and Dustin Smith podcast GCP Podcast Episode 287: Imposter Syndrome with Carter Morgan podcast Most Popular Episodes of 2021 GCP Podcast Episode Episode 264: SRE III with Steve McGhee and Yuri Grinshtey podcast GCP Podcast Episode 258: The Power of Serverless with Aparna Sinha and Philip Beevers podcast GCP Podcast Episode 253: Data Governance with Jessi Ashdown and Uri Gilad podcast GCP Podcast Episode 263: SAP + Apigee: The Power of APIs with Benjamin Schuler and Dave Feuer podcast GCP Podcast Episode 271: The Future of Service Networking with Ryan Przybyl podcast Sound Effects Attribution “Dun Dun Duuun” by Divenorth of Freesound.org “Cash Register” by Kiddpark of Freesound.org “Jingles and Pings” by BristolStories of HDInteractive.com “Time – Inception Theme” Composed by Hanz Zimmer (super-low-budget midi version) Hosts Stephanie Wong, Carter Morgan and Mark Mirchandani

Guest Peter Friese - Blog Twitter - @peterfriese YouTube - @peterfriese GitHub - @peterfriese Youtube Video - https://youtu.be/8m8oppa-LosRelated Episodes Episode 87 - Core Data Fun with Tim Mitra Episode 85 - AWS Amplify with Kilo Loco Episode 75 - Year of the Server with Tim Condon - Part 2 Episode 35 - SwiftUI - The Good, the Bad, and the Benefits Episode 8 - Cloud and Backend Services For Apps with Erik Gillespie Related Links Firebase Summit - November 10th Firebase YouTube Channel Firebase Blog Firebase Medium channel Firebase vs GCP Videos Projects & storage Functions & Firestore the LansingCodes app that never was Authenticate with Firebase Anonymously on Apple Platforms Make It So - Replicating Apple's Reminders app with SwiftUI and Firebase Swift on Cloud Run by Grant Timmerman from GCP SponsorsRevenueCatUsing RevenueCat to power your in-app purchase infrastructure solves: For edge cases you don't even know you have Protects from outages your team hasn't seen yet Saves you time on future maintenance  As well as new features released by the app stores Empowers your marketing teams with clean, reliable IAP data All that to say, RevenueCat handles all the headaches of in-app purchases so you can get back to building your app. Try RevenueCat today at revenuecat.com.LinodeA cloud experience developers love Great for Setting Up a Backend for Your App Variety of VM Configurations and Settings Reasonable Pricing Starting at $5 per month Global Data Centers The Developer Cloud Simplified Try it today with this special link:https://www.linode.com/?r=97e09acbd5d304d87dadef749491d245e71c74e7Check out OrchardNest Today:https://orchardnest.comShow Notes What does Firebase consist of How to use it properly in your iOS app How Firestore's NoSQL DB works How to work with Firestore and SwiftUI What are Firebase's authentication features Setting up security properly How to authenticate with Firebase anonymously? Register for Firebase Summit Social MediaEmailleo@brightdigit.comGitHub - @brightdigitTwitter BrightDigit - @brightdigitLeo - @leogdionRedditLeo - /u/leogdionLinkedInBrightDigitLeoInstagram - @brightdigitPatreon - empowerappshowCreditsMusic from https://filmmusic.io"Blippy Trance" by Kevin MacLeod (https://incompetech.com)License: CC BY (http://creativecommons.org/licenses/by/4.0/)★ Support this podcast on Patreon ★

John shares his first impressions of the new 14-inch MacBook Pro and how he has been utilizing Swift's new concurrency features to get the most out of the M1 Max. Also, Rambo's work with Shortcuts, maintaining SwiftUI-based Mac apps, and much more. Accelerate app development with Firebase: Use Firebase's backend services like Firestore, Cloud Storage, Authentication, and more to build serverless, secure apps at global scale. Get started now. Sponsored by Survivor: Protect your iPhone 13 w/ Survivors new MagSafe collection and enter to win the iPhone 13 Pro. Sponsored by RevenueCat: RevenueCat makes it easy to build and manage in-app purchases on iOS, Android, and the web. Learn more.  Download MP3 Hosts Gui on Twitter: @_inside John on Twitter: @johnsundell Links Using SwiftUI to build internal tools John's MacBook Pro box tweet Swift's new concurrency system gains backward compatibility in Xcode 13.2 Publish Subscribe 🟣 Apple Podcasts🟠 Overcast🟢 Spotify If you have any feedback about the show, feel free to reach out on Twitter or send us an email.

0:22 - Episode begins2:50 - Collaboration tool jam.dev was featured in Forbes3:35 - usepastel.com7:15 - Postman has a tool called flows in beta9:25 - Mutiny, a no-code marketing website builder to help you convert11:15 - ClickUp Poll14:52 - PixieBrix, a low-code extension builder to automate the web15:25 - GitHub + Your Webflow site and versioning with webflow-git17:39 - Forum post by Jarek18:05 - Rowy unites Google Cloud with a spreadsheet front end for your Firestore data18:53 - Big news from Bravo Studio26:00 - Has anyone here used Reform?27:35 - I love it when people build on top of no-code tools — Airtable Invoice Maker28:13 - Y Code lets you build using Tailwind CSS classes and adds more breakpoints29:40 - Want to do some freelancing for Zapier? They're looking for a TikTok creator31:05 - Aron Korenblit has a video out going over how to use colors in Airtable31:22 - Glide has pages?!? 33:03 - Coda made some BIG announcements at their block party today!34:22 - Coda's new editor35:29 - Canvas Column in Coda38:00 - Coda Fund39:10 - Coda SDK42:38 - Kyle's tweet

John gets back into game development, Rambo builds a custom Bluetooth packet parser for AirBuddy, and the two embark on another technical deep dive — this time into the big topic of performance tuning. Accelerate app development with Firebase: Use Firebase's backend services like Firestore, Cloud Storage, Authentication, and more to build serverless, secure apps at global scale. Get started now. Download MP3 Hosts Gui on Twitter: @_inside John on Twitter: @johnsundell Links Imagine Engine John's SwiftUI game demo Rambo's debug app for inspecting BLE advertisements Synalyze It! Sets in Swift Time complexity Entity Component System (ECS) cloc Subscribe 🟣 Apple Podcasts🟠 Overcast🟢 Spotify If you have any feedback about the show, feel free to reach out on Twitter or send us an email.

¡Hola a todos! Hoy os vengo a contar las sensaciones que he tenido utilizando firestore en la primera app que publiqué en agosto como parte del reto de una app cada dos meses. Por si tenéis curiosidad y le queréis echar un vistazo, la app es «Story Planet«, una pequeña app para descubrir y compartir […]

John and Rambo discuss the iOS 15 beta process, the latest round of App Store debates, Swift concurrency backward compatibility, and whether Apple should embrace a more continuous delivery process for new APIs and system features. Sponsored by Things: The award-winning to-do app for iPhone, iPad, and Mac — now with Markdown support! Accelerate app development with Firebase: Use Firebase's backend services like Firestore, Cloud Storage, Authentication, and more to build serverless, secure apps at global scale. Get started now. Download MP3 Hosts Gui on Twitter: @_inside John on Twitter: @johnsundell Links rambo.codes Files TestFlight for Mac beta FusionCast TestFlight beta Doug Gregor's Swift concurrency PR Apple's press release about its App store “updates” “Apple loosens rules for developers in major concession amid antitrust pressure” - The Washington Post The StatusBuddy code base Subscribe 🟣 Apple Podcasts🟠 Overcast🟢 Spotify If you have any feedback about the show, feel free to reach out on Twitter or send us an email.

This is a fifth episode of GCP Series which covers an overview of NOSQL Services like FireStore, BigTable and MemStore. Please listen other series as well. --- Send in a voice message: https://anchor.fm/vishnu-vg/message

John's new iPad development setup, Rambo's widget layout challenges, and Apple's (lack of a strong) home device strategy. Also, managing deadlines, maintaining SwiftUI views across multiple system versions, and continuous integration. Accelerate app development with Firebase: Use Firebase's backend services like Firestore, Cloud Storage, Authentication, and more to build serverless, secure apps at global scale. Get started now. Sponsored by Pillow: Pillow is an all-in-one sleep tracking solution to help you get a better night's sleep. Download it from the App Store today. Download MP3 Hosts Gui on Twitter: @_inside John on Twitter: @johnsundell Links Publish Working Copy SwiftUI layout priorities Report: Apple lacks a ‘strong living room hardware strategy,' still planning HomePod/Apple TV combo for 2023 Klipsch The Fives fastlane Bitrise Jenkins Subscribe 🟣 Apple Podcasts🟠 Overcast🟢 Spotify If you have any feedback about the show, feel free to reach out on Twitter or send us an email.

Eure vier Stamm-Hosts der programmier.bar sind heute wieder vereint und berichten von Neuigkeiten aus der Kalenderwoche 31: In Dockerfiles kann man nun heredocs nutzen. Einer der großen Vorteile ist, dass man mehrere Run Statements schreiben kann, ohne eine seltsame Syntax für den Multiline-Support nutzen zu müssen. Node 16.6 ist raus und unterstützt die Array-Prototype-Funktion “at”, die es noch nicht in den Standard geschafft hat, aber schon von Chrome unterstützt wird. Wir bekommen ein Update zu CouchBase, das nun in Version 7 verfügbar ist.Jetpack Compose ist stable und es gibt eine neue Android Studio-Version namens Arctic Fox. Bei Firestore ist neu, dass man vordefinierte Daten nun im Bundle ausliefern kann und daher nicht mehr bei App-Start einen Online Sync benötigt. Und um unseren Quantencomputer-Hype fortzusetzen: Das Deutsche Museum in München ist das weltweit erste, das einen Sycamore Quantenchip von Google ausstellt.Schreibt uns!Schickt uns eure Themenwünsche und euer Feedback.podcast@programmier.barFolgt uns!Bleibt auf dem Laufenden über zukünftige Folgen und beteiligt euch an Community-Diskussionen.TwitterInstagramFacebookMeetup 

The adoption of cloud databases is accelerating, driven by business transformation and the need for database modernization. In this episode of the Cloud Database Report Podcast, founding editor John Foley talks with Andi Gutmans, Google Cloud's GM and VP of Engineering for Databases, about the platforms and technologies that organizations are using to build and manage these new data environments. Gutmans is responsible for development of Google Cloud's databases and related technologies, including Bigtable, Cloud SQL, Spanner, and Firestore. In this conversation, he discusses the three steps of cloud database adoption: migration, modernization, and transformation. "We're definitely seeing a tremendous acceleration," he says. Gutmans talks about the different types of database migrations, from "homogenous" migrations that are relatively fast and simple to more complex ones that involve different database sources and target platforms. He reviews the tools and services available to help with the process, including Google Cloud's Database Migration Service and Datastream for change data capture. Gutmans provides an overview of the "data cloud" model as a comprehensive data environment that connects multiple databases and reduces the need for organizations to build their own plumbing. Data clouds can "democratize" data while providing security and governance. Looking ahead, Google Cloud will continue to focus on database migrations, developing new enterprise capabilities, and providing a better experience for developers. 

Brian Dorsey and Mark Mirchandani are talking intro to Firestore this week with fellow Googler Allison Kornher. Allison, a Cloud Technical Resident, starts the show telling us about the program and how it brought her to Firestore. Allison takes us through the differences between SQL and NoSQL databases and describes the four categories of NoSQL databases: family, document, key value, and graph. Firestore is a scalable, flexible NoSQL document database. To illustrate the uses and benefits of Firestore, Allison walks us through a delicious pizza example. Each document in the database belongs to a collection, which is used to organize these documents. Firestore documents are assigned an identifier and can be quickly changed and called within their collections. Because these documents are stored in an implicit schema in key value pairs, developers have control over the details of database organization and data change and growth are easy to manage. The availability of subcollections further adds to the flexibility of Firestore database design. Choosing a database type will depend on the situation, and Allison suggests this starts with a look at CAP theorem. If a document database is your database of choice, Allison gives our listeners tips for getting started with Firestore and clearing any hurdles along the way. Allison Kornher Allison is a Cloud Technical Resident and has worked helping startups looking to join GCP and in the Premium Tier Cloud Support organization with a focus on Storage. Cool things of the week BigQuery admin reference guide: Tables & routines blog Top 25 Google Search terms, now in BigQuery blog Three security and scalability improvements for Cloud SQL for SQL Server blog GCP Podcast Episode 247: Cloud SQL Insights with Nimesh Bhagat podcast GCP Podcast Episode 163: Cloud SQL with Amy Krishnamohan podcast Interview Cloud Firestore site Cloud Firestore Documentation docs Cloud Firestore explained: for users who never used Firestore before blog Gabi on Twitter site Datastore site BigTable site Firebase Realtime Database site Memorystore site Cloud Spanner site GCP Podcast Episode 248: Cloud Spanner Revisited with Dilraj Kaur and Christoph Bussler podcast All you need to know about Firestore: A cheatsheet blog What’s something cool you’re working on? Brian has been working on sharing a persistent disk between Google Compute Engine VMs. Cloud Storage site Cloud Filestore site Cloud SQL site

Hola a tod@s ya tenemos nuevo episodio, esta vez hablamos de #firestore una base de datos #realtime. Hablamos de sus propiedades, usos y recomendaciones. Recuerda compartir. Síguenos: https://twitter.com/jggomezt https://twitter.com/DevHackCali

タイムライン 01:00 Firestoreのデータを簡単にAlgoliaに連携できるFirebaseの “Search with Algolia” Extension 05:13 サーチ vs ブラウズ: ユーザーのインテントを満たす方法 12:55 GymsharkのMACHを使った実践的なSearch and Navigationの事例 関連リンク (英語ブログ) Announcing the Firebase + Algolia search extension (Firebaseのページ) Firebase Extensions (英語ブログ) How to satisfy user intent when considering search vs browse (英語ブログ) Gymshark's journey to MACH: The practical case for search and navigation 関連Youtubeビデオ

https://codingcat.dev/podcasts/firestore-for-unity-and-c/ --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app --- Send in a voice message: https://anchor.fm/purrfect-dev/message Support this podcast: https://anchor.fm/purrfect-dev/support

Matthew Lawson of IKEA Retail (Ingka Group) joins Mark Mirchandani and Priyanka Vergadia today, telling us all about IKEA Retail (Ingka Group)’s move to the cloud. Engineering Manager Matt and his team primarily focus on the early stages of development at IKEA Retail (Ingka Group), helping the company with research and planning as well as development. Lately, they have been focused on incrementally moving IKEA Retail (Ingka Group)’s digital presence to the cloud. Matt explains the digital shift process for IKEA Retail (Ingka Group) and why they chose to modernize and move pieces to the cloud over time. By illustrating through examples, he details projects the team worked on during this digital transformation. Matt also talks about the changes to the IKEA Retail (Ingka Group) Digital DNA, emphasizing progress made in their digital culture to allow for the drastic change from on-prem to the cloud. Using managed services like Google Cloud Run, IKEA Retail (Ingka Group) has been able to adapt and grow in the cloud. Because IKEA Retail (Ingka Group)’s culture is developer-supportive, Matt and his team were able to research and convince the company that managed services in the cloud was the way to go, and developers were allowed some autonomy to choose things like GKE to create an effective cloud environment for IKEA Retail (Ingka Group). Next year, Matt and his engineering team are hoping to run some online hackathons and other events. Matthew Lawson Matthew Lawson is responsible for leading a small innovation team at IKEA Retail (Ingka Group) in southern Sweden. He has worked within the IT/Digital industry for 13 years and has deep experience and knowledge in application development, automation, DevOps and cloud technologies - especially serverless. He has a deep passion for enabling teams to quickly provide business value across the entire digital and physical customer journey. Cool things of the week Next OnAir as it happens: All the announcements in one place blog A developer’s take: Get the most out of Cloud AI Week at Next OnAir blog BANDAI NAMCO Entertainment Inc. brings PAC-MAN to the real world in PAC-MAN GEO blog Interview IKEA Retail (Ingka Group) site Matt’s Next Session: Serverless Functions (FaaS): Secure, Scalable, Resilient, Anywhere site ML Kit site Compute Engine site Cloud Run site Google Cloud Functions site Pub/Sub site BigQuery site GKE site Firestore site IKEA Retail (Ingka Group) is hiring! site Tip of the week This week, we get a great tip from our friend Grant on using Google Cloud Functions! github What’s something cool you’re working on? Priyanka is working on sketches like this summary of Google Cloud Next and more GCP Comics!

Estamos en una nueva temporada esta vez hablando de Google Cloud Platform. En este episodio hablo sobre Firestore. Una base de datos NoSQL, serverless, real time y con un gran rendimiento. Recuerda compartir si crees en la comunidad.

Cuáles son los servicios de firebase para almacenar datos? Qué es firestore? Qué es real time database? Cuándo usar firestore o real time database ? Cuál es mejor? Cómo guarda la información firestore? Cuáles son los costos? Esto y mucho más aprenderás en este episodio

In this episode of Adventures in Angular the panel has fun interviewing David East about Firebase. David starts by sharing what it was like at the recent Firebase Summit in Madrid. There were so many announcements they had a tough time fitting them all into the one-hour keynote address.    One of the cool new features announced at the Firebase Summit is Firebase Extension, David describes it as serverless without any code. The panel discusses this feature and how it works. Another cool feature announced is Google Analytics for Firebase. This allows you to use Firebase tools in conjunction with Google Analytics. The panel considers the smart things you can do in your app with this feature.    The next feature the panel discusses is Remote Config which allows you to store data and then pull out that information on demand. If you use the Google Analytics for Firebase you can target specific data for certain audiences. David explains that before this could only be done with native apps. He also explains how in doing this you no longer have to worry about the gtag loader and defines gtag for the panel.    The panel gets a little off track as David jokingly explains his beef with Aaron Frost, Frosty. Frosty host My Angular Story and a while back had twitted looking for awesome angular stories. David had responded but never heard back from Frosty. Frosty jokingly says he faxed an invite to David. The panel jokes about how awesome David’s episode will be and tells everyone to look out for his episode.    Getting back on track, David gives more examples of ways to use the Remote Config feature on with the Google Analytics for Firebase. Frosty confesses he needs to get better at looking at analytics. Sharing an example from a company he is currently working for, Frosty explains how they made nearly 2 million dollars just by changing the color of a button. The panel considers how minor changes like that can make such a big difference and how analytics helps you target your audience.    David shares the story behind writing Angular Fire. Jeff Cross worked on the angular team and started writing angular fire but then left for Nrwl. After Jeff left, David took over and ended up rewriting the entire library. He explains some of the mistakes that they made that led to the rewrite and how he fixed them.    The panel wonders at David about using Angular Fire and NgRX. David tells the panel that the Firebase console uses NgRx under the hood and shares what he learned while working on it. Using firebase and NgRx can be very confusing because of the mass duplication of responsibility. David’s advice is to let Firebase and NgRx do their own thing and connect the dots with RxJs.    David discusses Firestore, a very advanced caching system and what you can do with it. Including, working offline and setting security rules. Frosty brings up Firebase Messaging Cues, he explains that it is similar to three-way messaging cues except its n-way. David explains that even though he is intrigued by the idea, he does not approve of the name. The panel considers possible use cases for an n-way messaging cue. David explains some of the costs and benefits of this architecture.    The episode ends with a discussion of Firebase’s documentation, which is currently a group of markdown files. David defends the simplicity of this documentation style and gives recommendations and resources for those who need more help.  Panelists Aaron Frost Brian Love Alyssa Nicoll Shai Reznik Guest David East Adventures in Angular is produced by DevChat.TV in partnership with Hero Devs Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Flatfile Cachefly Links https://firebase.google.com/ https://firebase.google.com/summit My Angular Story https://fireship.io/ Fireship Youtube https://twitter.com/_davideast https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast Picks Brain Love: Bonnie Love Aaron Frost: Stop shaming people Miss Saigon Alyssa Nicoll: David East David East: Alyssa Nicoll Freakonomics The Signal and the Noise: Why So Many Predictions Fail-But Some Don't  

In this episode of Adventures in Angular the panel has fun interviewing David East about Firebase. David starts by sharing what it was like at the recent Firebase Summit in Madrid. There were so many announcements they had a tough time fitting them all into the one-hour keynote address.    One of the cool new features announced at the Firebase Summit is Firebase Extension, David describes it as serverless without any code. The panel discusses this feature and how it works. Another cool feature announced is Google Analytics for Firebase. This allows you to use Firebase tools in conjunction with Google Analytics. The panel considers the smart things you can do in your app with this feature.    The next feature the panel discusses is Remote Config which allows you to store data and then pull out that information on demand. If you use the Google Analytics for Firebase you can target specific data for certain audiences. David explains that before this could only be done with native apps. He also explains how in doing this you no longer have to worry about the gtag loader and defines gtag for the panel.    The panel gets a little off track as David jokingly explains his beef with Aaron Frost, Frosty. Frosty host My Angular Story and a while back had twitted looking for awesome angular stories. David had responded but never heard back from Frosty. Frosty jokingly says he faxed an invite to David. The panel jokes about how awesome David’s episode will be and tells everyone to look out for his episode.    Getting back on track, David gives more examples of ways to use the Remote Config feature on with the Google Analytics for Firebase. Frosty confesses he needs to get better at looking at analytics. Sharing an example from a company he is currently working for, Frosty explains how they made nearly 2 million dollars just by changing the color of a button. The panel considers how minor changes like that can make such a big difference and how analytics helps you target your audience.    David shares the story behind writing Angular Fire. Jeff Cross worked on the angular team and started writing angular fire but then left for Nrwl. After Jeff left, David took over and ended up rewriting the entire library. He explains some of the mistakes that they made that led to the rewrite and how he fixed them.    The panel wonders at David about using Angular Fire and NgRX. David tells the panel that the Firebase console uses NgRx under the hood and shares what he learned while working on it. Using firebase and NgRx can be very confusing because of the mass duplication of responsibility. David’s advice is to let Firebase and NgRx do their own thing and connect the dots with RxJs.    David discusses Firestore, a very advanced caching system and what you can do with it. Including, working offline and setting security rules. Frosty brings up Firebase Messaging Cues, he explains that it is similar to three-way messaging cues except its n-way. David explains that even though he is intrigued by the idea, he does not approve of the name. The panel considers possible use cases for an n-way messaging cue. David explains some of the costs and benefits of this architecture.    The episode ends with a discussion of Firebase’s documentation, which is currently a group of markdown files. David defends the simplicity of this documentation style and gives recommendations and resources for those who need more help.  Panelists Aaron Frost Brian Love Alyssa Nicoll Shai Reznik Guest David East Adventures in Angular is produced by DevChat.TV in partnership with Hero Devs Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Flatfile Cachefly Links https://firebase.google.com/ https://firebase.google.com/summit My Angular Story https://fireship.io/ Fireship Youtube https://twitter.com/_davideast https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast Picks Brain Love: Bonnie Love Aaron Frost: Stop shaming people Miss Saigon Alyssa Nicoll: David East David East: Alyssa Nicoll Freakonomics The Signal and the Noise: Why So Many Predictions Fail-But Some Don't  

In this episode of Adventures in Angular the panel has fun interviewing David East about Firebase. David starts by sharing what it was like at the recent Firebase Summit in Madrid. There were so many announcements they had a tough time fitting them all into the one-hour keynote address.    One of the cool new features announced at the Firebase Summit is Firebase Extension, David describes it as serverless without any code. The panel discusses this feature and how it works. Another cool feature announced is Google Analytics for Firebase. This allows you to use Firebase tools in conjunction with Google Analytics. The panel considers the smart things you can do in your app with this feature.    The next feature the panel discusses is Remote Config which allows you to store data and then pull out that information on demand. If you use the Google Analytics for Firebase you can target specific data for certain audiences. David explains that before this could only be done with native apps. He also explains how in doing this you no longer have to worry about the gtag loader and defines gtag for the panel.    The panel gets a little off track as David jokingly explains his beef with Aaron Frost, Frosty. Frosty host My Angular Story and a while back had twitted looking for awesome angular stories. David had responded but never heard back from Frosty. Frosty jokingly says he faxed an invite to David. The panel jokes about how awesome David’s episode will be and tells everyone to look out for his episode.    Getting back on track, David gives more examples of ways to use the Remote Config feature on with the Google Analytics for Firebase. Frosty confesses he needs to get better at looking at analytics. Sharing an example from a company he is currently working for, Frosty explains how they made nearly 2 million dollars just by changing the color of a button. The panel considers how minor changes like that can make such a big difference and how analytics helps you target your audience.    David shares the story behind writing Angular Fire. Jeff Cross worked on the angular team and started writing angular fire but then left for Nrwl. After Jeff left, David took over and ended up rewriting the entire library. He explains some of the mistakes that they made that led to the rewrite and how he fixed them.    The panel wonders at David about using Angular Fire and NgRX. David tells the panel that the Firebase console uses NgRx under the hood and shares what he learned while working on it. Using firebase and NgRx can be very confusing because of the mass duplication of responsibility. David’s advice is to let Firebase and NgRx do their own thing and connect the dots with RxJs.    David discusses Firestore, a very advanced caching system and what you can do with it. Including, working offline and setting security rules. Frosty brings up Firebase Messaging Cues, he explains that it is similar to three-way messaging cues except its n-way. David explains that even though he is intrigued by the idea, he does not approve of the name. The panel considers possible use cases for an n-way messaging cue. David explains some of the costs and benefits of this architecture.    The episode ends with a discussion of Firebase’s documentation, which is currently a group of markdown files. David defends the simplicity of this documentation style and gives recommendations and resources for those who need more help.  Panelists Aaron Frost Brian Love Alyssa Nicoll Shai Reznik Guest David East Adventures in Angular is produced by DevChat.TV in partnership with Hero Devs Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Flatfile Cachefly Links https://firebase.google.com/ https://firebase.google.com/summit My Angular Story https://fireship.io/ Fireship Youtube https://twitter.com/_davideast https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast Picks Brain Love: Bonnie Love Aaron Frost: Stop shaming people Miss Saigon Alyssa Nicoll: David East David East: Alyssa Nicoll Freakonomics The Signal and the Noise: Why So Many Predictions Fail-But Some Don't  

Wir nehmen den Google-Werkzeugkasten zum Entwickeln mobiler Apps genauer unter die Lupe. Google Firebase kann in vielen Bereichen der App-Entwicklung Hilfestellungen leisten und das Leben von EntwicklerInnen einfacher machen. Sebi und Dennis waren in Madrid bei einer Veranstaltung im Rahmen des Google Firebase Summits und berichten von ihren Erfahrungen. Außerdem gehen wir auf alle Tools ein, die Firebase unter sich vereint.In dieser Folge geht es um die Bereiche "Entwickeln" und "Qualität". Da Firebase einiges an Funktionalitäten bietet, gibt es mit Folge 41 einen zweiten Teil, in dem es um "Analyse" und "Wachsen" geht.Picks of the DayDennis: Nuki, das smarte Türschloss Fabi: Reaktive Programming zusammengefasst Sebi: QuickPath in iOS 13Schreibt uns! Schickt uns eure Themenwünsche und euer Feedback. podcast@programmier.bar Folgt uns! Bleibt auf dem Laufenden über zukünftige Folgen und Meetups und beteiligt euch an Community-Diskussionen. Twitter Instagram Facebook Meetup YouTubeErfahrt hier, wann das nächste Meetup in unserem Office in Bad Nauheim stattfindet. Meetup Musik: Hanimo

Jeff Whelpley joins us for a deep dive into Firestore --- Video of episode: https://youtu.be/jmitfq11FWA --- Support this podcast: https://anchor.fm/angularair/support

Datenbanken: relational oder nicht-relational? SQL oder NoSQL? Und spricht man es "Es Kuh El" oder "Sequel"? In Folge 33 sprechen wir nicht nur über unser neues Büro, sondern vor allem über Datenbanken. Wie geben einen Einblick in die von uns genutzten Technologien und erzählen von unseren Erfahrungen in Hinblick auf Skalierung und Wartung. Picks of the Day Fabi: "docker-compose start/stop/restart {service-name}": Damit muss man nicht alle Container per up und down im Fehlerfall neustarten, sondern kann es auch mit einzelnen Containern aus der docker-compose.yml machen. Dennis: Intergrieren von mehreren Kalendern in Einem. Schreibt uns! Schickt uns eure Themenwünsche und euer Feedback. podcast@programmier.bar Folgt uns! Bleibt auf dem Laufenden über zukünftige Folgen und Meetups und beteiligt euch an Community-Diskussionen. Twitter Instagram Facebook Meetup YouTube Erfahrt hier, wann das nächste Meetup in unserem Office in Bad Nauheim stattfindet. Meetup Musik: Hanimo

On this episode, our hosts Mark Mirchandani and Gabi Ferrara dive into Google Cloud Platform UX with guest and Google Product Designer Michael Kleinerman. Michael’s path to Product Designer started with “ancient” tech designing with Flash and 3D motion graphics and progressed from there through interaction designer to his place now with Google. His experience has helped him appreciate the many different kinds of designers needed for projects and how they have to work together for a good product. At Google, Michael’s team builds design systems that create a balance between what Google uses and what the products built on Google use. He adopted Material Design, which offers guidelines for patterns and components of design, to Google Cloud. Material Design spans across multiple devices and screen sizes to help simplify design across devices. When Cloud reached the enterprise space, where components can be more complex, Michael’s team worked to adjust Cloud using Material Design so that features like tables would work correctly. Accessibility is also a top priority for Cloud and the design team. To begin the process of designing for accessibility, the team finds the top three or so reasons that a user would come to their product and ensures those are accessible to all. The next step is to create easier usability in the second tier features of the product, and then all features beyond. Using a screen reader, they go through the product to see if it’s usable, and really try to make the experience better. The team also makes sure there are a lot of guidance pages as well. The goal in product design is to make things simple and consistent for everyone. Michael Kleinerman Michael is a Product Designer at Google. He worked on Android and YouTube in the Bay Area before joining Cloud in NYC, where he started by leading the UX for Firestore until it launched in both Firebase and GCP. This work evolved into his current role on the core platform team, responsible for the design direction of the main design system used by producer teams to build and launch products on GCP. Cool things of the week Committed use discounts at a glance blog Networking in depth blog Chatbots with Dialog Flow blog and video Turn it up to eleven: Java 11 runtime comes to App Engine blog App Engine second generation runtimes now get double the memory; plus Go 1.12 and PHP 7.3 now generally available blog Interview Material.io site Material Design site Firebase site Cloud Firestore site Question of the week How do I work with my containers locally and then get them into the cloud? Where can you find us next? Gabi is done traveling. Mark Mirch’ is filming for customers in the Bay area. Everyone else is just laying low for now! Sound Effect Attribution “alert.wav” by danielnieto7 of Freesound.org “cell phone vibraion.wav” by MrAuralization of Freesound.org “laugh crowd 2.wav” by MrAuralizationFunWithSound of Freesound.org

V dalším díle jsme se sešli s Davidem Várou a tématem byla real time databáze Google Firestore.

Google Developer Advocate Jen Person talks with Mark Mandel and Mark Mirchandani today about developments in Firebase. Firebase is a suite of products that helps developers build apps. According to Jen, it’s equivalent to the client-side of Google Cloud. Firebase works across platforms, including Android, web, iOS and offers many growth features, setting it apart from other Google products. It helps site and app owners interact with and reach customers with services like notifications, remote configurations to optimize the app, testing, and more. Cloud Firestore has come out of beta, and it is available both through Firebase and Google Cloud Platform, making it easy for developers to move from one to the other if their needs change. Recently, the Firebase team has been working to refine their products based on user feedback. Firebase Authentication has been upgraded with the additions of phone authentication, email link authentication, and multiple email actions. They’ve also added a generic authentication option so developers can use any provider they choose. ML Kit makes machine learning much easier for client apps or on the server. With on-device ML features, users can continue using the app without internet service. Things like face recognition can still be done quickly without a wifi connection. ML Kit is adding new features all the time, including smart reply and translation, image labeling , facial feature detection, etc. Cloud Functions for Firebase is also out of beta. It includes new features like a crash-litics trigger that can notify you if your site or app crashes and scheduled functions. An emulator is new as well, so you can test without touching your live code. Jen Person Jen is a Developer Advocate at Google. She worked with Firebase for 2.5 years prior to recently joining Google Cloud. She loves building iOS apps with Swift and planning the ideal data structures for various apps using Cloud Firestore. Jen is currently co-starring with JavaScript in a buddy cop comedy where the two don’t see eye to eye but are forced to work together, eventually forming a strong loving bond through a series of hilarious misadventures. Cool things of the week Uploading images directly to Cloud Storage using Signed URL blog Build your own event-sourced system using Cloud Spanner blog Cloud Shell on the Cloud Console app site Google Cloud networking in depth: Cloud Load Balancing deconstructed blog Interview Firebase site Firestore site Cloud Storage site Firebase Authentication site ML Kit site TensorFlow Lite site Cloud Functions for Firebase site Cloud Functions Samples site I/O 2019 Talk: Zero to App video Guide - Cloud Firestore collection group queries docs Guide - Scheduled Cloud Functions docs YouTube - #AskFirebase Playlist videos Codelab - Recognize text, facial features, and objects in images with ML Kit for Firebase: iOS site Codelab - Train and deploy on-device image classification model with AutoML Vision in ML Kit site Codelab - Recognize text, facial features, and objects in images with ML Kit for Firebase: Android site Codelab - Identify objects in images using custom machine learning models with ML Kit for Firebase site Codelab - Detect objects in images with ML Kit for Firebase: Android site Previous episodes on Firebase: GCP Podcast Episode 13: Firebase with Sara Robinson and Vikrum Nijjar podcast GCP Podcast Episode 29: The New Firebase with Abe Haskins and Doug Stevenson podcast GCP Podcast Episode 78: Firebase at I/O 2017 with James Tamplin and Andrew Lee podcast GCP Podcast Episode 97: Cloud Firestore with Dan McGrath and Alex Dufetel podcast GCP Podcast Episode 99: Cloud Functions and Firebase Hosting with David East podcast Question of the week How do I save money on my GCP resources? Where can you find us next? Mark Man will be at Tokyo Next! Watch him live code on Twitch. Mark Mirch is going on vacation!

Mark Mirchandani is our Mark this week, joining new host Michelle Casbon in a recap of their favorite things at Next! The main story this episode is Cloud Run, and Gabi and Mark met up with Steren Giannini and Ryan Gregg at Cloud Next to learn more about it. Announced at Next, Cloud Run brings serverless to containers! It offers great options and security, and the client only pays for what they use. With containers, developers can use any language, any library, any software, anything! Two versions of Cloud Run were released last week. Cloud Run is the fully managed, hosted service for running serverless containers. The second version, Cloud Run GKE, provides a lot of the same benefits, but runs the compute inside your Kubernetes container. It’s easy to move between the two if your needs change as well. Steren Giannini Steren is a Product Manager in the Google Cloud Platform serverless team. He graduated from École Centrale Lyon, France and then was CTO of a startup that created mobile and multi-device solutions. After joining Google, Steren managed Stackdriver Error Reporting, Node.js on App Engine, and Cloud Run. Ryan Gregg Ryan is a product manager at Google, working on Knative and Cloud Run. He has over 15 years experience working with developers on building and extending platforms and is passionate about great documentation and reducing developer toil. After more than a decade of working on enterprise software platforms and cloud solutions at Microsoft, he joined Google to work on Knative and building great new experiences for serverless and Kubernetes. Cool things of the week News to build on: 122+ announcements from Google Cloud Next ‘19 blog Mark’s Favorite Announcement: Network service tiers site Michelle’s Favorite Announcements: Cloud Code site Cloud SQL for Postgres now supports v11 release notes Cloud Data Fusion for visual code-free ETL pipelines site Cloud AI Platform site AutoML Natural Language site Google Voice for G Suite blog Hangouts Chat in Gmail site Kubeflow v0.5.0 release site Interview Cloud Run site Knative site Knative Docs site Firestore site App Engine site Cloud Functions site GKE site Cloud Run on GKE site Understanding cluster resource usage site Docker site Cloud Build site Gitlab site Buildpacks site Jib (Java Image Builder) site Pub/Sub site Cloud VPC site Google Cloud Next ‘19 All Sessions videos Question of the week If I want to try out Cloud Run, how do I get started? Get started with the beta version by logging in site Quicklinks site Codelab site Where can you find us next? Gabi is at PyTexas Jon and Mark Mandel are at East Coast Game Conference Michelle & Mark Mirchandani will be at Google IO in May Michelle will be at Kubecon Barcelona in May

While continuing work on the Chasms app, Randy asks Don for his two cents on an approach to solving a document datastore (firestore) schema involving a many-to-many relationship. A discussion ensues to make sure the whole approach to the project is right.

Randy has started working on the Chasms project again, and after the previous episode with David Rogers, he chose to use (and learn) Vue.js to get it started. Don and Randy discuss the various libraries being used to build the app, along with some strategies for other folks to get started with the framework.

First-time host, Aja, joins Mark today to talk Go Cloud Functions with two Google colleagues! Stewart, lead Product Manager on Google Cloud Functions, and Tyler, Developer Programs Engineer at Google, start the show by explaining the purpose of Cloud Functions. It is a severless compute product that supports many programming languages, scales automatically, and only charges for what you use. It works best as event-driven computing, in other words, when something happens, you want something else to happen in response. Cloud Functions also works well between clouds or even Google Cloud services, acting as the glue between them. Go Cloud Functions works specifically for Go. Google makes a huge effort to make Cloud Functions easy to use for all developers, so that no matter what language you’re familiar with, Cloud Functions works for you. Stewart Reichling Stewart Reichling is the lead Product Manager on Google Cloud Functions. He is a graduate of Georgia Institute of Technology and has worked across Strategy, Marketing, and Product Management at Google. Tyler Bui-Palsulich Tyler is a Developer Programs Engineer at Google. He graduated with his Master’s in Computer Science from NYU and loves detailed documentation, random trivia, and homemade bread. You can find his blog at buipalsulich.com Cool things of the week Actually cool thing of the week twitter NoSQL for the serverless age: Announcing Cloud Firestore general availability and updates blog Site Reliability Workbook now available in HTML site Building a serverless online game: Cloud Hero on Google Cloud Platform blog The tech industry is failing people with disabilities and chronic illnesses article Interview GCP Podcast Episode 34: Stackdriver monitoring with Aja Hammerly podcast GCP Podcast Episode 53: Ruby with Aja Hammerly podcast Cloud Functions site Cloud Scheduler site Firestore site Pub/Sub site Go Mod site App Engine site Open Census site GCP Podcast Episode 118: OpenCensus with Morgan McLean and JBD podcast Google Stackdriver site Launch/overview video video The Go Runtime site Cloud Functions Quickstarts site Question of the week How many ways can you run containers on GCP? Where can you find us next? Mark will be at GDC in March, Cloud NEXT, and ECG in April. Agones has a new website agones.dev! And he’s also back to Twitch streaming! Aja will be at Cloud NEXT in April.

** Summary ** Michael Dowden tells me how FlexePark build a completely serverless application with Firebase. ** Details ** Who he is, what he does. What is serverless computing, how it differs from traditional and container based computing. What Firebase is, its ecosystem ; where the business logic lives. Progressive web apps, languages you can use with Firebase. Where Firebase "lives". Why Michael chose Firebase. Storing data, real time database, cloud Firestore. Accessing other data and api's. Firebase suite of tools, authentication and authorization "oauth in 15 minutes with Firebase", using authentication by itself. Crashlytics and track.js. Configuration tools. Deploying your application, easy app rollbacks. How much it costs. Full Show Notes

Don and Randy get back from a couple weeks of trips and projects and discuss a grab-bag of subjects of things they've worked on or learned.

Don and Randy get back from a couple weeks of trips and projects and discuss a grab-bag of subjects of things they've worked on or learned.

We yell at document datastores to get off our lawns! We talk about the joys of SQL and 50-year-old relational databases we grew up with, trying to make sense of why MongoDB, Firestore, and Dynamo are necessary, and Randy's unhealthy love for Materialized Views. In addition, Lotus 1-2-3 is a database, no matter what Don says.

We yell at document datastores to get off our lawns! We talk about the joys of SQL and 50-year-old relational databases we grew up with, trying to make sense of why MongoDB, Firestore, and Dynamo are necessary, and Randy's unhealthy love for Materialized Views. In addition, Lotus 1-2-3 is a database, no matter what Don says.

We yell at document datastores to get off our lawns! We talk about the joys of SQL and 50-year-old relational databases we grew up with, trying to make sense of why MongoDB, Firestore, and Dynamo are necessary, and Randy's unhealthy love for Materialized Views. In addition, Lotus 1-2-3 is a database, no matter what Don says.

We yell at document datastores to get off our lawns! We talk about the joys of SQL and 50-year-old relational databases we grew up with, trying to make sense of why MongoDB, Firestore, and Dynamo are necessary, and Randy's unhealthy love for Materialized Views. In addition, Lotus 1-2-3 is a database, no matter what Don says.

We talk about Firebase as a new backend tool for a few projects we're working on and cover many of its features, what is weird about it, and why this seems to be a product in which Google is making a big investment. Hint: It's about the Person, er, people!

NativeScript-Vue 1.0, GraphQL, the Chopin brothers on Nuxt.js, why StoreFront chose Vue.js, 5 things learned building SaaS with Vue, and building a progressive quiz app with Vue, Vuex, and Firestore.

This week, we dive into machine learning bias and fairness from a social and technical perspective with machine learning research scientists Timnit Gebru from Microsoft and Margaret Mitchell (aka Meg, aka M.) from Google. They share with Melanie and Mark about ongoing efforts and resources to address bias and fairness including diversifying datasets, applying algorithmic techniques and expanding research team expertise and perspectives. There is not a simple solution to the challenge, and they give insights on what work in the broader community is in progress and where it is going. Timnit Gebru Timnit Gebru works in the Fairness Accountability Transparency and Ethics (FATE) group at the New York Lab. Prior to joining Microsoft Research, she was a PhD student in the Stanford Artificial Intelligence Laboratory, studying computer vision under Fei-Fei Li. Her main research interest is in data mining large-scale, publicly available images to gain sociological insight, and working on computer vision problems that arise as a result, including fine-grained image recognition, scalable annotation of images, and domain adaptation. The Economist and others have recently covered part of this work. She is currently studying how to take dataset bias into account while designing machine learning algorithms, and the ethical considerations underlying any data mining project. As a cofounder of the group Black in AI, she works to both increase diversity in the field and reduce the impact of racial bias in the data. Margaret Mitchell M. Mitchell is a Senior Research Scientist in Google's Research & Machine Intelligence group, working on artificial intelligence. Her research involves vision-language and grounded language generation, focusing on how to evolve artificial intelligence toward positive goals. Margaret's work combines machine learning, computer vision, natural language processing, social media, and insights from cognitive science. Before Google, Margaret was a founding member of Microsoft Research's “Cognition” group, focused on advancing artificial intelligence, and a researcher in Microsoft Research's Natural Language Processing group. Cool things of the week GPS/Cellular Asset Tracking using Google Cloud IoT Core, Firestore and MongooseOS blog GPUs in Kubernetes Engine now available in beta blog Announcing Spring Cloud GCP - integrating your favorite Java framework with Google Cloud blog Interview PAIR | People+AI Research Initiative site FATE | Fairness, Accountability, Transparency and Ethics in AI site Fat* Conference site & resources Joy Buolamwini site Algorithmic Justice Leaguge site ProPublica Machine Bias article AI Ethics & Society Conference site Ethics in NLP Conference site FACETS site TensorFlow Lattice repo Sample papers on bias and fairness: Gender Shades: Intersectional Accuracy Disparities in Commercial Gender Classification paper Facial Recognition is Accurate, if You're a White Guy article Mitigating Unwanted Biases with Adversarial Learning paper Improving Smiling Detection with Race and Gender Diversity paper Fairness Through Awareness paper Avoiding Discrimination through Casual Reasoning paper Man is to Computer Programmer as Woman is to Homemaker? Debiasing Word Embeddings paper Satisfying Real-world Goals with Dataset Constraints paper Axiomatic Attribution for Deep Networks paper Monotonic Calibrated Interpolated Look-Up Tables paper Equality of Opportunity in Machine Learning blog Additional links: Bill Nye Saves the World Episode 3: Machines Take Over the World (includes Margaret Mitchell) site “We're in a diversity crisis”: Black in AI's founder on what's poisoning the algorithms in our lives article Using Deep Learning and Google Street View to Estimate Demographics with Timnit Gebru TWiML & AI podcast Security and Safety in AI: Adversarial Examples, Bias and Trust with Mustapha Cisse TWiML & AI podcast How we can build AI to help humans, not hurt us TED PAIR Symposium conference Question of the week “Is there a gcp service that's cloud identity-aware proxy except for a static site that you host via cloud storage?” Answer between Mark & KF Cloud Identity-Aware Proxy site & docs Cloud Storage site & docs Hosting a Static Website on Cloud Storage site Google App Engine site & docs weasel repo Where can you find us next? Melanie will be at Fat* in New York in Feb. Mark will be at the Game Developer's Conference | GDC in March.

Поговорили о RxJava 3, JUnit 5, FireStore, обновлении дизайн гайдлайнов и о других анонсах.

In questa puntata Eugenio analizza il presente e il futuro delle Interfacce Vocali prendendo spunto dall'evento di presentazione del nuovo Google Pixel 2 che ha fatto parlare di se grazie al lancio delle cuffiette intelligenti che permettono la traduzione istantanea da e verso quasiasi lingua. Si continua dando uno sguardo a come si sta muovendo in questo campo il mondo Open Source e ai progetti più promettenti, come Common Voice di Mozilla. In chiusura una piccola riflessione extra sul nuovo Database non relazionale della suite cloud di Google ovvero Firestore.Link e Risorse-------------------Google Pixel Buds Presentation Video- https://www.youtube.com/watch?v=HRy_fOyVKRUVoice User Interface- https://arstechnica.com/gadgets/2016/11/google-home-review-a-step-forward-for-hotwords-a-step-backward-in-capability/Mozilla Common Voice- https://voice.mozilla.org/Open Source Speech & Machine Learning- https://research.mozilla.org/machine-learning/Web Speech API - W3C Draft- https://w3c.github.io/speech-api/webspeechapi.htmlGoogle Firestore- https://cloud.google.com/firestore/docs/

In questa puntata Eugenio analizza il presente e il futuro delle Interfacce Vocali prendendo spunto dall'evento di presentazione del nuovo Google Pixel 2 che ha fatto parlare di se grazie al lancio delle cuffiette intelligenti che permettono la traduzione istantanea da e verso quasiasi lingua. Si continua dando uno sguardo a come si sta muovendo in questo campo il mondo Open Source e ai progetti più promettenti, come Common Voice di Mozilla. In chiusura una piccola riflessione extra sul nuovo Database non relazionale della suite cloud di Google ovvero Firestore.Link e Risorse-------------------Google Pixel Buds Presentation Video- https://www.youtube.com/watch?v=HRy_fOyVKRUVoice User Interface- https://arstechnica.com/gadgets/2016/11/google-home-review-a-step-forward-for-hotwords-a-step-backward-in-capability/Mozilla Common Voice- https://voice.mozilla.org/Open Source Speech & Machine Learning- https://research.mozilla.org/machine-learning/Web Speech API - W3C Draft- https://w3c.github.io/speech-api/webspeechapi.htmlGoogle Firestore- https://cloud.google.com/firestore/docs/

October 9th, 2017 | This week on W3 Radio, we celebrate Hacktober, talk about releases like Shopify's Draggable JS, Google Firestore, the update to AWS Elastic Beanstalk, and hilariously mourn AOL Instant Messenger. Follow @w3_radio on Twitter.  Michael Schofield is @schoeyfield. Dave Gillhepsy is @yodasw16 Dan Sims is @danielgsims