Podcasts about api first

Emmanuel et Guillaume discutent de divers sujets liés à la programmation, notamment les systèmes de fichiers en Java, le Data Oriented Programming, les défis de JPA avec Kotlin, et les nouvelles fonctionnalités de Quarkus. Ils explorent également des sujets un peu fous comme la création de datacenters dans l'espace. Pas mal d'architecture aussi. Enregistré le 13 février 2026 Téléchargement de l'épisode LesCastCodeurs-Episode-337.mp3 ou en vidéo sur YouTube. News Langages Comment implémenter un file system en Java https://foojay.io/today/bootstrapping-a-java-file-system/ Créer un système de fichiers Java personnalisé avec NIO.2 pour des usages variés (VCS, archives, systèmes distants). Évolution Java: java.io.File (1.0) -> NIO (1.4) -> NIO.2 (1.7) pour personnalisation via FileSystem. Recommander conception préalable; API Java est orientée POSIX. Composants clés à considérer: Conception URI (scheme unique, chemin). Gestion de l'arborescence (BD, métadonnées, efficacité). Stockage binaire (emplacement, chiffrement, versions). Minimum pour démarrer (4 composants): Implémenter Path (représente fichier/répertoire). Étendre FileSystem (instance du système). Étendre FileSystemProvider (moteur, enregistré par scheme). Enregistrer FileSystemProvider via META-INF/services. Étapes suivantes: Couche BD (arborescence), opérations répertoire/fichier de base, stockage, tests. Processus long et exigeant, mais gratifiant.   Un article de brian goetz sur le futur du data oriented programming en Java https://openjdk.org/projects/amber/design-notes/beyond-records Le projet Amber de Java introduit les "carrier classes", une évolution des records qui permet plus de flexibilité tout en gardant les avantages du pattern matching et de la reconstruction Les records imposent des contraintes strictes (immutabilité, représentation exacte de l'état) qui limitent leur usage pour des classes avec état muable ou dérivé Les carrier classes permettent de déclarer une state description complète et canonique sans imposer que la représentation interne corresponde exactement à l'API publique Le modificateur "component" sur les champs permet au compilateur de dériver automatiquement les accesseurs pour les composants alignés avec la state description Les compact constructors sont généralisés aux carrier classes, générant automatiquement l'initialisation des component fields Les carrier classes supportent la déconstruction via pattern matching comme les records, rendant possible leur usage dans les instanceof et switch Les carrier interfaces permettent de définir une state description sur une interface, obligeant les implémentations à fournir les accesseurs correspondants L'extension entre carrier classes est possible, avec dérivation automatique des appels super() quand les composants parent sont subsumés par l'enfant Les records deviennent un cas particulier de carrier classes avec des contraintes supplémentaires (final, extends Record, component fields privés et finaux obligatoires) L'évolution compatible des records est améliorée en permettant l'ajout de composants en fin de liste et la déconstruction partielle par préfixe Comment éviter les pièges courants avec JPA et Kotlin - https://blog.jetbrains.com/idea/2026/01/how-to-avoid-common-pitfalls-with-jpa-and-kotlin/ JPA est une spécification Java pour la persistance objet-relationnel, mais son utilisation avec Kotlin présente des incompatibilités dues aux différences de conception des deux langages Les classes Kotlin sont finales par défaut, ce qui empêche la création de proxies par JPA pour le lazy loading et les opérations transactionnelles Le plugin kotlin-jpa génère automatiquement des constructeurs sans argument et rend les classes open, résolvant les problèmes de compatibilité Les data classes Kotlin ne sont pas adaptées aux entités JPA car elles génèrent equals/hashCode basés sur tous les champs, causant des problèmes avec les relations lazy L'utilisation de lateinit var pour les relations peut provoquer des exceptions si on accède aux propriétés avant leur initialisation par JPA Les types non-nullables Kotlin peuvent entrer en conflit avec le comportement de JPA qui initialise les entités avec des valeurs null temporaires Le backing field direct dans les getters/setters personnalisés peut contourner la logique de JPA et casser le lazy loading IntelliJ IDEA 2024.3 introduit des inspections pour détecter automatiquement ces problèmes et propose des quick-fixes L'IDE détecte les entités finales, les data classes inappropriées, les problèmes de constructeurs et l'usage incorrect de lateinit Ces nouvelles fonctionnalités aident les développeurs à éviter les bugs subtils liés à l'utilisation de JPA avec Kotlin Librairies Guide sur MapStruct @IterableMapping - https://www.baeldung.com/java-mapstruct-iterablemapping MapStruct est une bibliothèque Java pour générer automatiquement des mappers entre beans, l'annotation @IterableMapping permet de configurer finement le mapping de collections L'attribut dateFormat permet de formater automatiquement des dates lors du mapping de listes sans écrire de boucle manuelle L'attribut qualifiedByName permet de spécifier quelle méthode custom appliquer sur chaque élément de la collection à mapper Exemple d'usage : filtrer des données sensibles comme des mots de passe en mappant uniquement certains champs via une méthode dédiée L'attribut nullValueMappingStrategy permet de contrôler le comportement quand la collection source est null (retourner null ou une collection vide) L'annotation fonctionne pour tous types de collections Java (List, Set, etc.) et génère le code de boucle nécessaire Possibilité d'appliquer des formats numériques avec numberFormat pour convertir des nombres en chaînes avec un format spécifique MapStruct génère l'implémentation complète du mapper au moment de la compilation, éliminant le code boilerplate L'annotation peut être combinée avec @Named pour créer des méthodes de mapping réutilisables et nommées Le mapping des collections supporte les conversions de types complexes au-delà des simples conversions de types primitifs Accès aux fichiers Samba depuis Java avec JCIFS - https://www.baeldung.com/java-samba-jcifs JCIFS est une bibliothèque Java permettant d'accéder aux partages Samba/SMB sans monter de lecteur réseau, supportant le protocole SMB3 on pense aux galériens qui doivent se connecter aux systèmes dit legacy La configuration nécessite un contexte CIFS (CIFSContext) et des objets SmbFile pour représenter les ressources distantes L'authentification se fait via NtlmPasswordAuthenticator avec domaine, nom d'utilisateur et mot de passe La bibliothèque permet de lister les fichiers et dossiers avec listFiles() et vérifier leurs propriétés (taille, date de modification) Création de fichiers avec createNewFile() et de dossiers avec mkdir() ou mkdirs() pour créer toute une arborescence Suppression via delete() qui peut parcourir et supprimer récursivement des arborescences entières Copie de fichiers entre partages Samba avec copyTo(), mais impossibilité de copier depuis le système de fichiers local Pour copier depuis le système local, utilisation des streams SmbFileInputStream et SmbFileOutputStream Les opérations peuvent cibler différents serveurs Samba et différents partages (anonymes ou protégés par mot de passe) La bibliothèque s'intègre dans des blocs try-with-resources pour une gestion automatique des ressources Quarkus 3.31 - Support complet Java 25, nouveau packaging Maven et Panache Next - https://quarkus.io/blog/quarkus-3-31-released/ Support complet de Java 25 avec images runtime et native Nouveau packaging Maven de type quarkus avec lifecycle optimisé pour des builds plus rapides voici un article complet pour plus de detail https://quarkus.io/blog/building-large-applications/ Introduction de Panache Next, nouvelle génération avec meilleure expérience développeur et API unifiée ORM/Reactive Mise à jour vers Hibernate ORM 7.2, Reactive 3.2, Search 8.2 Support de Hibernate Spatial pour les données géospatiales Passage à Testcontainers 2 et JUnit 6 Annotations de sécurité supportées sur les repositories Jakarta Data Chiffrement des tokens OIDC pour les implémentations custom TokenStateManager Support OAuth 2.0 Pushed Authorization Requests dans l'extension OIDC Maven 3.9 maintenant requis minimum pour les projets Quarkus A2A Java SDK 1.0.0.Alpha1 - Alignement avec la spécification 1.0 du protocole Agent2Agent - https://quarkus.io/blog/a2a-java-sdk-1-0-0-alpha1/ Le SDK Java A2A implémente le protocole Agent2Agent qui permet la communication standardisée entre agents IA pour découvrir des capacités, déléguer des tâches et collaborer Passage à la version 1.0 de la spécification marque la transition d'expérimental à production-ready avec des changements cassants assumés Modernisation complète du module spec avec des Java records partout remplaçant le mix précédent de classes et records pour plus de cohérence Adoption de Protocol Buffers comme source de vérité avec des mappers MapStruct pour la conversion et Gson pour JSON-RPC Les builders utilisent maintenant des méthodes factory statiques au lieu de constructeurs publics suivant les best practices Java modernes Introduction de trois BOMs Maven pour simplifier la gestion des dépendances du SDK core, des extensions et des implémentations de référence Quarkus AgentCard évolue avec une liste supportedInterfaces remplaçant url et preferredTransport pour plus de flexibilité dans la déclaration des protocoles Support de la pagination ajouté pour ListTasks et les endpoints de configuration des notifications push avec des wrappers Result appropriés Interface A2AHttpClient pluggable permettant des implémentations HTTP personnalisées avec une implémentation Vert.x fournie Travail continu vers la conformité complète avec le TCK 1.0 en cours de développement parallèlement à la finalisation de la spécification Pourquoi Quarkus finit par "cliquer" : les 10 questions que se posent les développeurs Java - https://www.the-main-thread.com/p/quarkus-java-developers-top-questions-2025 un article qui revele et repond aux questions des gens qui ont utilisé Quarkus depuis 4-6 mois, les non noob questions Quarkus est un framework Java moderne optimisé pour le cloud qui propose des temps de démarrage ultra-rapides et une empreinte mémoire réduite Pourquoi Quarkus démarre si vite ? Le framework effectue le travail lourd au moment du build (scanning, indexation, génération de bytecode) plutôt qu'au runtime Quand utiliser le mode réactif plutôt qu'impératif ? Le réactif est pertinent pour les workloads avec haute concurrence et dominance I/O, l'impératif reste plus simple dans les autres cas Quelle est la différence entre Dev Services et Testcontainers ? Dev Services utilise Testcontainers en gérant automatiquement le cycle de vie, les ports et la configuration sans cérémonie Comment la DI de Quarkus diffère de Spring ? CDI est un standard basé sur la sécurité des types et la découverte au build-time, différent de l'approche framework de Spring Comment gérer la configuration entre environnements ? Quarkus permet de scaler depuis le développement local jusqu'à Kubernetes avec des profils, fichiers multiples et configuration externe Comment tester correctement les applications Quarkus ? @QuarkusTest démarre l'application une fois pour toute la suite de tests, changeant le modèle mental par rapport à Spring Boot Que fait vraiment Panache en coulisses ? Panache est du JPA avec des opinions fortes et des défauts propres, enveloppant Hibernate avec un style Active Record Doit-on utiliser les images natives et quand ? Les images natives brillent pour le serverless et l'edge grâce au démarrage rapide et la faible empreinte mémoire, mais tous les apps n'en bénéficient pas Comment Quarkus s'intègre avec Kubernetes ? Le framework génère automatiquement les ressources Kubernetes, gère les health checks et métriques comme s'il était nativement conçu pour cet écosystème Comment intégrer l'IA dans une application Quarkus ? LangChain4j permet d'ajouter embeddings, retrieval, guardrails et observabilité directement en Java sans passer par Python Infrastructure Les alternatives à MinIO https://rmoff.net/2026/01/14/alternatives-to-minio-for-single-node-local-s3/ MinIO a abandonné le support single-node fin 2025 pour des raisons commerciales, cassant de nombreuses démos et pipelines CI/CD qui l'utilisaient pour émuler S3 localement L'auteur cherche un remplacement simple avec image Docker, compatibilité S3, licence open source, déploiement mono-nœud facile et communauté active S3Proxy est très léger et facile à configurer, semble être l'option la plus simple mais repose sur un seul contributeur RustFS est facile à utiliser et inclut une GUI, mais c'est un projet très récent en version alpha avec une faille de sécurité majeure récente SeaweedFS existe depuis 2012 avec support S3 depuis 2018, relativement facile à configurer et dispose d'une interface web basique Zenko CloudServer remplace facilement MinIO mais la documentation et le branding (cloudserver/zenko/scality) peuvent prêter à confusion Garage nécessite une configuration complexe avec fichier TOML et conteneur d'initialisation séparé, pas un simple remplacement drop-in Apache Ozone requiert au minimum quatre nœuds pour fonctionner, beaucoup trop lourd pour un usage local simple L'auteur recommande SeaweedFS et S3Proxy comme remplaçants viables, RustFS en maybe, et élimine Garage et Ozone pour leur complexité Garage a une histoire tres associative, il vient du collectif https://deuxfleurs.fr/ qui offre un cloud distribué sans datacenter C'est certainement pas une bonne idée, les datacenters dans l'espace https://taranis.ie/datacenters-in-space-are-a-terrible-horrible-no-good-idea/ Avis d'expert (ex-NASA/Google, Dr en électronique spatiale) : Centres de données spatiaux, une "terrible" idée. Incompatibilité fondamentale : L'électronique (surtout IA/GPU) est inadaptée à l'environnement spatial. Énergie : Accès limité. Le solaire (type ISS) est insuffisant pour l'échelle de l'IA. Le nucléaire (RTG) est trop faible. Refroidissement : L'espace n'est pas "froid" ; absence de convection. Nécessite des radiateurs gigantesques (ex: 531m² pour 200kW). Radiations : Provoque erreurs (SEU, SEL) et dommages. Les GPU sont très vulnérables. Blindage lourd et inefficace. Les puces "durcies" sont très lentes. Communications : Bande passante très limitée (1Gbps radio vs 100Gbps terrestre). Le laser est tributaire des conditions atmosphériques. Conclusion : Projet extrêmement difficile, coûteux et aux performances médiocres. Data et Intelligence Artificielle Guillaume a développé un serveur MCP pour arXiv (le site de publication de papiers de recherche) en Java avec le framework Quarkus https://glaforge.dev/posts/2026/01/18/implementing-an-arxiv-mcp-server-with-quarkus-in-java/ Implémentation d'un serveur MCP (Model Context Protocol) arXiv en Java avec Quarkus. Objectif : Accéder aux publications arXiv et illustrer les fonctionnalités moins connues du protocole MCP. Mise en œuvre : Utilisation du framework Quarkus (Java) et son support MCP étendu. Assistance par Antigravity (IDE agentique) pour le développement et l'intégration de l'API arXiv. Interaction avec l'API arXiv : requêtes HTTP, format XML Atom pour les résultats, parser XML Jackson. Fonctionnalités MCP exposées : Outils (@Tool) : Recherche de publications (search_papers). Ressources (@Resource, @ResourceTemplate) : Taxonomie des catégories arXiv, métadonnées des articles (via un template d'URI). Prompts (@Prompt) : Exemples pour résumer des articles ou construire des requêtes de recherche. Configuration : Le serveur peut fonctionner en STDIO (local) ou via HTTP Streamable (local ou distant), avec une configuration simple dans des clients comme Gemini CLI. Conclusion : Quarkus simplifie la création de serveurs MCP riches en fonctionnalités, rendant les données et services "prêts pour l'IA" avec l'aide d'outils d'IA comme Antigravity. Anthropic ne mettra pas de pub dans Claude https://www.anthropic.com/news/claude-is-a-space-to-think c'est en reaction au plan non public d'OpenAi de mettre de la pub pour pousser les gens au mode payant OpenAI a besoin de cash et est probablement le plus utilisé pour gratuit au monde Anthropic annonce que Claude restera sans publicité pour préserver son rôle d'assistant conversationnel dédié au travail et à la réflexion approfondie. Les conversations avec Claude sont souvent sensibles, personnelles ou impliquent des tâches complexes d'ingénierie logicielle où les publicités seraient inappropriées. L'analyse des conversations montre qu'une part significative aborde des sujets délicats similaires à ceux évoqués avec un conseiller de confiance. Un modèle publicitaire créerait des incitations contradictoires avec le principe fondamental d'être "genuinely helpful" inscrit dans la Constitution de Claude. Les publicités introduiraient un conflit d'intérêt potentiel où les recommandations pourraient être influencées par des motivations commerciales plutôt que par l'intérêt de l'utilisateur. Le modèle économique d'Anthropic repose sur les contrats entreprise et les abonnements payants, permettant de réinvestir dans l'amélioration de Claude. Anthropic maintient l'accès gratuit avec des modèles de pointe et propose des tarifs réduits pour les ONG et l'éducation dans plus de 60 pays. Le commerce "agentique" sera supporté mais uniquement à l'initiative de l'utilisateur, jamais des annonceurs, pour préserver la confiance. Les intégrations tierces comme Figma, Asana ou Canva continueront d'être développées en gardant l'utilisateur aux commandes. Anthropic compare Claude à un cahier ou un tableau blanc : des espaces de pensée purs, sans publicité. Infinispan 16.1 est sorti https://infinispan.org/blog/2026/02/04/infinispan-16-1 déjà le nom de la release mérite une mention Le memory bounded par cache et par ensemble de cache s est pas facile à faire en Java Une nouvelle api OpenAPI AOT caché dans les images container Un serveur MCP local juste avec un fichier Java ? C'est possible avec LangChain4j et JBang https://glaforge.dev/posts/2026/02/11/zero-boilerplate-java-stdio-mcp-servers-with-langchain4j-and-jbang/ Création rapide de serveurs MCP Java sans boilerplate. MCP (Model Context Protocol): standard pour connecter les LLM à des outils et données. Le tutoriel répond au manque d'options simples pour les développeurs Java, face à une prédominance de Python/TypeScript dans l'écosystème MCP. La solution utilise: LangChain4j: qui intègre un nouveau module serveur MCP pour le protocole STDIO. JBang: permet d'exécuter des fichiers Java comme des scripts, éliminant les fichiers de build (pom.xml, Gradle). Implémentation: se fait via un seul fichier .java. JBang gère automatiquement les dépendances (//DEPS). L'annotation @Tool de LangChain4j expose les méthodes Java aux LLM. StdioMcpServerTransport gère la communication JSON-RPC via l'entrée/sortie standard (STDIO). Point crucial: Les logs doivent impérativement être redirigés vers System.err pour éviter de corrompre System.out, qui est réservé à la communication MCP (messages JSON-RPC). Facilite l'intégration locale avec des outils comme Gemini CLI, Claude Code, etc. Reciprocal Rank Fusion : un algorithme utile et souvent utilisé pour faire de la recherche hybride, pour mélanger du RAG et des recherches par mots-clé https://glaforge.dev/posts/2026/02/10/advanced-rag-understanding-reciprocal-rank-fusion-in-hybrid-search/ RAG : Qualité LLM dépend de la récupération. Recherche Hybride : Combiner vectoriel et mots-clés (BM25) est optimal. Défi : Fusionner des scores d'échelles différentes. Solution : Reciprocal Rank Fusion (RRF). RRF : Algorithme robuste qui fusionne des listes de résultats en se basant uniquement sur le rang des documents, ignorant les scores. Avantages RRF : Pas de normalisation de scores, scalable, excellente première étape de réorganisation. Architecture RAG fréquente : RRF (large sélection) + Cross-Encoder / modèle de reranking (précision fine). RAG-Fusion : Utilise un LLM pour générer plusieurs variantes de requête, puis RRF agrège tous les résultats pour renforcer le consensus et réduire les hallucinations. Implémentation : LangChain4j utilise RRF par défaut pour agréger les résultats de plusieurs retrievers. Les dernières fonctionnalités de Gemini et Nano Banana supportées dans LangChain4j https://glaforge.dev/posts/2026/02/06/latest-gemini-and-nano-banana-enhancements-in-langchain4j/ Nouveaux modèles d'images Nano Banana (Gemini 2.5/3.0) pour génération et édition (jusqu'à 4K). "Grounding" via Google Search (pour images et texte) et Google Maps (localisation, Gemini 2.5). Outil de contexte URL (Gemini 3.0) pour lecture directe de pages web. Agents multimodaux (AiServices) capables de générer des images. Configuration de la réflexion (profondeur Chain-of-Thought) pour Gemini 3.0. Métadonnées enrichies : usage des tokens et détails des sources de "grounding". Comment configurer Gemini CLI comment agent de code dans IntelliJ grâce au protocole ACP https://glaforge.dev/posts/2026/02/01/how-to-integrate-gemini-cli-with-intellij-idea-using-acp/ But : Intégrer Gemini CLI à IntelliJ IDEA via l'Agent Client Protocol (ACP). Prérequis : IntelliJ IDEA 2025.3+, Node.js (v20+), Gemini CLI. Étapes : Installer Gemini CLI (npm install -g @google/gemini-cli). Localiser l'exécutable gemini. Configurer ~/.jetbrains/acp.json (chemin exécutable, --experimental-acp, use_idea_mcp: true). Redémarrer IDEA, sélectionner "Gemini CLI" dans l'Assistant IA. Usage : Gemini interagit avec le code et exécute des commandes (contexte projet). Important : S'assurer du flag --experimental-acp dans la configuration. Outillage PipeNet, une alternative (open source aussi) à LocalTunnel, mais un plus évoluée https://pipenet.dev/ pipenet: Alternative open-source et moderne à localtunnel (client + serveur). Usages: Développement local (partage, webhooks), intégration SDK, auto-hébergement sécurisé. Fonctionnalités: Client (expose ports locaux, sous-domaines), Serveur (déploiement, domaines personnalisés, optimisé cloud mono-port). Avantages vs localtunnel: Déploiement cloud sur un seul port, support multi-domaines, TypeScript/ESM, maintenance active. Protocoles: HTTP/S, WebSocket, SSE, HTTP Streaming. Intégration: CLI ou SDK JavaScript. JSON-IO — une librairie comme Jackson ou GSON, supportant JSON5, TOON, et qui pourrait être utile pour l'utilisation du "structured output" des LLMs quand ils ne produisent pas du JSON parfait https://github.com/jdereg/json-io json-io : Librairie Java pour la sérialisation et désérialisation JSON/TOON. Gère les graphes d'objets complexes, les références cycliques et les types polymorphes. Support complet JSON5 (lecture et écriture), y compris des fonctionnalités non prises en charge par Jackson/Gson. Format TOON : Notation orientée token, optimisée pour les LLM, réduisant l'utilisation de tokens de 40 à 50% par rapport au JSON. Légère : Aucune dépendance externe (sauf java-util), taille de JAR réduite (~330K). Compatible JDK 1.8 à 24, ainsi qu'avec les environnements JPMS et OSGi. Deux modes de conversion : vers des objets Java typés (toJava()) ou vers des Map (toMaps()). Options de configuration étendues via ReadOptionsBuilder et WriteOptionsBuilder. Optimisée pour les déploiements cloud natifs et les architectures de microservices. Utiliser mailpit et testcontainer pour tester vos envois d'emails https://foojay.io/today/testing-emails-with-testcontainers-and-mailpit/ l'article montre via SpringBoot et sans. Et voici l'extension Quarkus https://quarkus.io/extensions/io.quarkiverse.mailpit/quarkus-mailpit/?tab=docs Tester l'envoi d'emails en développement est complexe car on ne peut pas utiliser de vrais serveurs SMTP Mailpit est un serveur SMTP de test qui capture les emails et propose une interface web pour les consulter Testcontainers permet de démarrer Mailpit dans un conteneur Docker pour les tests d'intégration L'article montre comment configurer une application SpringBoot pour envoyer des emails via JavaMail Un module Testcontainers dédié à Mailpit facilite son intégration dans les tests Le conteneur Mailpit expose un port SMTP (1025) et une API HTTP (8025) pour vérifier les emails reçus Les tests peuvent interroger l'API HTTP de Mailpit pour valider le contenu des emails envoyés Cette approche évite d'utiliser des mocks et teste réellement l'envoi d'emails Mailpit peut aussi servir en développement local pour visualiser les emails sans les envoyer réellement La solution fonctionne avec n'importe quel framework Java supportant JavaMail Architecture Comment scaler un système de 0 à 10 millions d'utilisateurs https://blog.algomaster.io/p/scaling-a-system-from-0-to-10-million-users Philosophie : Scalabilité incrémentale, résoudre les goulots d'étranglement sans sur-ingénierie. 0-100 utilisateurs : Serveur unique (app, DB, jobs). 100-1K : Séparer app et DB (services gérés, pooling). 1K-10K : Équilibreur de charge, multi-serveurs d'app (stateless via sessions partagées). 10K-100K : Caching, réplicas de lecture DB, CDN (réduire charge DB). 100K-500K : Auto-scaling, applications stateless (authentification JWT). 500K-10M : Sharding DB, microservices, files de messages (traitement asynchrone). 10M+ : Déploiement multi-régions, CQRS, persistance polyglotte, infra personnalisée. Principes clés : Simplicité, mesure, stateless essentiel, cache/asynchrone, sharding prudent, compromis (CAP), coût de la complexité. Patterns d'Architecture 2026 - Du Hype à la Réalité du Terrain (Part 1/2) - https://blog.ippon.fr/2026/01/30/patterns-darchitecture-2026-part-1/ L'article présente quatre patterns d'architecture logicielle pour répondre aux enjeux de scalabilité, résilience et agilité business dans les systèmes modernes Il présentent leurs raisons et leurs pièges Un bon rappel L'Event-Driven Architecture permet une communication asynchrone entre systèmes via des événements publiés et consommés, évitant le couplage direct Les bénéfices de l'EDA incluent la scalabilité indépendante des composants, la résilience face aux pannes et l'ajout facile de nouveaux cas d'usage Le pattern API-First associé à un API Gateway centralise la sécurité, le routage et l'observabilité des APIs avec un catalogue unifié Le Backend for Frontend crée des APIs spécifiques par canal (mobile, web, partenaires) pour optimiser l'expérience utilisateur CQRS sépare les modèles de lecture et d'écriture avec des bases optimisées distinctes, tandis que l'Event Sourcing stocke tous les événements plutôt que l'état actuel Le Saga Pattern gère les transactions distribuées via orchestration centralisée ou chorégraphie événementielle pour coordonner plusieurs microservices Les pièges courants incluent l'explosion d'événements granulaires, la complexité du debugging distribué, et la mauvaise gestion de la cohérence finale Les technologies phares sont Kafka pour l'event streaming, Kong pour l'API Gateway, EventStoreDB pour l'Event Sourcing et Temporal pour les Sagas Ces patterns nécessitent une maturité technique et ne sont pas adaptés aux applications CRUD simples ou aux équipes junior Patterns d'architecture 2026 : du hype à la réalité terrain part. 2 - https://blog.ippon.fr/2026/02/04/patterns-darchitecture-2026-part-2/ Deuxième partie d'un guide pratique sur les patterns d'architecture logicielle et système éprouvés pour moderniser et structurer les applications en 2026 Strangler Fig permet de migrer progressivement un système legacy en l'enveloppant petit à petit plutôt que de tout réécrire d'un coup (70% d'échec pour les big bang) Anti-Corruption Layer protège votre nouveau domaine métier des modèles externes et legacy en créant une couche de traduction entre les systèmes Service Mesh gère automatiquement la communication inter-services dans les architectures microservices (sécurité mTLS, observabilité, résilience) Architecture Hexagonale sépare le coeur métier des détails techniques via des ports et adaptateurs pour améliorer la testabilité et l'évolutivité Chaque pattern est illustré par un cas client concret avec résultats mesurables et liste des pièges à éviter lors de l'implémentation Les technologies 2026 mentionnées incluent Istio, Linkerd pour service mesh, LaunchDarkly pour feature flags, NGINX et Kong pour API gateway Tableau comparatif final aide à choisir le bon pattern selon la complexité, le scope et le use case spécifique du projet L'article insiste sur une approche pragmatique : ne pas utiliser un pattern juste parce qu'il est moderne mais parce qu'il résout un problème réel Pour les systèmes simples type CRUD ou avec peu de services, ces patterns peuvent introduire une complexité inutile qu'il faut savoir éviter Méthodologies Le rêve récurrent de remplacer voire supprimer les développeurs https://www.caimito.net/en/blog/2025/12/07/the-recurring-dream-of-replacing-developers.html Depuis 1969, chaque décennie voit une tentative de réduire le besoin de développeurs (de COBOL, UML, visual builders… à IA). Motivation : frustration des dirigeants face aux délais et coûts de développement. La complexité logicielle est intrinsèque et intellectuelle, non pas une question d'outils. Chaque vague technologique apporte de la valeur mais ne supprime pas l'expertise humaine. L'IA assiste les développeurs, améliore l'efficacité, mais ne remplace ni le jugement ni la gestion de la complexité. La demande de logiciels excède l'offre car la contrainte majeure est la réflexion nécessaire pour gérer cette complexité. Pour les dirigeants : les outils rendent-ils nos développeurs plus efficaces sur les problèmes complexes et réduisent-ils les tâches répétitives ? Le "rêve" de remplacer les développeurs, irréalisable, est un moteur d'innovation créant des outils précieux. Comment creuser des sujets à l'ère de l'IA générative. Quid du partage et la curation de ces recherches ? https://glaforge.dev/posts/2026/02/04/researching-topics-in-the-age-of-ai-rock-solid-webhooks-case-study/ Recherche initiale de l'auteur sur les webhooks en 2019, processus long et manuel. L'IA (Deep Research, Gemini, NotebookLM) facilite désormais la recherche approfondie, l'exploration de sujets et le partage des résultats. L'IA a identifié et validé des pratiques clés pour des déploiements de webhooks résilients, en grande partie les mêmes que celles trouvées précédemment par l'auteur. Génération d'artefacts par l'IA : rapport détaillé, résumé concis, illustration sketchnote, et même une présentation (slide deck). Guillaume s'interroge sur le partage public de ces rapports de recherche générés par l'IA, tout en souhaitant éviter le "AI Slop". Loi, société et organisation Le logiciel menacé par le vibe coding https://www.techbuzz.ai/articles/we-built-a-monday-com-clone-in-under-an-hour-with-ai Deux journalistes de CNBC sans expérience de code ont créé un clone fonctionnel de Monday.com en moins de 60 minutes pour 5 à 15 dollars. L'expérience valide les craintes des investisseurs qui ont provoqué une baisse de 30% des actions des entreprises SaaS. L'IA a non seulement reproduit les fonctionnalités de base mais a aussi recherché Monday.com de manière autonome pour identifier et recréer ses fonctionnalités clés. Cette technique appelée "vibe-coding" permet aux non-développeurs de construire des applications via des instructions en anglais courant. Les entreprises les plus vulnérables sont celles offrant des outils "qui se posent sur le travail" comme Atlassian, Adobe, HubSpot, Zendesk et Smartsheet. Les entreprises de cybersécurité comme CrowdStrike et Palo Alto sont considérées plus protégées grâce aux effets de réseau et aux barrières réglementaires. Les systèmes d'enregistrement comme Salesforce restent plus difficiles à répliquer en raison de leur profondeur d'intégration et de données d'entreprise. Le coût de 5 à 15 dollars par construction permet aux entreprises de prototyper plusieurs solutions personnalisées pour moins cher qu'une seule licence Monday.com. L'expérience soulève des questions sur la pérennité du marché de 5 milliards de dollars des outils de gestion de projet face à l'IA générative. Conférences En complément de l'agenda des conférences de Aurélie Vache, il y a également le site https://javaconferences.org/ (fait par Brian Vermeer) avec toutes les conférences Java à venir ! La liste des conférences provenant de Developers Conferences Agenda/List par Aurélie Vache et contributeurs : 12-13 février 2026 : Touraine Tech #26 - Tours (France) 12-13 février 2026 : World Artificial Intelligence Cannes Festival - Cannes (France) 19 février 2026 : ObservabilityCON on the Road - Paris (France) 6 mars 2026 : WordCamp Nice 2026 - Nice (France) 18 mars 2026 : Jupyter Workshops: AI in Jupyter: Building Extensible AI Capabilities for Interactive Computing - Saint-Maur-des-Fossés (France) 18-19 mars 2026 : Agile Niort 2026 - Niort (France) 20 mars 2026 : Atlantique Day 2026 - Nantes (France) 26 mars 2026 : Data Days Lille - Lille (France) 26-27 mars 2026 : SymfonyLive Paris 2026 - Paris (France) 26-27 mars 2026 : REACT PARIS - Paris (France) 27-29 mars 2026 : Shift - Nantes (France) 31 mars 2026 : ParisTestConf - Paris (France) 31 mars 2026-1 avril 2026 : FlowCon France 2026 - Paris (France) 1 avril 2026 : AWS Summit Paris - Paris (France) 2 avril 2026 : Pragma Cannes 2026 - Cannes (France) 2-3 avril 2026 : Xen Spring Meetup 2026 - Grenoble (France) 7 avril 2026 : PyTorch Conference Europe - Paris (France) 9-10 avril 2026 : Android Makers by droidcon 2026 - Paris (France) 9-11 avril 2026 : Drupalcamp Grenoble 2026 - Grenoble (France) 16-17 avril 2026 : MiXiT 2026 - Lyon (France) 17-18 avril 2026 : Faiseuses du Web 5 - Dinan (France) 22-24 avril 2026 : Devoxx France 2026 - Paris (France) 23-25 avril 2026 : Devoxx Greece - Athens (Greece) 6-7 mai 2026 : Devoxx UK 2026 - London (UK) 12 mai 2026 : Lead Innovation Day - Leadership Edition - Paris (France) 19 mai 2026 : La Product Conf Paris 2026 - Paris (France) 21-22 mai 2026 : Flupa UX Days 2026 - Paris (France) 22 mai 2026 : AFUP Day 2026 Lille - Lille (France) 22 mai 2026 : AFUP Day 2026 Paris - Paris (France) 22 mai 2026 : AFUP Day 2026 Bordeaux - Bordeaux (France) 22 mai 2026 : AFUP Day 2026 Lyon - Lyon (France) 28 mai 2026 : DevCon 27 : I.A. & Vibe Coding - Paris (France) 28 mai 2026 : Cloud Toulouse 2026 - Toulouse (France) 29 mai 2026 : NG Baguette Conf 2026 - Paris (France) 29 mai 2026 : Agile Tour Strasbourg 2026 - Strasbourg (France) 2-3 juin 2026 : Agile Tour Rennes 2026 - Rennes (France) 2-3 juin 2026 : OW2Con - Paris-Châtillon (France) 3 juin 2026 : IA–NA - La Rochelle (France) 5 juin 2026 : TechReady - Nantes (France) 5 juin 2026 : Fork it! - Rouen - Rouen (France) 6 juin 2026 : Polycloud - Montpellier (France) 9 juin 2026 : JFTL - Montrouge (France) 9 juin 2026 : C: - Caen (France) 11-12 juin 2026 : DevQuest Niort - Niort (France) 11-12 juin 2026 : DevLille 2026 - Lille (France) 12 juin 2026 : Tech F'Est 2026 - Nancy (France) 16 juin 2026 : Mobilis In Mobile 2026 - Nantes (France) 17-19 juin 2026 : Devoxx Poland - Krakow (Poland) 17-20 juin 2026 : VivaTech - Paris (France) 18 juin 2026 : Tech'Work - Lyon (France) 22-26 juin 2026 : Galaxy Community Conference - Clermont-Ferrand (France) 24-25 juin 2026 : Agi'Lille 2026 - Lille (France) 24-26 juin 2026 : BreizhCamp 2026 - Rennes (France) 2 juillet 2026 : Azur Tech Summer 2026 - Valbonne (France) 2-3 juillet 2026 : Sunny Tech - Montpellier (France) 3 juillet 2026 : Agile Lyon 2026 - Lyon (France) 6-8 juillet 2026 : Riviera Dev - Sophia Antipolis (France) 2 août 2026 : 4th Tech Summit on Artificial Intelligence & Robotics - Paris (France) 20-22 août 2026 : 4th Tech Summit on AI & Robotics - Paris (France) & Online 4 septembre 2026 : JUG Summer Camp 2026 - La Rochelle (France) 17-18 septembre 2026 : API Platform Conference 2026 - Lille (France) 24 septembre 2026 : PlatformCon Live Day Paris 2026 - Paris (France) 1 octobre 2026 : WAX 2026 - Marseille (France) 1-2 octobre 2026 : Volcamp - Clermont-Ferrand (France) 5-9 octobre 2026 : Devoxx Belgium - Antwerp (Belgium) 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/

Join Pure Storage Technical Evangelists Don Poorman and Mike Nelson as we dive into Pure Fusion and how Pure Storage is enabling users to focus less on managing storage and more on managing their data. We start by examining the complexities of managing storage and application workloads in today's rapidly evolving IT landscape. We expose the challenges posed by legacy vendor "portfolios" which often consist of disparate products lacking unified GUIs and APIs. Learn why a fundamental shift is necessary to eliminate silos in enterprise storage, moving beyond mere federation to true integration – a unified management plane with common APIs that seamlessly operate across the entire storage ecosystem. Poorman and Nelson underscore how this integration and automation are not just valuable for traditional workloads but will be absolutely critical for the future of AI implementation, especially for inference. Our discussion pivots to Pure Storage's groundbreaking solution: Fusion. Learn what Fusion is – a powerful capability included in the latest versions of the Purity operating environment that provides an intelligent control plane for a centralized, unified management experience across an entire fleet of arrays. Our experts explain how Fusion inherently adopts Pure's API-First strategy, offering robust automation capabilities through PowerShell SDK, Ansible, and Python. They highlight how Fusion drives management, compliance, and workload configuration consistency from a single pane of glass, and how it's a vital foundation of Pure's Enterprise Data Cloud (EDC) vision. Listeners and viewers will gain invaluable insights into the tangible benefits of Fusion, including the ability to provision storage on any array from any array within the same UI, search and manage storage resources globally, and reconfigure resources without needing to access a specific array. Poorman and Nelson also explore how Fusion simplifies and standardizes workload deployments with pre-configured definitions, enabling end-to-end workload orchestration. They touch upon future enhancements like seamless interoperability across file, object, and block storage in on-site, hybrid, and cloud environments, and the exciting prospect of workload mobility. 
 Check out the new Pure Storage digital customer community to join the conversation with peers and Pure experts: 
https://purecommunity.purestorage.com/

In dieser Episode sprechen Björn Darko und Norman über eines der spannendsten Themen der neuen AI-Search-Ära: das Model Context Protocol (MCP) – ein Standard, der festlegt, wie KI-Systeme mit Tools, Websites und Datenquellen interagieren. Norman erklärt, warum Marken künftig API-First denken müssen, wie sich Brand Visibility in Promptsmessen lässt und was das alles für SEO, Content und Conversion bedeutet.Außerdem geht es um Conversation Shopping, neue Geschäftsmodelle rund um API-Abfragen und wie Marken künftig sicherstellen, dass ihre Inhalte in LLM-Antworten auftauchen – und nicht im Datenrauschen verschwinden.

В 80 выпуске подкаста Javaswag поговорили с Ильей Зоновым о роли архитектора, подходе API First и Code of Architecture 00:00 Начало 06:03 Linux и эмбедед системы 12:57 Проекты на Java 19:03 Рост 26:12 Переход в банк 30:31 PostgreSQL 34:55 Бизнес-процессы 42:13 Процесс разработки в малых и крупных компаниях 49:12 Принятие решений в команде 55:16 Ворк лайф баланс жизни на высоких грейдах 01:02:38 Подход API First 01:10:36 Кафка и сериализацией 01:14:23 Роль архитектора и Kotlin 01:17:23 Генерация клиентов 01:25:10 Книжный клуб Code of Architecture 01:33:48 Мотивация 01:40:45 Чтение книг 01:47:29 Инструменты для работы с текстом и заметками 01:55:10 Vim и Emacs 01:56:52 Ответ на предыдущее непопулярное мнение 02:01:35 Готовность к изменениям Гость https://www.linkedin.com/in/zonov/ Ссылки: ПузоТёрка Немного про Zotero и Obsidian Про Kotlin Code of Architecture Мой личный ТОП-1 разобранных книг: Ousterhout J. - A Philosophy of Software Design Курс про неЧтение Emacs и Vim Spacemacs: сборка Emacs, собирающее лучшее из миров Emacs и Vim Evil Mode: Vim внутри Emacs Ссылки на подкаст: Сайт - https://javaswag.github.io/ Телеграм - https://t.me/javaswag Youtube - https://www.youtube.com/@javaswag Linkedin - https://www.linkedin.com/in/volyihin/ X - https://x.com/javaswagpodcast

In this episode of the CPQ Podcast, we're joined by Nikhil Muralitharan, Senior Director of Product Marketing at Chargebee, to explore how modern CPQ solutions are evolving for software and digital service businesses. Nikhil shares his unique journey from software engineering to product marketing leadership—and how his career path mirrors his personal theme of "connecting the dots." We dive deep into Chargebee's API-first, modular CPQ platform, built to support hybrid sales motions like PLG and sales-assisted selling—without maintaining separate catalogs or tech stacks. With customers ranging from $3M to $150M in revenue across the UK, Europe, ANZ, and North America, Chargebee offers out-of-the-box integrations with Salesforce, HubSpot, NetSuite, Sage Intacct, and over 60 other systems. Nikhil also discusses: Their AI-generated quote summaries and vision for CPQ in an AI-native world Why sales and finance teams should operate from a shared data foundation Chargebee's approach to billing-first CPQ architecture, SOC 1/SOC 2 and ISO 27001 compliance A new guided selling experience launching later this year Their 6-stage implementation methodology and fast go-live timelines If you're looking for a CPQ solution designed for digital growth, flexible pricing models, and enterprise-grade compliance—this episode is a must-listen.

API First - это просто! Просто садимся и делаем крутой API: универсальный, изящный, дико сложный в реализации и абсолютно бесполезный для использования! А как бы так, чтобы без последних двух пунктов?Спасибо всем, кто нас слушает. Ждем Ваши комментарии.Музыка из выпуска: - https://artists.landr.com/056870627229- https://t.me/angry_programmer_screamsВесь плейлист курса "Kubernetes для DotNet разработчиков": https://www.youtube.com/playlist?list=PLbxr_aGL4q3SrrmOzzdBBsdeQ0YVR3Fc7Бесплатный открытый курс "Rust для DotNet разработчиков": https://www.youtube.com/playlist?list=PLbxr_aGL4q3S2iE00WFPNTzKAARURZW1ZShownotes: 00:00:00 Вступление00:05:00 Кто должен разрабатывать спеку API?00:18:30 Spec First vs Code First vs ...00:22:30 Когда спеки не сходятся00:24:30 Ревью спеки00:30:50 Красивая API, которая никому не нужна00:33:30 Backend 4 Frontend00:45:00 Баланс согласования00:49:25 API as a product00:57:50 Регрессия01:03:20 GraphQL, OData01:19:30 Тестирование моками01:21:05 Версионирование API01:31:30 Как рекламировать спеки, витрина API01:34:00 Open Close Principle для API01:36:00 Безопасность01:39:15 API экономикаСсылки:- https://swagger.io/resources/articles/adopting-an-api-first-approach/ : Неплохая статья- https://github.com/OpenAPITools/openapi-generator : То что заставит всех использовать спеку! Видео: https://youtube.com/live/p_KIy8rTWRs Слушайте все выпуски: https://dotnetmore.mave.digitalYouTube: https://www.youtube.com/playlist?list=PLbxr_aGL4q3R6kfpa7Q8biS11T56cNMf5Twitch: https://www.twitch.tv/dotnetmoreОбсуждайте:- Telegram: https://t.me/dotnetmore_chatСледите за новостями:– Twitter: https://twitter.com/dotnetmore– Telegram channel: https://t.me/dotnetmoreCopyright: https://creativecommons.org/licenses/by-sa/4.0/

FastLetter - Una fonte buona dalla quale aggiornarsia cura di Giorgio TavernitiN. 55 - 26 Maggio 2025Di cosa parliamo* I rilasci in USA hanno rotto* Il FURTO* La disintermediazione di tutto* Il grande reset di Internet* Il futuro delle aziende* Il futuro delle persone* Il Google I/O e il nuovo mondo in cui vivremo* SalutiPremessa: la scorsa edizione della FastLetter, Il Collasso di Internet, era solo una anticipazione di quello che avremmo visto durante il Google I/O.Chi mi segue da molto non è sorpreso di nulla. Cito la Liquidità di Google, il crollo del traffico per le informazioni, il calo dell'awareness che avverrà, il mondo API First o MCP First, gli acquisti diretti dove ad un certo punto non ci sarà più nessuno in mezzo tra l'utente e l'azienda se non Google o altri, la realtà aumentata. La salute, l'ambiente.All'evento di Google abbiamo visto veramente tutto ciò che in questi anni abbiamo trattato sia qui che nei vari nostri eventi con i nostri speaker.Parlando invece solo di Gemini lo abbiamo visto crescere sia in potenza che in espansione dell'ecosistema Google. Ricordo che all'inizio mi si diceva che ero una sorta di pazzo a pensare che Google avrebbe ripreso OpenAI. Bah, non so dove avete vissuto negli ultimi 20 anni.O cosa guardate.Certo, OpenAI non starà lì a guardare, ma come oramai è chiaro a tutti, sta succedendo ciò che vi ho mostrato nel framework della Search Journey Umana che è arrivato il momento di aggiornare e tenerci un corso su YouTube. Ovvero che più entriamo nei nuovi mondi, più la leadership diventa frammentata. Anthropic ha appena rilasciato Claude 4 che spacca.Ma l'ecosistema di Google fa paura a tutti, perché quello che può fare Google con tutto ciò che noi usiamo, non può farlo nessuno. Quello che stiamo vivendo in questo periodo è un cambiamento profondo di come abbiamo conosciuto Internet fino ad ora. È un grande reset. Prima però, mancano pochi giorni al WMF. So che incontrerò molti di voi e devo dirvi che non vedo l'ora di scambiare 4 chiacchiere. Io sarò sempre in giro!Controllate che ci sono vari tipi di biglietti, ovviamente per chi viene anche per la formazione il Full Ticket è quello giusto: https://www.wemakefuture.it/È arrivato il momendo di addentrarci in queste novità, però dobbiamo farlo con la consapevolezza che hanno molto di positivo e io sono entusiasta dell'AI e dell'innovazione, ma ci sono una serie di punti negativi che vorrei trattare prima. Perché è importante vedere tutta la torta.I RILASCI IN USA HANNO ROTTONon lo leggerete da nessuna parte. C'è un sentiment molto negativo che sta crescendo da parte di tutto il Digital nei confronti di Google al di fuori dagli Stati Uniti.Lasciamo da parte la politica, è un sentiment dovuto al continuo rilascio di applicazioni solo per quel mercato.Lo conosco molto bene perché su YouTube è più evidente e impattante. Ho montato un casino 2 anni durante un loro meeting perché con queste cose favoreggiano i Creator USA ma dicono di essere una community globale.Oggi su YouTube molte cose vengono lanciate in USA e poi anche in Korea o Brasile o India. Cosa che Google sta tentando di fare, ma non ci riesce.Durante la live c'erano ad un certo punto 75.000 spettatori in contemporanea con 22.000 mi piace. A me le dinamiche umane fanno troppo impazzire, sono lì a guardare come ci comportiamo per comprendere chi siamo.È un numero molto elevato. Giustificato comunque, in linea con i grandi annunci positivi.Ad un certo punto nel giro di 5 minuti i mi piace sono scesi a 13.000. Un botto, una roba mai vista. Sapete cosa era successo?Sunder Pichai ha detto che AI Mode sarà rilasciato per tutti solo in USA.Booooooomm!Gli USA hanno rotto. Ero in chat con Gianluca Fiorelli (lo avete letto vero il suo articolo su AI Mode?) che mi ha detto: che occhio! Potrebbe sembrare un dettaglio e sono sicuro che tanti pensano che sia ovvio, ma vi posso assicurare che un calo del genere non ha niente di ovvio.È un sentiment molto forte. Segno che c'è oramai una community globale che si sente esclusa. Si parla molto di inclusione, superficialmente per mettersi delle piccole bandierine sul petto la facciamo. Ma praticamente, nella sostanza, siamo lontani anni luce.Queste aziende sono degli scrigni bellissimi all'esterno, ma vuoti dentro. Il problema è quando lo sono anche molte delle persone che ci lavorano.IL FURTOSta avvenendo il più grande furto di conoscenza all'Umanità. Mi ricordo che due anni fa, all'AI Festival e poi al WMF, Sergio Barile (Professore Economia e Gestione delle Imprese presso Università di Roma “La Sapienza”) fece un intervento dal titolo: “La redistribuzione della ricchezza nell'era dell'intelligenza artificiale. Quale futuro?”.Questo nuovo mondo sta sfruttando la conoscenza del mondo di prima senza alcuna preoccupazione, distruggendo modelli di business molto importanti.Non parliamo di uno o due settori, parliamo di centinaia.Con l'attivazione di AI Overviews e ancora di più con AI Mode (della quale presto avremo i dati nella Search Console di Google per tracciare il traffico) Google si erge a editore. Già lo faceva prima, ma ora la scala è troppo grande.L'uso di un “motore di ricerca” in quel modo lo trasforma in un produttore di contenuti. Di contenuti ovviamente ai quali riconosce un link. Vorrei però farvi riflettere. Mettere un link ad una fonte, nell'Internet di ieri aveva un valore. E inoltre, era solo un pezzo di contenuto, con link alla fonte. Oggi si usa tutto quel contenuto e quello di altri.Non è più solo un pezzo di contenuto e un link alla fonte. Che vale sempre meno. C'è da rivedere il sistema perché si sta spostando anche la parte economica, Google usa i contenuti di tutta l'Umanità per fare molto di più di quello che faceva ieri.A breve avremo la pubblicità dentro AI Overviews e AI Mode.Che paradosso: rubando contenuti e utenti, ci guadagneranno di più. Da chi? Dalle aziende che hanno prodotto i contenuti e non hanno più visibilità; quindi la compreranno.LA DISINTERMEDIAZIONE DI TUTTOCredo che sia il punto focale.Non parliamo solo dell'editoria. Non parliamo solo dell'e-commerce. Non parliamo solo delle agenzie pubblicitarie. Vogliono disintermediare tutto.La mission di Google è stata sempre organizzare le informazioni del mondo.Ora si è aggiunta un piccola postilla, che vi dico io, perché lì non c'è.Diventare l'unico soggetto in campo tra le persone e le informazioni. Ridurre il più possibile la visibilità di chi sta in mezzo. Tagliare più pezzi possibile della catena.Perché per l'utente è tutto più facile.Ecco, voglio farvi focalizzare una cosa.Se è bene per l'utente, non è detto che sia un bene per la persona.Non è uno questione linguistica. L'utente è colui o colei che usufruisce di un bene o servizio. La persona beh…non c'è bisogno vero?Ma di sicuro, ciò che è un bene per l'utente mi fa davvero troppo strano che coincida così spesso con un bene per Google e sempre un male per altre aziende.Stiamo entrando nell'era agentica. È tutto un agente. Che sia in ricerca o in assistenza, Google diventerà per noi tutto.IL GRANDE RESET DI INTERNETNon siamo più in grado di fermarci per protestare. Siamo troppi in questo mondo, siamo frammentati. Non possiamo permettercelo.Raga, davvero.Quando Google decise di fare il rollback della funzionalità di Chrome per guadagnarci di più e far pagare alle aziende questo costo ingiusto, perché non ci siamo organizzati per spegnere Google ADS per una settimana?Sta avvenendo un grande reset. Il Collasso di Internet è l'inizio di un nuovo mondo.Le aziende che sono leader hanno visto l'opportunità economica di spremere tutte le altre che sono sotto, prenderne il valore e concretizzarlo tutto per loro.Si sta creando un nuovo mondo Economico per Internet.Per certi versi Internet tornerà alle origini. Faremo un balzo indietro nel tempo per alcune cose.La questione per noi è una: bisogna che ci togliamo rapidamente dai nostri modelli di pensiero quella Internet per iniziare a ragionare il prima possibile della nuova Internet.Niente piagnistei. È un mondo molto crudo che se ne frega.Dobbiamo cambiare rapidamente.La produzione di un contenuto non può più essere come prima. Non si può affrontare il futuro facendo quello che facevamo in passato. È già cambiato tutto. Se continuiamo a fare come abbiamo sempre fatto, almeno dovremmo avere l'onestà intellettuale di dire che avremo numeri diversi e inferiori a prima.IL FUTURO DELLE AZIENDECosa cambia? Cosa dobbiamo fare?Ci sono un paio di cose importanti. Certo bisogna essere presenti, non ci piove. Bisogna sicuramente avere visibilità e fare SEO.Ma le cose che ha scritto John Mueller nel post Top ways to ensure your content performs well in Google's AI experiences, sono così da più 10 anni:* Focus on unique, valuable content for people* Provide a great page experience* Ensure we can access your content...e via dicendo.E sono quelle che vede un uomo che lavora per Google la cui visione è limitata. Limitata alle SERP ovviamente. È un grande John, ma giustamente risponde al contesto.Infatti la cosa più importante da fare è studiare il modo più forte che abbiamo per offrire un grande servizio, fidelizzare la persona. Sì, la persona, non solo l'utente.Fare in modo che quando quei pochi utenti arriveranno ai vostri contenuti tramite un sistema di AI, gli viene la voglia n

FastLetter - Una fonte buona dalla quale aggiornarsia cura di Giorgio TavernitiN. 54 - 12 Maggio 2025Di cosa parliamo* Il Collasso di Internet* Apple darà il segnale* AI Overviews è peggio di quello che pensi* AI Max di Google: un mondo senza Keyword* L'Internet Liquida sarà API First (o MCP)* La Realtà Aumentata* SalutiPremessa: Vi ho raccontato del WMF in Silicon Valley come parte del nostro Road to WMF 2025. Ci sono delle belle novità in arrivo. Il 29 Aprile si è svolto The Script Day: un evento online e gratuito dove alcuni dei Best PPC Influencers del 2025 ci hanno raccontato le novità sulla tematica. Mentre il 20 maggio si terrà la conferenza stampa del WMF.E poi ci sono due eventi partner nel Road To! Il primo è il SusHi Tech 8-10 maggio a Tokyo. Il WMF - We Make Future ha partecipato all'evento insieme al Comune di Bologna per ridisegnare il futuro delle metropoli.Il secondo è il Montemagno Live 2025, il tour che toccherà Milano, Torino, Firenze, Bologna e Roma! La tappa di Bologna del Montemagno Tour 2025 sarà al Teatro Europauditorium il 18 Maggio alle 21:00. E io ci andrò, visto che Bologna è la nostra città!Marco Montemagno salirà sul palco con un monologo di idee, humor e provocazione per affrontare le sfide future. Ci sarà anche un bonus esclusivo per accedere a un workshop gratuito su ChatGPT.Ci vediamo lì?Qui il sito ufficiale del Tour. Qui tutto il nostro RoadShow.IL COLLASSO DI INTERNETInternet, per come l'abbiamo imparata a conoscere, collasserà.Il potere economico si concentrerà nelle mani di pochi. La produzione di informazioni testuali sarà sempre minore, controllata, fatta da persone pagate in modo specifico per questo.Le voci autorevoli diminuiranno.Il mondo video resterà un mondo a parte, ma anche qui avremo un cambiamento con molta spazzatura e sempre meno valore, da andare a ricercarsi con cura.Questo è ciò che avverrà con la scusa dell'Intelligenza Artificiale.Se Google avesse attivato AI Overviews senza che ci fosse ChatGPT ci sarebbe stata una rivolta sociale. I guadagni di Google aumenteranno. Il traffico delle query informative non era poi così importante a livello economico per Google. Ma lo era per le aziende. Che alzeranno gli investimenti per compensare.I proprietari dei siti produrranno sempre meno contenuti informativi, perché non conviene.Sia chiaro: l'Intelligenza Artificiale Generativa è uno strumento utilissimo. Ma se c'è una possibilità che le cose possano andare male, questa possibilità sarà realtà.E non perché ci sono i cattivi in giro, ma perché il mondo nel quale tutti viviamo è un mondo che ha da molti anni una direzione chiaramente economica. Questa direzione, più l'azienda diventa grande, più diventa l'unico obiettivo da perseguire.Le aziende devono guadagnare. Non ci piove su questo.Non abbiamo però trovato il modo di proteggere il valore del mondo che viene distrutto da una cosa nuova.Attenzione. Voglio essere chiaro. Può essere che non ci sia alcun modo. Ma nessuno può saperlo perché non ci abbiamo nemmeno provato. Non vorrei però che passasse il messaggio del tipo: “hey, guarda che queste cose accadono sempre. Prendi Uber ad esempio…”Non è questo il caso. Qui stiamo parlando di toccare tutta la parte di condivisione della conoscenza in senso ampio. Cosa nascerà da questa era non lo sappiamo. Se l'Umanità si impigrisse perché non ha alcuna soddisfazione nel cercare qualcosa di nuovo da poi condividere, non sappiamo cosa potrebbe accadere.Vabbè, magari è un pensiero mio.Quando è nato il Web 2.0 sembrava una cosa solo FIGHISSIMA. Il frutto sono stati i Content Creator, che hanno subito mostrato il loro aspetto positivo, prima che le piattaforme ne approfittassero spremendoli e creando ambienti sempre più tossici, veloci, superficiali. Distruggendo poi i luoghi di discussione, cambiando radicalmente il significato della parola conversazione.Conversazione:Dal lat. conversatio -onis ‘il trovarsi insieme', der. di conversari ‘trovarsi insieme'.Oggi è io contro chi non la pensa come me. Risultato? Odio ovunque.Vabbè, magari è un pensiero mio.Però sogno da sempre un mondo consapevole che ragioni insieme sulle innovazioni e sulla tutela di ciò che abbiamo. Magari non c'è soluzione. Il problema principale però è la resa cognitiva. Non parliamo nemmeno più di come si potrebbe fare diversamente. Accettiamo e basta.E le Big Tech se ne approfittano, ovviamente, di questo.Se possono guadagnare di più senza alzare polveroni, legittimate dall'innovazione o dal doversi adattare, lo fanno senza alcuna preoccupazione di distruggere le realtà che fino ad ora hanno creato quel valore. Vabbè, magari è un pensiero mio.A livello personale non sono preoccupato. Io da sempre regalo tutto quello che ho. Ma ricordo cosa è successo con i blog. C'è stata un'era fiorente, molte persone scrivevano, conveniva. Poi non c'è stato modo di renderle indipendenti. Si sono fatte assumere e hanno smesso di condividere.Spero che questa cosa non avvenga con un più grande impatto. La mia paura più grande è che il danno più grande lo subiremo noi come esseri umani. Così come abbiamo perso la voglia di parlare davvero con qualcuno, di conversare, di approfondire…non vorrei che perdessimo la capacità e la voglia di condividere.Vabbè, magari è un pensiero mio.Tipo…Wikipedia non sarebbe mai nata da questo mondo.APPLE DARÀ IL SEGNALEÈ un po' di tempo che dico di cambiare il motore di ricerca interno dei siti e di mettere il proprio ChatGPT o Gemini attraverso un sistema con i RAG.Questo per due motivi:* è un sistema migliore* si possono iniziare a studiare i comportamenti del nostro target e comprendere meglio il nuovo mondoMa nonostante i vantaggi nel farlo siamo sempre troppo lenti. Ci sono però una serie di notizie che riguardano Apple che magari aprono un po' la mente: aldilà del cambio di naming da Search ADS a Apple ADS, quelli di Cupertino hanno fatto sapere che stanno parlando con Anthropic, OpenAI e Perplexity perché vorrebbero integrare la ricerca AI al posto della ricerca classica.Il tutto nel contesto del processo che vede sotto accusa l'accordo Apple-Google come motore di ricerca. Eddy Cue (Senior Vice President Services di Apple) ha detto che è vero che la ricerca AI ha una qualità peggiore, ma che le ricerche tramite Google sono calate.Google ha dovuto fare un comunicato stampa per smentire questo calo, affermando il contrario. Su Search Engine Land entrano nei dettagli di questa diatriba.Pensate a questa cosa: per anni si è pensato che Apple dovesse avere un suo motore di ricerca, oggi invece potrebbe fare un accordo per un modello ibrido e poi costruirselo più facilmente.Di sicuro c'è una strada importante: Apple sta pensando di sostituire il suo sistema interno di ricerca. È un segnale molto forte.Poi magari continuerà a portare avanti il suo accordo con Google e sostituirà Search con AI Mode, offrendo anche le alternative. Ma la strada è spianata: l'esperienza di ricerca sta cambiando radicalmente.Di sicuro su Google avremo l'AI Mode come default. Su questo tema vi consiglio il grande articolo di Gianluca Fiorelli: Why AI Mode will replace traditional search as Google's default interface.Troverete un sacco di spunti. Alcune cose le conoscete già perché io e Gianluca ci confrontiamo spesso e abbiamo una visione simile. Dal Search Journey a Discover in home.Altre invece sono nuove e di approfondimento anche per me.AI OVERVIEWS È PEGGIO DI QUELLO CHE PENSIQualche mese fa scrivevo che il calo di traffico dovuto ad AI Overviews avrebbe sicuramente portato un traffico più vicino alla conversione, ma che comunque avremmo perso un quantitativo di utenti importante. E suggerivo di salvare il tutto con Big Query.Sto leggendo in giro che questi utenti che stiamo perdendo sono traffico non molto utile, perché vogliono solo informazioni.Purtroppo non è così.L'AI Overviews non si attiva solo per le query informative semplici, ma anche per quelle complesse, dove la risposta la offrono e l'hanno sempre offerta i siti.Il problema principale riguarda però il fatto che questo traffico molto importante è da considerare come Awareness. Certo, per alcuni progetti il problema è principalmente economico. Un sistema basato sulle pageviews è destinato a chiudere. Per le aziende invece, significa perdere una grande fetta di Awareness. E a volte anche dei passi successivi del Customer Journey. È vero che le aziende dovranno produrre più contenuti e aumentare la quantità di volte che sono pertinenti. È vero che bisogna creare dei contenuti molto approfonditi.Ma la questione va focalizzata. Purtroppo ci perdiamo sempre in quello che accade oggi senza fermarci a riflettere. È Awareness molte volte.E per compensare questo traffico non si può pensare di fare un piano solo per entrare dentro AI Overviews, perché il quantitativo di persone che poi clicca è troppo basso.La parte di Awareness va potenziata andando a trasformare i contenuti informativi

On today's sponsored episode, Editor in Chief Sarah Wheeler talks with Erin Wester, chief product officer at Optimal Blue, about AI, API-first technology and how Optimal Blue is constantly evolving to serve the needs of lenders. Related to this episode: Optimal Blue ⁠HousingWire | YouTube⁠ More info about HousingWire⁠ Enjoy the episode! The HousingWire Daily podcast brings the full picture of the most compelling stories in the housing market reported across HousingWire. Each morning, listen to editor in chief Sarah Wheeler talk to leading industry voices and get a deeper look behind the scenes of the top mortgage and real estate stories. Hosted and produced by the HousingWire Content Studio. Learn more about your ad choices. Visit megaphone.fm/adchoices

In this episode, Derric Gilling sits down with David Biesack, Chief API Officer at Apiture, to discuss building an API-first, customer-centric digital banking platform from the ground up. David shares the origin story of Apiture, a joint venture born from a vision of open banking, and how his team embedded API design and governance into every layer of the product. From establishing API University to codifying internal tooling and style guides, David explains how they've scaled API excellence across product and engineering teams. They explore the critical role of collaboration between product managers, architects, and API designers, emphasizing use-case-driven development, robust internal tooling, and strict security validation. David also talks about empowering partners through a tailored developer portal, balancing compliance with usability, and the cautious optimism around using generative AI in API workflows. Whether you're managing API platforms or designing developer experiences, this episode offers a wealth of insights into building secure, scalable APIs that actually solve real-world problems.

Flexibility and integration have become the new currency in financial services. In this deeply insightful conversation with Renaud from Basikon, we unpack how modern lending and leasing technology is fundamentally reshaping financial operations.Founded by industry veterans who witnessed the limitations of legacy systems firsthand, Basikon delivers a refreshingly different approach to banking technology. What makes their platform revolutionary isn't just cutting-edge tech—their adaptability philosophy. They're helping financial institutions break free from operational rigidity through embedded workflows and an API-first architecture while maintaining regulatory compliance.Renaud shares fascinating contrasts between implementing for greenfield startups versus established incumbents. While startups benefit from rapid deployment of standardized processes, the challenge with established players lies more in change management—convincing them to let go of non-differentiated processes that add unnecessary complexity. The guiding mantra? "Keep it stupidly simple."The conversation expands into broader trends reshaping finance: embedded finance blurring traditional boundaries, AI transforming credit decisioning, and the inevitable shift toward real-time lending. Perhaps most provocatively, Renaud challenges the notion that complex products like mortgages can't be streamlined, suggesting that decision processes could be drastically accelerated across all financial services.Whether you're a fintech entrepreneur, banking executive, or technology enthusiast, this episode offers valuable insights into how API-first, flexible architectures are creating the foundation for tomorrow's financial ecosystem. Visit their website at basikon.io to learn how modular, adaptive systems might revolutionize your financial operations.Thank you for tuning into our podcast about global trends in the FinTech industry.Check out our podcast channel.Learn more about The Connector. Follow us on LinkedIn.CheersKoen Vanderhoydonkkoen.vanderhoydonk@jointheconnector.com#FinTech #RegTech #Scaleup #WealthTech

Want to build your own model or check out our expert models?  The Rabbit Hole is less than a dollar a day to use.  You can build, share, and download unlimited models!Try it today.  Get 10% just for reading this YouTube description using promo code YOUTUBER   https://bit.ly/3ZTj1Z3Follow us on Twitter: https://x.com/BetspertsGolfFollow us on Bluesky: https://bsky.app/profile/betspertsgolf.bsky.socialFollow us on Instagram: https://www.instagram.com/betspertsgolfig/

Daniela Binatti of Pismo joins Nick to discuss Overcoming the Odds: Pismo's Journey to Build API-First Banking, Fixing Finance's Broken Core, and the Future of Payments. In this episode we cover: Challenges in Banking and Pismo's Solution Target Market and Client Base Overcoming Objections and Sales Cycles Innovation and Cultural Transformation Trends and Opportunities in Banking Geographic Challenges and Market Expansion Future Opportunities and Blockchain Founding and Building Pismo Building in the Brazilian Ecosystem Culture and Employee Support Guest Links: Daniela's LinkedIn Daniela's X Pismo's LinkedIn Pismo's Website Pismo's X The host of The Full Ratchet is Nick Moran of New Stack Ventures, a venture capital firm committed to investing in founders outside of the Bay Area. Want to keep up to date with The Full Ratchet? Follow us on social. You can learn more about New Stack Ventures by visiting our LinkedIn and Twitter. Are you a founder looking for your next investor? Visit our free tool VC-Rank and we'll send a list of potential investors right to your inbox!

Empower Your SaaS Growth with Maesn Maesn's solution accelerates the growth of SaaS companies by simplifying the complexities of integrating with your customers' ERP and accounting systems. Our mission is to empower your business to focus on what matters most: driving growth and enhancing customer satisfaction. With our innovative API solution, you can effortlessly sync your SaaS data across multiple platforms, freeing up your engineering resources and allowing you to scale faster than ever before.

In today's jam-packed episode, they dive deep into the world of API design, logging best practices, and effective configuration management. Our esteemed guests, Michael Dawson, James Snell, Matteo Collina, and Natalia Venditto, bring their extensive expertise to the table, discussing the nuances between GraphQL and REST/Open API, the merits of API First vs. Code First approaches, and the impacts of global states in Node.js applications.You'll hear insights on how to maintain effective API contracts, avoid common pitfalls in software development, and implement robust error handling and logging mechanisms. Additionally, the episode covers practical advice on optimizing large-scale ecosystems with tools like Pino and managing dependencies thoughtfully to avoid technical debt.They also touch on the personal side of development, with James Snell emphasizing the importance of well-being by taking regular breaks. Charles Max Wood shares his recent experience at a board game convention and recommends the TV show "Reacher" for some downtime entertainment.So, sit back and enjoy this enlightening conversation that spans across technical deep dives and light-hearted discussions, offering valuable takeaways for developers at all levels.SocialsLinkedIn: James SnellLinkedIn: Michael DawsonLinkedIn: Matteo CollinaLinkedIn: Natalia VendittoPicksCharles - Gnome Hollow | Board GameCharles - Reacher (TV Series 2022Michael - MakerWorld: Download Free 3D Printing Models Become a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Get ready for a fascinating journey into the world of CPQ! This episode features Rick Huebner, the founder and CEO of VISTECH. Buckle up as Rick dives deep into his software development experience that began way back in the early 80s. But that's not all! We'll also explore: The VISTECH CPQ story: Discover how their CPQ adventure started in 2019 and how they're transforming an acquired solution into something truly innovative. No-code customization explained: Demystify what Rick means by "no-code customization" and see how it can empower your CPQ experience. SolSuite's latest and greatest: Stay ahead of the curve with insights into the newest update for SolSuite, VISTECH's CPQ solution. AI in CPQ: The future is here: Explore how VISTECH is integrating AI features into CPQ, what they're currently working on, and what's on the horizon. Building a best-in-class solution: Dive into VISTECH's approach to CPQ with their API-first, headless, and composable architecture. And that's just the tip of the iceberg! This episode is packed with valuable insights you won't want to miss. So, tune in and get ready to take your CPQ knowledge to the next level! website https://www.vistech.com/ Linkedin https://www.linkedin.com/in/rickhuebner/ Phone  860.251.8003

Eyal Solomon, CEO and co-founder of Lunar.dev, joins SE Radio's Kanchan Shringi for a discussion on tooling for API consumption management. The episode starts by examining why API consumption management is an increasingly important topic, and how existing tooling on the provider side can be inadequate for client-side issues. Eyal talks in detail about issues that are unique to API consumers, before taking a deep dive into the evolution of middleware built by teams and companies to address these issues and the gaps. Finally they consider how Lunar.dev seeks to solve these issues, as well as Eyal's vision of lunar.dev as a open source platform. This episode is sponsored by WorkOS.

Mohamed Abdel-Kader, Chief Innovation Officer at USAID and Alexis Bonnell, Former Chief Innovation Officer at USAID, discussed the impact of AI and other machine learning tools. They explored the balance between the risks and rewards associated with these tools, reaching a consensus that AI can revolutionize USAID's impact when appropriately developed and utilized. The discussion emphasized the importance of developing AI to benefit all countries where USAID is active, not just English-speaking nations. Recognizing the rapid advancement of machine learning, the speakers stressed the need for precision and thoughtfulness in posing questions to AI, given its evolving nature. They also addressed issues of localization, pointing out the challenges when native languages are overlooked or when communities lack access to computers. Mike highlighted upcoming events for those interested in collaborating with USAID. On February 15th, SID-US will host its annual career fair, followed by the annual conference on April 26th in Washington, DC. He expressed his belief that this conference is a must-attend event of the year. IN THIS EPISODE: [01:53] Mike Shanley introduces today's guests and shares their backgrounds. [02:53] Mohamed describes his role at USAID as Chief Innovation Officer and talks about how technology is advancing with the advent of machine learning tools. [6:30] Mohamed touches on some of the early-use cases that he's seen of AI applications or other technologies. [12:47] Mohamed reflects on the potential risks AI presents and whether the good outweighs the bad.  [17:04] Alexis comments that we are navigating at a different rate of change in technology; therefore, we need to be intentional about how we use AI, and she provides an example of an experiment she led.  [26:08] Mohamed discusses the ethical development of AI, strengthening policies and systems that govern AI and accessing computing power in parts of the world where it's cost-prohibitive.  [31:38] Alexis discusses how the cultures and identities of different countries impact how you work with them. She describes a sector who asked themselves if they have been as innovative as they think they have been and how AI revealed a surprising result to their question. [38:42] Mohamad discusses the significance of localization in AI, emphasizing the interconnected nature of our world and the necessity of incorporating it into our AI tools. He notes that numerous countries are enthusiastic about AI, viewing it as a tool to propel their advancement. [46:00] Alexis says that there's a gold mine for all of the entities to bring unique applications to USAID, suggesting you can recycle or reuse proposals.  [52:34] The panelists leave advice to the listeners.  KEY TAKEAWAYS: Led by Mohamed Abdel-Kader, USAID's Innovation, Technology, and Research Hub, formerly known as the Global Development Lab, team is behind cutting edge tech development and approaches within the digital space. USAID strives to reach more people through innovative and cost effective approaches from cybersecurity, to emerging technologies like artificial intelligence, digital finance, digital inclusion, and digital literacy. AI is an extremely powerful tool that is evolving and changing daily. With this, comes the risk that a lot of people will be left behind. But there's also tremendous opportunity in the AI space. USAID actively works to intentionally shape this technology to be useful for everyone, while exploring the practicalities of how they might achieve this goal.  USAID plays a unique role in fostering the ethical development of AI and other tools through various approaches. Mohamed and his team focus on utilizing the powerful tool of AI responsibly in environments where there are a lot of vulnerable people. USAID takes an ecosystem approach to discern how AI as a tool sits in the broader digital ecosystem within USAID's partner countries and how USAID can support the responsible use of AI and continue to shape that global agenda. They do this by strengthening the underlying policies and systems and civil society environment that shapes how AI is designed, developed, and deployed in partner countries, including the quality and representative data sets that are used to build these particular tools. RESOURCES: Aid Market Podcast Aid Market Podcast YouTube Mike Shanley - LinkedIn Mohamed Abdel-Kader LinkedIn Alexis Bonnell LinkedIn Co-host Society for International Development-US USAID_Digital Twitter USAID Twitter USAID Innovates Twitter BIOGRAPHIES: Mohamed Abdel-Kader serves as USAID's Chief Innovation Officer and Executive Director of the Innovation, Technology, and Research Hub. In these roles, he oversees various Agency mechanisms to promote the application of innovation, technology, and research for greater aid effectiveness within USAID and the inter-agency, and with our partners in the international development community, private sector, and civil society. Prior to USAID, Mohamed advised companies, leading NGOs and multilateral organizations, foundations and educational institutions, and government agencies in addressing their most pressing challenges. He served in the Obama administration as Deputy Assistant Secretary for International and Foreign Language Education in the U.S. Department of Education and later led the Aspen Institute's Stevens Initiative, an international ed-tech program. He has also served several postsecondary institutions in international strategy and major gift fundraising roles. A speaker of fluent Arabic and basic Spanish, Mohamed is a Truman National Security Fellow, an Eisenhower Fellow, and the author of a children's book about stereotypes. He holds a Bachelor's degree from Clemson University, a Master's degree in Higher Education from Vanderbilt University, and an MBA from Georgetown University's McDonough School of Business. He is also a trustee of the Longview Foundation for International Education & World Affairs.   Alexis Bonnell is the Chief Information Officer and Director of the Digital Capabilities Directorate of the Air Force Research Laboratory, the primary scientific research and development center for the Department of the Air Force. She is responsible for developing and executing the AFRL Information Technology strategy, leading the strategic development of highly advanced next generation technologies and platforms for AFRL. Her focus includes catalyzing the discovery, development, and integration of warfighting technologies for air, space, and cyberspace forces via digital capabilities, IT infrastructure and technological innovation across the lab's operations and culture. She was one of the first employees of the Internet Trade Association, contributing to the early development and growth of the digital landscape. She has served in challenging environments, including warzones with the United Nations to support over $1B of critical DOD operations in Afghanistan, Iraq and many other operational theaters. She has contributed to dual-use technology and innovation culture across the DOD Innovation community including: AFWERX, AFRL, Kessel Run, NavalX, Marine Innovation Unit, Army Futures Command, DIU, Army Software Factory, DARPA and more. Prior to her current position, she was the Emerging Technology Evangelist at Google, driving the use of emerging technologies such as Artificial Intelligence, cyber security/zero trust, API First, Big Data, Cloud Computing, and others to drive efficiency and innovation within government organizations, including tackling digital transformation in defense, healthcare, education, COVID response, natural disasters, supply chain, system/process modernization, hybrid workforce and more. Bonnell co-founded the Global Development Lab, the premier innovation lab of the United States Agency for International Development (USAID), leveraging Global Allied Nation partnerships in Science, Technology, and Innovation, reviewing over 25,000 game changing innovations and technologies, funding 1,200 of them. She served as USAID's Chief Innovation Officer, receiving the first 10/10 for innovation in the Results For America Rankings. She was named in the Fed 100 in 2020. She also assisted with major platform and technology transitions, drove hybrid work adoption, countering malign nation initiatives and global cyber security programming.

Key Points:The rush to categorize all of our tooling in data has caused many issues - we will see a big shake-up coming in the future much like happened in application development tooling.So much of data people's time is spent on things that don't add value themselves, it's work that should be automated. We need to fix that so the data work is about delivering value.We can learn a lot from virtualization but data virtualization is not where things should go in general.Containerization is merely an implementation detail. Much like software developers don't really care much about process containers, the same will happen in data product containers - it's all about the experience and containers significantly improve the experience.The pendulum swung towards decoupled data tech instead of monolithic offerings with 'The Modern Data Stack' but most of the technologies were not that easy to stitch together. Going forward, we want to keep the decoupled strategy but we need a better way to integrate - APIs is how it worked in software, why not in data? Sponsored by NextData, Zhamak's company that is helping ease data product creation.For more great content from Zhamak, check out her book on data mesh, a book she collaborated on, her LinkedIn, and her Twitter. Sign up for Data Mesh Understanding's free roundtable and introduction programs here: https://landing.datameshunderstanding.com/Please Rate and Review us on your podcast app of choice!If you want to be a guest or give feedback (suggestions for topics, comments, etc.), please see hereData Mesh Radio episode list and links to all available episode transcripts here.Provided as a free resource by Data Mesh Understanding / Scott Hirleman. Get in touch with Scott on LinkedIn if you want to chat data mesh.If you want to learn more and/or join the Data Mesh Learning Community, see here: https://datameshlearning.com/community/All music used this episode was found on PixaBay and was created by (including slight edits by Scott Hirleman): Lesfm, MondayHopes, SergeQuadrado, ItsWatR, Lexin_Music, and/or

Pour l'épisode de cette semaine, je reçois Julien Le Coupanec, fondateur de The Companies API. The Companies API c'est une solution permettant de récupérer des données d'entreprise pour faire de la prospection, enrichir votre CRM,.. Au cours de cet épisode, Julien nous a expliqué son parcours, comment il en était arrivé à lancer The Companies API, son pivot d'une app à une “API first”, de l'équilibre “produit” vs “marketing” quand on est un Indie Hacker. Nous avons aussi un peu parlé de technique et des enjeux de migration auxquels il a été récemment confronté. Vous pouvez suivre Julien sur LinkedIn. Bonne écoute ! _____ Mentionnés pendant l'épisode : Malt (ex Hopwork) Brevo (ex Send-in-blue) Veed.io (landing page spécialisée par use-case) Stripe OpenAPI Swagger Bump.sh Dribbble ThinkerView L'épisode de SaaS Connection avec Moritz Dausinger de Refiner Lean Analytics - Alistair Croll et Benjamin Yoskovitz From Impossible to Inevitable - Aaron Ross et Jason Lemkin The SaaS Playbook - Rob Walling Les conférences MicroConf _____ Pour soutenir SaaS Connection en 1 minute⏱ (et 2 secondes) : Abonnez-vous à SaaS Connection sur votre plateforme préférée pour ne rater aucun épisode

InformData is an 'API First' company. What does that mean? Wait... what even is an API? Greg Jones, our Chief Product Officer, joins me in this episode to dig into the basics of an API and data integration, why this technology is important in the background screening industry, and how InformData's API benefits CRAs.

This week on the API Intersection podcast, we interviewed Alex Chernyak, CEO of ZAPTEST, a software organization specializing in software automation testing and merging automation with RPA. ZAPTEST also automates business processes, using APIs and UI steps to overcome specific customer integration challenges.We chatted with Alex to learn more about automation testing, the role APIs play in that, and why an API-first approach is essential to better performance at ZAPTEST._____To subscribe to the podcast, visit https://stoplight.io/podcast--- API Intersection Podcast listeners are invited to sign up for Stoplight and save up to $650! Use code INTERSECTION10 to get 10% off a new subscription to Stoplight Platform Starter or Pro.Offer good for annual or monthly payment option for first-time subscribers. 10% off an annual plan ($650 savings for Pro and $94.80 for Starter) or 10% off your first month ($9.99 for Starter and $39 for Pro).

There are about as many "first" approaches to software as there are colors in the rainbow. Front-end first, serverless-first, API-first, test-first, the list goes on and on. Andres Moreno and I cover what it means to be API-first, clarify the definition of serverless-first, and discuss how he managed to build a development process that follows both patterns. Learn about the tooling that helps this highly-optimized team push out high-quality code faster than ever without getting lost in the weeds. About Andres Andres is a lead software engineer at Tyler Technologies with over a decade of experience. He's a skilled AWS serverless engineer and has spent time as an AWS Community Builder. Andres writes in-depth technical content on his blog where he shares his insights on CI/CD, cloud security, and JavaScript. Links Twitter - https://twitter.com/andmoredev LinkedIn -https://www.linkedin.com/in/andmoredev Personal blog - https://www.andmore.dev Postman - https://postman.com Open API Specification - https://www.openapis.org --- Send in a voice message: https://podcasters.spotify.com/pod/show/readysetcloud/message Support this podcast: https://podcasters.spotify.com/pod/show/readysetcloud/support

In this episode of the Breaking Changes podcast, Kin Lane is joined by Rickey McCoy, Senior Development Manager at Riot Games, to discuss how the video game developer is using their API to develop new characters and their award-winning television show on Netflix, embracing API-first when it comes to developing a deep understanding of their consumers.

(Part 1/8): You may have heard about API-First strategies. What does it mean to build your APIs first? What is an API Gateway?  At Snowpal, we are close enough to launching our first API so other technology businesses can consume it, thereby focusing more on their core business problems and delivering quicker.   In this API Gateway series, I'll be sharing a lot of those details. If you have an interest in doing something similar, I hope it benefits you.   #snowpal #projectmanagement Manage personal and professional projects on https://snowpal.com.

During the course of this season of the All About APIs podcast, we have been exploring the different aspects of API-led product growth - why it's important, how to approach it and the key challenges to achieving it. In this episode, we speak with Deepa Goyal, Product Strategist at Postman about metrics that matter in an endeavour to define, analyse and optimise what success looks like for different stakeholders within an API-first business. We look at 3 different types of metrics - business, infrastructure and user metrics, and establish the need for a common language for collaboration to bring together the business, product and engineering teams. Deepa Goyal resides in San Francisco, California and brings a wealth of experience in data science and APIs. She has been part of product development at startups as well as Fortune500s, PayPal and Twilio. She is a champion for applying product thinking to building API products, women in tech and data-driven decision-making. Join us in celebrating the upcoming publishing of her first book, API Analytics for Product Managers, available in February of 2023. If you enjoyed the episode, please rate and subscribe!

Kin Lane (@kinlane, Founder API Evangelist  & Chief Evangelist @Postman) talks about getting started with APIs. We also cover API lifecycle & governance.SHOW: 670CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotwCHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS"SHOW SPONSORS:Granulate, an Intel company - Autonomous, continuous, workload optimizationgProfiler from Granulate - Reduce Kubernetes costs by up to 60%CDN77 - Content Delivery Network Optimized for Video85% of users stop watching a video because of stalling and rebuffering. Rely on CDN77 to deliver a seamless online experience to your audience. Ask for a free trial with no duration or traffic limits.JetBrains Datalore: Collaborative data science for your whole organizationEnhance your core data team's performance by bringing real-time collaboration, a first-class coding experience, and no-code automations to Jupyter notebooks. Make conversation with business stakeholders easy through the sharing of interactive data apps. Start for free at datalore.team/cloudcast.SHOW NOTES:API Evangelist websiteBreaking Changes PodcastPostman websiteTopic 1 - Kin, for those out there that maybe haven't heard of you, give everyone a brief introduction.Topic 2 - You've been doing APIs since before APIs were cool. You started the API evangelist site 12 years ago. Tell us about that journey. As a follow up, how do new folks get started?Topic 3 - As you mention on the API Evangelist website. APIs are more than technology. The headline of the website is “making sense of the technology, business, and politics of APIs since 2010. What do you mean by that? How does business and politics come into play with APIs.Topic 4 - We often hear the phrases Cloud First and API First thrown around. What does that mean? Also, help everyone out with terminology differences between say Open API, GraphQL, etc.Topic 5 - Follow up to API First question. Let's talk about API First companies, we often hear about the poster children: Twilio, Stripe, and SendGrid for instance. Are they still valid examples? Who are the latest examples and use cases? Topic 6 - Let's talk about API Lifecycles and dig into Postman a bit. We've reached a point in our industry that APIs are treated like a product, have PM and full development teams, and just like any product or service a company would produce. What are the typical steps you see and how does Postman help with this journey? Topic 7 - You are active in API research, publishing of articles and research around APIs. I noticed you have been digging into Government APIs recently for instance. Where is your focus these days and what are the latest emerging trends you are seeing?FEEDBACK?Email: show at the cloudcast dot netTwitter: @thecloudcastnet

In this episode of the Breaking Changes podcast, Kin Lane is joined by Mamta Suri, Former Senior Manager Software Development for Time Tracking at Workday, talking about the importance of diversity and business alignment across API operations, but halfway through our interview Mamta turned the tables and began interviewing Kin Lane about what he has learned about APIs doing the show.

Welcome to episode 3 of All About APIs, where we talk to seasoned Executive API Consultant, James Higginbotham, about establishing, growing and maturing API-first programs and deploying an API-first architecture. James is an API consultant with experience in architecting, building, and deploying APIs and cloud-native architectures. As an API consultant, he enjoys helping businesses balance great API design and product needs. He also creates and delivers API and cloud-native architecture training with the goal of equipping cross-functional teams to integrate their talents toward building first-class APIs for their product or enterprise systems. Follow James on Twitter. Visit his website. Check out his latest book, Principles of Web API Design: Delivering Value with APIs and Microservices and purchase it on Amazon

In this episode of Breaking Changes, Kin Lane sits down with Juha Stenberg, the CEO of eMabler, to talk about how being API-first is helping to define not only the future of the electric automobile charging industry, but also the wider energy and payment industries, and how relying on APIs will help iteratively define the future of these industries amidst a great deal of volatility and disruption.

The ecommerce platform landscape is quite cluttered. In this interview, Paul chats with with Chord's Co-founder and CEO Bryan Mahoney, looking at where Chord sits in the ecommerce platform market and whats its key selling points are for merchants. Bryan's background is running an design and development agency helping early stage DTC brands like Glossier grow their ecommerce presence. Bryan shares his expertise and discusses how their data-first approach provides a point of difference to older platforms that have only recently evolved into providing robust APIs.

In this Breaking Changes episode, Postman Chief Evangelist Kin Lane welcomes Fara Jituboh, Co-Founder and CEO/CTO of Okra. Okra is Africa's first API fintech super-connector and aims to democratize finance as a service through technology. Fara shares her compelling view of why API-first is how the next generation of applications will be delivered in Africa.

In this Breaking Changes episode, Postman Chief Evangelist Kin Lane is joined by ngrok CTO Peter Shafton. Peter shares his view of the API economy from his experience leading architecture for Twilio over the last decade.

In this Breaking Changes, Postman Chief Evangelist Kin Lane welcomes Chander Shivdasani, Vice President at Marcus by Goldman Sachs for a conversation about the contracts-first approach to API infrastructure at Goldman Sachs.

(Part 1/2) What is a Mobile First Strategy? How different is it from an API First Strategy? Are there other alternatives? What's the best way to go? #projectmanagement #snowpal Mobile First, or API First? Plan it on https://snowpal.com.

(Part 2/2) What is a Mobile First Strategy? How different is it from an API First Strategy? Are there other alternatives? What's the best way to go? #projectmanagement #snowpal Mobile First, or API First? Plan it on https://snowpal.com.

In this Breaking Changes, Postman Chief Evangelist Kin Lane welcomes Aleksei Akimov formerly of Adyen to talk about the road to becoming API-first in the payments industry by applying a well-known API lifecycle across teams.

Enterprises across the globe are struggling to innovate because their data and applications are siloed, disconnected, and not easily accessible. Today, Google Cloud is announcing the general availability of Apigee Integration, a solution that helps enterprises easily connect their existing data and applications and surface them as easily accessible APIs that can power new experiences. Data and applications are enablers of digital experiences. However, for many enterprises across the world, data and applications are siloed, buried inside various on-premises and cloud servers, and cannot be easily accessed by internal developers or partners. This challenge slows down efforts of digital transformation by extending development timelines from weeks to months. Integration and API management solutions address this challenge by enabling developers to seamlessly connect their data and applications, and surface them as easily consumable APIs. In this episode, Chris Hood sits down with Scott Haaland and Andrew Pickelsimer to better understand how an API-first approach to integration can help deliver on consumer expectations and generate business value.

What makes an Estonian fintech cooler than a Californian one? Probably not just the weather! It's time to get to know Tuum and its mission to help banks stay in the current digital age. Listen in on this episode with Ove Kreison, CTO and Co-founder of Tuum—formerly known as Modularbank—about what characterizes a state-of-the-art core banking system and why modern APIs are even more important for incumbent banks.

Grant and revoke access to your network with a proven cloud-enabled permissions platform. Whatever your organizational needs are, you'll find the perfect fit at Britive. More details at https://www.britive.com/pillar-dynamic-permission (https://www.britive.com/pillar-dynamic-permission)

Our First Look Livestream/Podcast walks you through the Super Prox sheet, our EAP Data and Spectrum Data, looking through Redkacheek's Key Stats for EAP and how to build a model and research certain players further. In this stream we use EAP, Spectrum, Data Golf's past leaderboards to determine key course statistics and also the Player Profiles.View all data at FantasyGolfBag.comTo view this podcast in the video format, please follow us on Twitch or YouTube.

On this episode of The Workflow Show, hosts Jason and Ben welcome from Cinedeck Jane Sung, COO, Charles d'Autremont, Product Development, and Ilya Derets, Project Manager. They discuss Cinedeck as a live media ingest solution, including what interesting workflows can be managed with their product and how being API first differentiates them from other solutions.

Chris Hood is the Head of Business Innovation & Strategy at Google. In this conversation he answers the below mentioned questions and many more. How do the marketers continuously innovate to remain relevant and provide value to their customers? According to research, majority of digital customers expect marketers to know what they want before you ask them ? How do we deliver personalized and predictable experience to our customers? What is an API First strategy and how does it help marketers and businesses to pivot quickly ? How does it accelerate time to market ? What are the opportunities to monetize data through APIs. In this conversation, Chris talks about Marketing Transformation, Digital Innovation at Scale and API First approach. His thought leadership and strategic insights on digital and business transformation have fueled countless enterprises' digital success. He is also a host of That Digital Show, a weekly business podcast for Google Cloud. Please visit his website https://chrishood.com You may also follow/connect with him on Linkedin : https://www.linkedin.com/in/chrishood/ Jagged with Jasravee is facilitated by Jasravee Kaur Chandra, Director- Brand Building, Research & Innovation at Master Sun, Consulting Brand of Adiva L Pvt. Ltd. Jasravee has over 20 years experience as a Strategic Brand Builder,Communications Leader and Entrepreneur. Please connect with Jasravee on Linkedin at https://www.linkedin.com/in/jasravee/ Sarvajeet Dinesh Chandra is an occasional co-host of the videocast/podcast. He is the Founder Director at Master Sun, Consulting Brand of Adiva L Pvt. Ltd. Please connect with Sarvajeet on Linkedin at https://www.linkedin.com/in/sarvajeet/ 00:00 Preview & Hello to Chris 01:53 Customers are becoming more curious, impatient and demanding 03:54 Digital transformation to meet the consumers needs 08:21 Outside-In approach to customer innovation 11:43 Hyper Personalization & Predictable Experience 15:42 Biggest barriers to digital transformation 20:15 Connected experiences as key differentiator for brands. 25:00 API First Strategy 29:00 Monetization through API 36:08 American Idol - Transformative story telling technologies for engaging content 40:00 Rapid Fire - Personally Speaking with Chris 47:19 Online Contact Details for Chris 48:19 Feedback about JWJ by Chris Follow Jagged with Jasravee on Social Media Facebook Page : https://www.facebook.com/jaggedwithjasravee Instagram : https://www.instagram.com/jagggedwithjasravee/ Podcast Page : https://anchor.fm/jagged-with-jasravee Youtube Page : https://www.youtube.com/c/jaggedwithjasravee Linktree : https://linktr.ee/jaggedwithjasravee Jagged with Jasravee, is an initiative of Master Sun, the Consulting Brand of Adiva Lifestyle Pvt Ltd. Please visit our blog at http://www.mastersun.in/ #apifirst #customerinnovation #datadrivenmarketing

Steven Cook is a Venture Associate at Chicago Ventures, a Chicago-based Venture Capital firm focused on the seed stage. Steven began his career in Venture Capital after playing professional basketball in Europe. He's a fantastic resource for advice on how to get your first job in Venture Capital and how to add value at the junior level.In this episode, we covered: Transitioning from professional basketball to Venture Capital API first companies Today's alternative asset classes The current enthusiasm around retail investing  The state of Chicago's venture landscape And much more... Please Enjoy!Further Readings on API-First Companies APIs All the Way Down - Packy McCormick The Third-Party API Economy APIs for the Rest of Us What's an API? Modern Suppliers Stealing Signs Issue 44 Manifold Group is a venture holding company based in Chicago with offices in Dallas, Los Angeles, and soon Atlantic Canada. Early stage private investments represent an extraordinary investment opportunity, but existing investment models in the space leave much to be desired.Manifold is a new model for growth in the new economy, designed to create and capture value at the early stage through synergies across its venture fund, incubation and acceleration studio, and advisory firm. Learn more about Manifold at https://www.manifold.group.You can find Steven on his Linkedin and Twitter and Chicago Ventures on their website and Linkedin.Chicago Restaurant Recommendations: Silver Spoon Thai and Lou Malnati's.Resource Recommendation: Sandhill.io 

Matt and Will discuss the background and philosophies of API-First development, the shift away from REST, React components, and APIs, and how headless development allows for an API-First model.Shout-outs:    Headless tutorials and content

This week we're covering two slightly separate topics. First, we will cover context-awareness in ubiquitous computing. Context-awareness is a tricky thing to define, but we're still going to think about the kinds of properties a context aware system should have. In the second part of this podcast we're going to be focusing on web-based APIs and why we use them. We'll cover REST, Webhooks and API-First design along the way.

Today's origin stories comes from: Sarah Stickfort Barb Levine Dave Graham We mention the WITFm Claris Engage ScholarshipSarah is working on integrating Dayback and LedgerLink togetherDave's working on learning JavaScript and our API First mentality.

The Twelve-Factor App methodology  Drafted by developers at Heroku based upon their observations of what made good apps  First presented by Adam Wiggins circa 2011 (then published in 2012)  The Factors  1 - Codebase: one codebase tracked in revision control, many deploys  2 - Dependencies: explicitly declare and isolate dependencies  3 - Config: strict separation of config from code  4 - Backing services: foster loose coupling by treating backing services as attached resources  5 - Build, release, run: strictly separate build and run stages  6 - Processes: processes are stateless and share-nothing  7 - Port binding: export services via port binding  8 - Concurrency: scale out via the process model  9 - Disposability: processes are disposable, they can be started or stopped at a moment's notice  10 - Dev/prod parity: Keep development, staging, and production as similar as possible  11 - Logs: treat logs as event streams, don't manage log files  12 - Admin processes: admin and utility code ships with app code to avoid synchronization issues  What's Missing? 7 years since first being published, what changes should be made to make it more relevant for today?  Some have argued for adding 3 additional factors:  Telemetry  Security  "API First"-philosophy  For a full transcription of this episode, please visit the episode webpage.End song:Flowerchild (Roy England Remix) by Owen Ni - Make MistakesWe'd love to hear from you! You can reach us at: Web: https://mobycast.fm Voicemail: 844-818-0993 Email: ask@mobycast.fm Twitter: https://twitter.com/hashtag/mobycast Reddit: https://reddit.com/r/mobycast