Podcasts about native apps

In this episode of ELI, we sit down with Abhinav Singh, the Founder of Techugo, a leading mobile app development company known for building highly scalable applications for startups and Fortune 500 clients like Airtel, Godfrey Phillips, and Byju's.Abhinav shares his rollercoaster entrepreneurial journey—from early success and a failed acquisition that led to bankruptcy, to rebuilding his life and company from scratch. We dive deep into the technical side of the business, discussing what makes an app truly scalable, the importance of documentation, and why enterprises still struggle with legacy tech.We also explore the future of the industry: Will AI agents replace traditional app UIs? Are Progressive Web Apps (PWAs) a threat to native development? And is the role of the app developer at risk due to AI coding tools?Topics Discussed:Building scalable apps with 200k+ downloads.Why enterprises outsource mobile development.Abhinav's personal story of bankruptcy and redemption.The shift from traditional UI to AI-driven conversational interfaces.Native Apps vs. Progressive Web Apps (PWA).The impact of AI on the future of software development jobs.Chapters(00:00) Introduction: Meet Abhinav Singh of Techugo (00:49) What makes a mobile app scalable? (01:46) Custom Solutions vs. Readymade Templates (03:02) Startups vs. Enterprise Clients (Fortune 500s) (04:45) Why big enterprises struggle to build mobile apps in-house (06:51) Go-To-Market Strategy and App Marketing (07:59) Abhinav's Journey: From $2B Exit Deal to Bankruptcy (10:33) Rebuilding from rock bottom to 1400+ Apps delivered (11:30) Technical Scalability: Why documentation is critical (14:34) Success Stories: TrueFan, Byju's, Gyan Fresh & Pickleball (16:50) The future of UI: AI Agents and Conversational Interfaces (20:56) Native Apps vs. Progressive Web Apps (PWAs) (23:24) Will AI replace App Developers? (26:09) Conclusion

Is Windows 11 full of apps you never use—or ones you shouldn't ignore? Paul Thurrott sorts the must-haves from the major annoyances, sharing candid takes on which programs he trusts, deletes, or wishes would finally disappear. Host: Paul Thurrott Download or subscribe to Hands-On Windows at https://twit.tv/shows/hands-on-windows Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free audio and video feeds, a members-only Discord, and exclusive content. Join today: https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord. Sponsor: canary.tools/twit - use code: TWIT

Is Windows 11 full of apps you never use—or ones you shouldn't ignore? Paul Thurrott sorts the must-haves from the major annoyances, sharing candid takes on which programs he trusts, deletes, or wishes would finally disappear. Host: Paul Thurrott Download or subscribe to Hands-On Windows at https://twit.tv/shows/hands-on-windows Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free audio and video feeds, a members-only Discord, and exclusive content. Join today: https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord. Sponsor: canary.tools/twit - use code: TWIT

Is Windows 11 full of apps you never use—or ones you shouldn't ignore? Paul Thurrott sorts the must-haves from the major annoyances, sharing candid takes on which programs he trusts, deletes, or wishes would finally disappear. Host: Paul Thurrott Download or subscribe to Hands-On Windows at https://twit.tv/shows/hands-on-windows Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free audio and video feeds, a members-only Discord, and exclusive content. Join today: https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord. Sponsor: canary.tools/twit - use code: TWIT

Is Windows 11 full of apps you never use—or ones you shouldn't ignore? Paul Thurrott sorts the must-haves from the major annoyances, sharing candid takes on which programs he trusts, deletes, or wishes would finally disappear. Host: Paul Thurrott Download or subscribe to Hands-On Windows at https://twit.tv/shows/hands-on-windows Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free audio and video feeds, a members-only Discord, and exclusive content. Join today: https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord. Sponsor: canary.tools/twit - use code: TWIT

Wie baust du Mobile Games, die nicht nur Spaß machen, sondern auch auf jeder Plattform funktionieren und sich selbst tragen? In dieser Episode sprechen wir über Mobile Gaming: von der Idee über den Game Loop bis zur Monetarisierung. Mit dabei ist Fabi Fink, Game Lead bei Lotum. Lotum steht für Social Casual und Puzzle Hits wie Quiz Planet und Word Blitz, hat die Marke von 1 Milliarde Installationen geknackt und spielt technisch die gesamte Klaviatur von Web bis Native.Wir klären, warum Mobile inzwischen rund die Hälfte des Gaming-Umsatzes ausmacht und ordnen Hypercasual, Casual, Midcore und Hardcore mit vielen Beispielen ein. Wir zeigen, was Mobile heute bedeutet: Native Apps in App Store und Play Store, aber auch Games als Facebook Instant Games sowie Integrationen für Reddit, Discord, TikTok und Netflix. Du erfährst, wie Social Loops auf Plattformen funktionieren, warum asynchrones Multiplayer ein Growth-Hebel ist und was Viralität gegenüber klassischer User Acquisition auszeichnet.Technisch gehen wir tief rein: Warum Lotum für viele Titel auf Vue.js setzt und Game-UX wie eine hochinteraktive Web-App denkt. Wir sprechen über Performance-Details, GPU-freundliche Animationen und warum beim WordBlitz-Core Plain JavaScript die Nase vorn hat. Im Backend wird es handfest mit WebSockets, Redis-Clustern und Realtime-Events in der Google Cloud. Dazu kommen Tools und Plattformen wie Nakama (Open Source Backend for Games) und SpacetimeDB, plus eine ehrliche Kostenstory rund um Firebase.Natürlich geht es auch ums Geld: Ads vs. In-App Purchases, Hybrid-Modelle, ROAS über 180 Tage und was erfolgreiche Titel wirklich auszeichnet. Wir teilen KPI-Realität, A/B-Testing-Erkenntnisse, warum kleine UX-Texte große Effekte haben können und welche Schwelle ein Spiel bei Lotum erreichen sollte, um weiterverfolgt zu werden.Wenn du wissen willst, wie moderne Mobile Games entstehen – technologisch, produktseitig und monetär – schnapp dir diese Episode.Unsere aktuellen Werbepartner findest du auf https://engineeringkiosk.dev/partnersDas schnelle Feedback zur Episode:

What does it take to tear down a multi-million-pound mobile app and rebuild it from the ground up? In this episode of the Life at NEXT podcast, we talk to Dave and Phil from our Technology team, who were at the heart of one of the most ambitious projects in NEXT's history: rewriting our iOS and Android apps.Together, they take us behind the scenes, discussing the move from a cross-platform framework to native development. Learn about the challenges of retraining an entire team on a tight deadline, the strategy behind launching a 100% crash-free app, and how the new, lightning-fast Android app is already generating more revenue with fewer features. Don't forget to subscribe to our channel and hit the notification bell to receive updates on everything Life at NEXT!

Joseph “Coop” Cooper is the co-founder of Nullshot, a collaborative platform for turning chats into apps. With over 20 years of experience in digital innovation and decentralized platform development, Coop is focused on building tech that empowers human creativity rather than replacing it. Prior to Nullshot, Coop launched KintoHub, a platform simplifying cloud native app development, and Earn Alliance, a Web3 platform for discovering and engaging in blockchain-based games.

Joseph “Coop” Cooper is the co-founder of Nullshot, a collaborative platform for turning chats into apps. With over 20 years of experience in digital innovation and decentralized platform development, Coop is focused on building tech that empowers human creativity rather than replacing it. Prior to Nullshot, Coop launched KintoHub, a platform simplifying cloud native app development, and Earn Alliance, a Web3 platform for discovering and engaging in blockchain-based games.

Today, the Elixir Wizards wrap up Season 14 “Enter the Elixirverse.” Dan, Charles, and Sundi look back at some common themes: Elixir plays well with others, bridges easily to access languages and tools, and remains a powerful technology for data flow, concurrency, and developer experience. We revisit the popular topics of the year, from types and tooling to AI orchestration and reproducible dev environments, and share what we're excited to explore next.   We also invite your questions and takeaways to help shape future seasons and conference conversations. Season 14 doubles as a handy primer for anyone curious about how Elixir integrates across the stack.   Key topics discussed in this episode:   * Lessons from a season of interoperability * Set-theoretic types and what new compiler warnings unlock * AI in practice: LLM orchestration, fallbacks, and real-world use * SDUI and GraphQL patterns for shipping UI across web/iOS/Android * Dataframes in Elixir with Explorer for analytics workflows * Python interoperability (ErlPort, PythonX) and when to reach for it * Reproducible dev environments with Nix and friends * Performance paths: Rustler and Zig for native extensions * Bluetooth & Nerves: Blue Heron and hardware integrations * DevEx upgrades: LiveView, build pipelines, and standard project setup * Observability and ops: Prometheus/Grafana and sensible deployments * Community feedback, conferences, and what's on deck for next season   Links mentioned in this episode: Cars.com S14E06 SDUI at Scale with Elixir https://youtu.be/nloRcgngTk?si=g4Zd4N1s56Ronrtw https://hexdocs.pm/phoenixliveview/Phoenix.LiveView.html https://wordpress.com/ https://elixir-lang.org/ S14E01 Zigler: Zig NIFs for Elixir https://youtu.be/hSAvWxh26TU?si=d55tVuZbNw0KCfT https://ziglang.org/ https://hexdocs.pm/zigler/Zig.html https://github.com/blue-heron/blueheron https://github.com/elixir-explorer/explorer S14E08 Nix for Elixir Apps https://youtu.be/yymUcgy4OAk?si=BRgTlc2VK5bsIhIf https://nixos.org/ https://nix.dev/ S14E07 Set Theoretic Types in Elixir https://youtu.be/qMmEnXcHxL4?si=Ux2lebiwEp3mc0e S14E10 Python in Elixir Apps https://youtu.be/SpVLrrWkRqE?si=ld3oQVXVlWHpo7eV https://www.python.org/ https://hexdocs.pm/pythonx/ https://github.com/Pyrlang/Pyrlang https://github.com/erlport/erlport S14E03 LangChain: LLM Integration for Elixir https://youtu.be/OwFaljL3Ptc?si=A0sDs2dzJ0UoE2PY https://github.com/brainlid/langchain S14E04 Nx & Machine Learning in Elixir https://youtu.be/Ju64kAMLlkw?si=zdVnkBTTLHvIZNBm S14E05 Rustler: Bridging Elixir and Rust https://youtu.be/2RBw7B9OfwE?si=aRVYOyxxW8fTmoRA https://github.com/rusterlium/rustler Season 3: Working with Elixir https://youtube.com/playlist?list=PLTDLmInI9YaDbhMRpGuYpboVNbp1Fl9PD&si=hbe7qt4gRUfrMtpj S14E11 Vibe Coding the LoopedIn Crochet App https://youtu.be/DX0SjmPE92g?si=zCBPjS1huRDIeVeP Season 5: Adopting Elixir  YouTubeLaunchisode and Outlaws Takeover with Chris Keathley, Amos King, and Anna Neyzberg S13E01 Igniter: Elixir Code Generation https://youtu.be/WM9iQlQSF_g?si=e0CAiML2qC2SxmdL Season 8: Elixir in a Polyglot Environment https://youtube.com/playlist?list=PLTDLmInI9YaAPlvMd-RDp6LWFjI67wOGN&si=YCI7WLA8qozD57iw !! We Want to Hear Your Thoughts *!!* Have questions, comments, or topics you'd like us to discuss on the podcast? Share your thoughts with us here: https://forms.gle/Vm7mcYRFDgsqqpDC9

Die Entwicklung mobiler Apps ist komplex - unter anderem weil unterschiedliche Geräte und Plattformen unterstützt werden müssen. Mark Zimmermann, Leiter des Center of Excellence for Mobile Solutions bei EnBW, skizziert einen modernen Ansatz der App-Entwicklung, der sich stark an den sich ständig ändernden Marktanforderungen orientiert.

In this episode, we're taking a closer look at two solutions that can redefine how we build universal React Native apps: DOM Components and React Server Components. They promise faster and better development—think low-latency interactions, offline capabilities, and the flexibility to scale effortlessly. If you're looking to future-proof your team's workflow and deliver apps that delight users regardless of the platform, this is a must-listen. To discuss DOM & React Server Components in detail, Łukasz invited Evan Bacon, the creator of Expo Router and Engineering Manager at Expo. Throughout the episode, Evan shares his expertise and journey in creating tools like DOM Components, which enable developers to integrate web code seamlessly into React Native apps, and React Server Components, simplifying server-driven rendering for mobile applications. Check out episode resources on our website

AJ (Alykhan Jetha), CEO and CTO of Marketcircle, joins the Elixir Wizards to share his experience building and evolving Daylite, their award-winning CRM and business productivity app for Apple users. He details his experiences as a self-taught programmer and how Marketcircle has navigated pivots, challenges, and opportunities since its founding in 1999. AJ explains why they migrated Daylite's backend to Elixir, focusing on their sync engine, which demands high concurrency and fault tolerance. He highlights how Elixir has improved performance, reduced cloud costs, and simplified development with its approachable syntax and productive workflows. The conversation also touches on the technical hurdles of deploying native apps for Apple devices and the potential for integrating new technologies like LiveView Native to streamline cross-platform development. For technical founders, AJ emphasizes the importance of leveraging your strengths (“superpowers”), staying deeply connected to the development process, and finding stability in tools like Elixir amidst a rapidly evolving tech ecosystem. He also shares Marketcircle's roadmap for migrating more customers to Elixir-powered systems and explores the potential for new features in their native apps. Tune in for insights on building resilient systems, navigating technical and business challenges, and how Elixir is shaping Marketcircle's future. Topics discussed in this episode: AJ's journey as a self-taught programmer and entrepreneur Marketcircle's evolution since 1999 and lessons from their pivots Daylite's growth as a flagship product for Apple users Migrating to Elixir for high concurrency and fault tolerance How Elixir improved performance and reduced cloud costs The simplicity of Elixir and its impact on developer onboarding Challenges in managing a growing microservices architecture Insights into deploying native apps for the Apple ecosystem Exploring LiveView Native for future cross-platform development Advice for technical founders: leveraging your superpowers Staying connected to development to maintain system understanding The role of Elixir in improving development efficiency and stability Planning gradual customer migrations to an Elixir-powered backend Potential new features for Daylite's native apps Benefits of collaboration with the Elixir community #ElixirMullet -- native app in the front, Elixir in the back Navigating a rapidly evolving tech ecosystem as a founder Leveraging Elixir to future-proof Marketcircle's systems Balancing technical and business priorities in a startup environment AJ's thoughts on the future of Elixir in powering business tools Links mentioned: https://www.marketcircle.com/ Daylite.app https://www.nextcomputers.org/ https://www.digitalocean.com/ Python Async https://docs.python.org/3/library/asyncio.html https://github.com/sinatra/sinatra https://github.com/dependabot https://kafka.apache.org/ https://www.djangoproject.com/ https://github.com/socketry/falcon https://github.com/puma/puma https://www.swift.org/blog/announcing-swift-6/ https://en.wikipedia.org/wiki/Async/await https://www.ffmpeg.org/ https://www.sqlite.org/ https://github.com/commanded/commanded https://pragprog.com/titles/khpes/real-world-event-sourcing/ https://en.wikipedia.org/wiki/ShipofTheseus https://reactnative.dev/ https://www.electronjs.org/ https://en.wikipedia.org/wiki/WebOS https://www.linkedin.com/in/alykhanjetha/ https://bsky.app/profile/ajetha.bsky.social Special Guest: Alykhan Jetha.

Plus, U.S. federal auto-safety regulators close their investigation into Cruise's self-driving system. And another Tesla executive announces departure from the electric vehicle maker. Zoe Thomas hosts.  Learn more about your ad choices. Visit megaphone.fm/adchoices

In this conversation, Gabriel Dierks, a lead mobile engineer at Kadmos, discusses the challenges and solutions related to mobile app development for seafarers. He also shares insights on the technology stack, release pipelines, and user experience considerations. The conversation covers topics such as the specific niche of the shipping industry, the challenges faced by seafarers, the technology stack used at Kadmos, and the release pipeline for app updates. The conversation dives further into app deployment, versioning, fingerprint comparison, Huawei App Gallery, and mobile app integration. It also delves into the challenges of integrating Huawei push service, and the connection between the web application and the mobile app for card activation. The discussion highlights the unique market focus of Kadmos and the challenges of catering to a different market.Learn React Native - https://galaxies.devGabriel DierksGabriel Twitter: https://x.com/GarioTVLinksApp.js talk: https://www.youtube.com/live/MdCn0Iq0ucU?si=8-AJoLnOsC8StM6w&t=26324Kadmos: https://www.kadmos.io/Huawei App Gallery: https://appgallery.huawei.com/TakeawaysInsights into the challenges and solutions of mobile app development for seafarersUnderstanding the technology stack and release pipeline for app updatesConsiderations for user experience in the shipping industry niche Insights into the deployment process for mobile apps, including versioning and fingerprint comparison.Challenges and considerations for integrating with the Huawei App Gallery and Huawei push service.The connection between web application and mobile app for card activation and the unique market focus of Kadmos.The impact of market differences on app development and the importance of a seamless fintech experience for users.

Dive into the dynamic world of AI innovation with our latest episode of Bonanza Growth! Hosted by Behrad Mirafshar, founder and CEO of Bonanza Studios, this week's special guest is none other than Jack Lancaster, the CPO and co-founder of Spoke.ai.Jack Lancaster, an industry titan with a passion for cutting-edge technology, takes us on an exhilarating journey through the evolution of Spoke.ai, a revolutionary platform that harnesses the power of AI to streamline workplace communication. Join Behrad and Jack as they explore the intricacies of generative AI, the transformative potential it holds for businesses worldwide, and the pivotal role it plays in navigating the complexities of remote and hybrid work environments. Discover the art of crafting AI solutions that not only meet but exceed user expectations, offering proactive insights and actionable strategies to combat information overload and enhance productivity.This captivating conversation delves deep into the challenges faced by early-stage startups in the AI space, the importance of creating genuine value, and the strategies employed to stay ahead of the curve in a rapidly evolving landscape. Don't miss out on this enlightening discussion that promises to inspire, educate, and ignite your passion for innovation!Tune in to Bonanza Growth, where every episode is an exploration of groundbreaking ideas, transformative technologies, and the visionary leaders shaping the future of AI. Subscribe now and join the conversation!Learn more about Bonanza StudiosFollow us on LinkedInFollow Jack Lancaster on LinkedIn

The first documented parachute jump happened in the late 1700s, when André-Jacques Garnerin just from balloons at “only” 2000 feet. He no doubt prepared for this moment, testing his parachute and doing everything he could to mitigate risk. Today, skydiving is a sport and a recreational activity, with a lot of safety measures and technology to further mitigate risk. Why am I telling you this? Because human beings are, by and large, risk-averse…so doing everything we can to reduce it is incredibly important. When it comes to launching a business, it, much like skydiving, is much less risky than it was 200 years ago. Part of that is the ability to create applications – and therefore launch software-based businesses – without code. That's exactly what Karla Fernandes is going to talk to us about today. And she should know. She's launched over a dozen native apps, without writing a single line of code. Top TakeawaysWhen evaluating business ideas, prioritize those that solve user problems and gauge interest through pre-sales and feedback from friends, ensuring a user-centric approach and viability.Use no-code tools for faster product development, which allow you to validate, test, and iterate quickly.With no code solutions, you can test multiple product ideas simultaneously without significant investment, helping to hedge your bets and validate ideas quickly and affordably.Show NotesKarla FernandesMillion Dollar Weekend by Noah KaganNative App: FigmaBravo StudioAirtable Sponsors: Check out Liquid WebMemberful: Get your free trial for at memberful.com/howibuiltit ★ Support this podcast ★

In this episode, Simon interviews Nader Dabit, a developer and expert in AI and Web3. Nader shares his background and explains why he left his job at AWS to focus on Web3. He discusses the current state of Web3 and AI, highlighting the job market and opportunities in the blockchain space. Nader also explains the concept of EigenLayer and its role in providing security for new blockchain networks. He emphasizes the importance of practical use cases in Web3 and discusses the potential for decentralized social networks. In this conversation, Nader Dabit and Simon discuss the intersection of Web3 and React Native, as well as the practical applications of AI in mobile app development. Learn React Native - https://galaxies.devNader DabitNader Twitter: https://twitter.com/dabit3Nader YouTube: https://www.youtube.com/c/naderdabitWilliam Github: https://github.com/dabit3LinksEigenlabs: https://www.eigenlabs.org/Bluesky: https://bsky.app/Farcaster: https://www.farcaster.xyz/Warpcast: https://warpcast.com/Lens Protocol: https://www.lens.xyz/React Native AI: https://github.com/dabit3/react-native-aiTakeawaysWeb3 and AI offer different opportunities and challenges, with Web3 currently having a more promising job market.Stablecoins are a powerful use case in Web3, providing a stable currency for international transactions.Decentralized social networks are emerging as a practical use case in Web3, offering public, immutable infrastructure and increased user control.The complexity and terminology of Web3 can be overwhelming, but embracing the chaotic and fast-paced environment can lead to success.Web3 offers exciting possibilities for building decentralized apps and social networks.React Native provides a powerful framework for developing apps on Web3.AI APIs make it easy to incorporate AI capabilities into mobile apps.Differentiation and rapid iteration are key to success in the Web3 space.

The second part of our MacVoices Live! discussion about the Apple Vision Pro fins the panel of Chuck Joiner, David Ginsburg, Brian Flanagan-Arthurs, Marty Jencius, Mark Fuccio, Jim Rea, Guy Serle, and Eric Bolden talking about keyboard experience, using the device with the Mac, and audio options and performance. Accessibility, single loop vs. over-the-head straps, weight considerations, productivity, and even comparisons to Meta's headsets are included. (Part 2) Take Control Books: The Answers You Need Now, From Leading Experts. Show Notes: Chapters: 0:02:02 Syncing Bluetooth Keyboard with Apple Vision Pro 0:04:39 Connecting Issues and Rebooting iMac 0:06:04 Using Vision Pro for Multitasking and Native Apps 0:08:02 Adjusting Window Sizes and Font Visibility 0:10:17 Placing Screens Anywhere and Customizing Window Placement 0:13:41 Using External Battery Packs to Power Vision Pro 0:15:23 Testing settings and guest mode compatibility 0:16:54 Panoramic pictures and personalized features 0:18:26 Experience with Juno app and potential issues 0:19:18 Camera Blurs When Covering Mouth or Nose 0:21:06 Traveling with AirPods on a plane 0:22:39 Alternatives to AirPods for noise cancellation and comfort 0:23:26 Dual Loop Band Comes with the Set 0:24:12 AirPods 2 and AirPods 2 with USB Charging Case Comparison 0:26:03 Controversy around Working with an iPad 0:28:44 Challenges with Facial Recognition and Unlocking Devices 0:29:42 Discussion on the Weight of the Apple Watch Bands 0:31:13 Adjusting the Solo Loop Band for Comfort 0:31:51 Comparison between Apple Vision Pro and Competitors 0:33:33 Different functionalities of Meta and Vision Pro Guests: Eric Bolden is into macOS, plants, sci-fi, food, and is a rural internet supporter. You can connect with him on Twitter, by email at embolden@mac.com, on Mastodon at @eabolden@techhub.social, and on his blog, Trending At Work. Brian Flanigan-Arthurs is an educator with a passion for providing results-driven, innovative learning strategies for all students, but particularly those who are at-risk. He is also a tech enthusiast who has a particular affinity for Apple since he first used the Apple IIGS as a student. You can contact Brian on twitter as @brian8944. He also recently opened a Mastodon account at @brian8944@mastodon.cloud. Mark Fuccio is actively involved in high tech startup companies, both as a principle at piqsure.com, or as a marketing advisor through his consulting practice Tactics Sells High Tech, Inc. Mark was a proud investor in Microsoft from the mid-1990's selling in mid 2000, and hopes one day that MSFT will be again an attractive investment. You can contact Mark through Twitter, LinkedIn, or on Mastodon. David Ginsburg is the host of the weekly podcast In Touch With iOS where he discusses all things iOS, iPhone, iPad, Apple TV, Apple Watch, and related technologies. He is an IT professional supporting Mac, iOS and Windows users. Visit his YouTube channel at https://youtube.com/daveg65 and find and follow him on Twitter @daveg65 and on Mastodon at @daveg65@mastodon.cloud. Dr. Marty Jencius has been an Associate Professor of Counseling at Kent State University since 2000. He has over 120 publications in books, chapters, journal articles, and others, along with 200 podcasts related to counseling, counselor education, and faculty life. His technology interest led him to develop the counseling profession ‘firsts,' including listservs, a web-based peer-reviewed journal, The Journal of Technology in Counseling, teaching and conferencing in virtual worlds as the founder of Counselor Education in Second Life, and podcast founder/producer of CounselorAudioSource.net and ThePodTalk.net. Currently, he produces a podcast about counseling and life questions, the Circular Firing Squad, and digital video interviews with legacies capturing the history of the counseling field. Generally, Marty is chasing the newest tech trends, which explains his interest in A.I. for teaching, research, and productivity. Marty is an active presenter and past president of the NorthEast Ohio Apple Corp (NEOAC). Jim Rea built his own computer from scratch in 1975, started programming in 1977, and has been an independent Mac developer continuously since 1984. He is the founder of ProVUE Development, and the author of Panorama X, ProVUE's ultra fast RAM based database software for the macOS platform. He's been a speaker at MacTech, MacWorld Expo and other industry conferences. Follow Jim at provue.com and via @provuejim@techhub.social on Mastodon. Guy Serle, best known for being one of the co-hosts of the MyMac Podcast, sincerely apologizes for anything he has done or caused to have happened while in possession of dangerous podcasting equipment. He should know better but being a blonde from Florida means he's probably incapable of understanding the damage he has wrought. Guy is also the author of the novel, The Maltese Cube. You can follow his exploits on Twitter, catch him on Mac to the Future on Facebook, at @Macparrot@mastodon.social, and find everything at VertShark.com. Support:      Become a MacVoices Patron on Patreon      http://patreon.com/macvoices      Enjoy this episode? Make a one-time donation with PayPal Connect:      Web:      http://macvoices.com      Twitter:      http://www.twitter.com/chuckjoiner      http://www.twitter.com/macvoices      Mastodon:      https://mastodon.cloud/@chuckjoiner      Facebook:      http://www.facebook.com/chuck.joiner      MacVoices Page on Facebook:      http://www.facebook.com/macvoices/      MacVoices Group on Facebook:      http://www.facebook.com/groups/macvoice      LinkedIn:      https://www.linkedin.com/in/chuckjoiner/      Instagram:      https://www.instagram.com/chuckjoiner/ Subscribe:      Audio in iTunes      Video in iTunes      Subscribe manually via iTunes or any podcatcher:      Audio: http://www.macvoices.com/rss/macvoicesrss      Video: http://www.macvoices.com/rss/macvoicesvideorss 00:00:00 Apple Vision Pro: Immersive Mac Experience 00:02:01 Syncing Bluetooth Keyboard with Apple Vision Pro 00:04:38 Connecting Issues and Rebooting iMac 00:06:03 Using Vision Pro for Multitasking and Native Apps 00:08:01 Adjusting Window Sizes and Font Visibility 00:10:17 Placing Screens Anywhere and Customizing Window Placement 00:13:40 Using External Battery Packs to Power Vision Pro 00:15:22 Testing settings and guest mode compatibility 00:16:54 Panoramic pictures and personalized features 00:18:26 Experience with Juno app and potential issues 00:19:18 Camera Blurs When Covering Mouth or Nose 00:21:06 Traveling with AirPods on a plane 00:22:39 Alternatives to AirPods for noise cancellation and comfort 00:23:25 Dual Loop Band Comes with the Set 00:24:12 AirPods 2 and AirPods 2 with USB Charging Case Comparison 00:26:02 Controversy around Working with an iPad 00:28:44 Challenges with Facial Recognition and Unlocking Devices 00:29:41 Discussion on the Weight of the Apple Watch Bands 00:31:13 Adjusting the Solo Loop Band for Comfort 00:31:51 Comparison between Apple Vision Pro and Competitors 00:33:33 Different functionalities of Meta and Vision Pro 00:33:50 Wrapping up the conversation about Apple Vision Pro 00:34:44 Advertising partnership with BackBeat Media at BackBeatMedia.com.

In this episode, Simon interviews Evan Bacon, the creator of Expo Router. They explore the features and benefits of Expo Router, including file-based routing, deep linking, and automatic TypeScript. Evan shares the roadmap for Expo Router version 4, which aims to unify the server-client connection and introduce server components. They also touch on the future of Expo Web and its separation from the core native platform.Learn React Native - https://galaxies.devEvan BaconTwitter: https://twitter.com/BaconbrixGithub: https://github.com/evanbaconBlog: https://evanbacon.dev/Blog Code: https://github.com/EvanBacon/evanbacon.devTakeaways- Expo Router is a file-based router for native applications that enables universal code sharing and simplifies complex navigation routing.- Expo Router provides features like deep linking, automatic TypeScript, and API routes, which allow for secure server-client communication.- Expo Router version 4 aims to tie together the server-client connection and introduce server components, enabling more flexible and efficient app development.- Expo Web will be separated from the core native platform, allowing developers to choose between Expo Router and React Navigation based on their specific needs.- The future of Expo Router and Expo Web promises exciting advancements in universal app development and improved developer experience. - Expo V4 is expected to be released around May, with a focus on unblocking important features.- Evan Bacon's blog, built with Expo, showcases the capabilities of Expo Router and other Expo features.- Expo and Next.js have different scopes and priorities, but Expo aims to be a universal React framework.- Expo's goal is to unlock new types of mobile experiences and provide a seamless transition between web and native.

Simon talks with Rodrigo Figueroa, a React Native developer from Chile. We dive deep into building universal apps for iOS, Android, and the web with React Native, plus tools like Solito and Rodrigos packages around MedusaJS and Vercel AI! Learn React Native - https://galaxies.devRodrigo FigueroaTwitter: https://twitter.com/bidahGithub: https://github.com/bidahUniversal Medusa: https://universal-medusa-docs.vercel.appReact Native Vercel AI: https://github.com/bidah/react-native-vercel-aiLinksMedusaJS: https://medusajs.comSolito: https://solito.devCodemods: https://nextjs.org/docs/app/building-your-application/upgrading/codemodsRadix UI: https://www.radix-ui.comShadCN: https://ui.shadcn.comNativewind: https://www.nativewind.devVercel AI: https://github.com/vercel/ai

Join Robin and Mazen as they delve into React Native app security. They discuss safe API key storage, secure data handling, SSL pinning, and additional pointers to help you keep your app safe. Check it out today! This episode brought to you by Infinite Red! Infinite Red is a premier React Native design and development agency located in the USA. With five years of React Native experience and deep roots in the React Native community (hosts of Chain React and the React Native Newsletter), Infinite Red is the best choice for your next React Native app.Episode NotesOfficial RN docshttps://jscrambler.com/Jscrambler's articleHalak Vachhani's articleJamon's twitter threadRNR-239 Shrinking your app with ProGuard w/ Jame Hamiltonhttps://www.youtube.com/@JamonsCodeQuestsJail Monkey (Gant's library) Connect With Us!React Native Radio: @ReactNativeRdioMazen -  @mazenchamiRobin -  @robin_heinze

Simon talks with David, a freelance designer and developer. We talk about the React Native community, how shipping apps is a muscle you can train, and how Tamagui and Expo play together.Learn React Native - https://galaxies.devDavid Twitter: https://twitter.com/flexbox_David Website: https://davidl.fr/David GitHub: https://github.com/flexboxLinks:Release Checklist: https://flexbox.gumroad.com/l/expo-checklistApp Icon Badge: https://github.com/obytes/app-icon-badge

Welcome to the first episode of Lightspeed! Armani Ferrante joins Garrett and Mert to discuss what crypto wallets get wrong. Armani is a product genius and the founder behind Anchor, Backpack, xNFTs and Mad Lads. In this episode, we cover the innovations behind Backpack and xNFTs, why demand generation is everything, if projects should go multichain, how to build a community, why Armani decided to build on Solana, why most apps will launch their own chain and more! - - Timestamps: (00:00) Introduction (00:48) Wallets: The Gateway to Crypto (04:01) Backpack: The Wallet's iPhone Moment (10:25) A Focus on Product vs Distribution (16:19) Should Projects Go Multichain?  (18:52) How Backpack Thinks About Distribution  (21:52) Permissionless Ad (23:09) xNFTs vs Native Apps (25:00) Why Choose Solana? (35:38) Metaplex and Why Neutral Standards Matter (39:05) Why Armani Loves the Cosmos Vision (48:47) Work-Life Balance & In-Person vs Remote (55:46) Leadership Lessons from Building Backpack (59:44) Rapid Fire Segment - - Follow Armani: https://twitter.com/armaniferrante Follow Mert: https://twitter.com/0xMert_ Follow Garrett: https://twitter.com/GarrettHarper_ Follow Lightspeed: https://twitter.com/Lightspeedpodhq Subscribe on YouTube: https://bit.ly/43o3Syk Subscribe on Apple: https://apple.co/3OhiXgV Subscribe on Spotify: https://spoti.fi/3OkF7PD Get top market insights and the latest in crypto news. Subscribe to Blockworks Daily Newsletter: https://blockworks.co/newsletter/ - - Use code LIGHTSPEED30 to get 30% off Permissionless 2023 in Austin: https://blockworks.co/event/permissionless-2023 - - Resources Backpack https://twitter.com/xNFT_Backpack Mad Lads https://www.madlads.com/ https://twitter.com/MadLadsNFT Anchor https://www.anchor-lang.com/ https://twitter.com/anchorlang Coral https://www.coral.community/ https://twitter.com/0xCoral - -  Disclaimers: Lightspeed was kickstarted by a grant from the Solana Foundation. Nothing said on Lightspeed is a recommendation to buy or sell securities or tokens. This podcast is for informational purposes only, and any views expressed by anyone on the show are solely our opinions, not financial advice. Mert, Garrett and our guests may hold positions in the companies, funds, or projects discussed.

Links in this episode:Build your own TwitterReal-World Xcode Project Using TuistLinting Documentation with Vale to Increase Quality & ConsistencyBasic Stream Backend Integration using NodeJSComparison of Cherry Brown and Gazzew U4 switchesSkip typing your login credentials manually with Xcode breakpointsNative vs Web: Technologies Available to Native Apps but not Web Apps3 mistakes to avoid with async / awaitUnderstanding unstructured and detached tasks in SwiftWhat I Learned Writing My Own CloudKit Syncing LibraryCyclomatic Complexity in Swift: Understanding How it Affect Your Code QualityRunwayPut your mobile releases on autopilot. More info on runway.teamDo iOS Conference - November 8 and 9, 2023Get your tickets now. Lead Software Developer Learn best practices for being a great lead software developer.Support the showRate me on Apple Podcasts. Send feedback on SpeakPipeOr contact me on Mastodon: https://hachyderm.io/@appforce1Support my podcast with a monthly subscription, it really helps.My book: Being a Lead Software Developer

This week on Modern Web Alyssa Nicoll from Progress takes the web out of the browser and into native apps. Bringing you the cutting edge of native applications with embedded web technologies, Angular offers the best of both worlds. We take some minor detours into learning backend technology stacks as a long life JavaScript developer, and the awesome communities and friends we've made along the way. Join us for a spectacular journey and a couple tangents.   Guest Alyssa Nicoll, Sr. Developer Advocate at Progress   Host Jesse Tomchak, Software Architect at This Dot Labs   Sponsored by This Dot Labs

Zak Cole, a core contributor to Canto, joins Bankless to answer: "What's good with Canto?" ------

Building Cloud Native Applications can bring about many operational and security problems. Today, we sat down with an expert in this field to talk about building cloud native applications, and deploying applications that are secure in the cloud. This episode features Fausto Lendeborg, Co-Founder & CCO, from Secberus, who provides answers and explanations to a variety of questions regarding Building applications in the cloud, deploying applications securely in the cloud, and much more. Join us as we discuss: · Building Cloud Native Applications · Deploying Applications Securely · Managing a Cloud · Security, Compliance, and Governance · DevOps To hear this episode, and many more like it, we would encourage you to subscribe to The Virtual CISO Podcast here. You can find all our full length and short form episodes here. Listening on a desktop & can't see the links? Just search for The Virtual CISO Podcast in your favorite podcast playerhttps://www.pivotpointsecurity.com/

When planning the development of a new app, one of the most basic questions to answer is whether to develop it as a Web app or as a native app. In this episode we delineate some of the pros and cons of each approach, including cost, accessibility, performance, capabilities, and more. We also discuss some alternatives like hybrid apps and cross-platform frameworks. Show Notes Episode 4: iOS vs. Android Episode 6: How does the Web work? Episode 59: What is HTML and CSS? Episode 60: What is JavaScript? Episode 99: Android App Development Follow us on Twitter @KopecExplains. Theme “Place on Fire” Copyright 2019 Creo, CC BY 4.0Episode Notes Notes go here Find out more at http://kopec.live

There's a lot to consider before committing to a framework to build a native app. If you choose to build in native, ask yourself whether you're prepared to handle the downsides that come with it.   To start, you're limited to one framework and writing in one programming language. If you're not familiar with the syntax, that could pose a major learning curve. With native apps, it's tempting to have a separate app for every device that a user might run your app on, but on the operations front, that's a slippery slope with high overhead costs. If you're on a tight budget or working on small teams like Chuck and Robbie, the cost of paying developers to maintain a bunch of apps isn't appealing. There's no shame in knowing your resource limitations and taking the easy route.  In this episode, Chuck and Robbie talk about the trade-off between building native apps in Swift, Objective-C, React Native, and other web technologies, why they enjoy progressive web apps, and Disney's monopoly in media.  Key Takeaways [02:21] - A whiskey Review - Four Roses Small Batch Select. [11:11] - Chuck and Robbie discuss building apps in different frameworks. [22:58] - Chuck and Robbie talk about progressive web apps. [34:54] - TV Shows Chuck and Robbie are currently watching. [51:46] - Chuck and Robbie's Halloween plans. Quotes [03:16] - “It's crazy how no one has money because of the recession, and yet everything that you could possibly buy is super expensive and sold out all the time. It doesn't make sense.” ~ Robbie Wagner [23:04] - “You feel like businesses don't feel like they have a presence unless they're in the App Store.” ~ Chuck Carpenter [25:05] - “The one thing that has been that I've used as a progressive web app that's worked well is Google Photos.” ~ Robbie Wagner Links Four Roses Bourbon Small Batch Select Costco WhistlePig Rye Whiskey Sagamore Spirit White Dog Distilling Buffalo Trace Distillery Android Java Script iPhone Flutter Google iOS React Native Expo Capacitor Electron Samsung Roku NextJS iPad Apple Chrome Hulu Wuf.plus Astro Ember JSON API Solid American Horror Story Game of Thrones House of the Dragon The Great Netflix Echoes HBO Max Disney NBC 21st Century Fox FX National Geographic Sons of Anarchy Marvel Star Wars Wolverine Spiderman Deadpool Aviation Gin Welcome to Wrexham Ballers Entourage David Letterman My Next Guest Is Peloton Tik Tok The Simpsons Law and Order SVU Peter Pan Toy Story He-Man Zorro Ninja Turtles Connect with our hosts Robbie Wagner Chuck Carpenter Ship Shape Subscribe and stay in touch Apple Podcasts Spotify Google Podcasts Whiskey Web and Whatnot Top-Tier, Full-Stack Software Consultants This show is brought to you by Ship Shape. Ship Shape's software consultants solve complex software and app development problems with top-tier coding expertise, superior service, and speed. In a sea of choices, our senior-level development crew rises above the rest by delivering the best solutions for fintech, cybersecurity, and other fast-growing industries. Check us out at shipshape.io.

What if you could build the routes for native apps by creating files? Evan Bacon joins us to talk about the Expo Router he has been working on and more! Links https://docs.expo.dev https://twitter.com/baconbrix https://github.com/expo/expo https://docs.expo.dev/eas/metadata Tell us what you think of PodRocket We want to hear from you! We want to know what you love and hate about the podcast. What do you want to hear more about? Who do you want to see on the show? Our producers want to know, and if you talk with us, we'll send you a $25 gift card! If you're interested, schedule a call with us (https://podrocket.logrocket.com/contact-us) or you can email producer Kate Trahan at kate@logrocket.com (mailto:kate@logrocket.com) Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form (https://podrocket.logrocket.com/get-podrocket-stickers), and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket combines frontend monitoring, product analytics, and session replay to help software teams deliver the ideal product experience. Try LogRocket for free today. (https://logrocket.com/signup/?pdr) Special Guest: Evan Bacon.

JavaOne 2022 Speaker Preview In this conversation Oracle's Jim Grisanzio talks with Java developer and JavaOne 2022 speaker Emily Jiang from the UK. Emily is a Java Champion and Developer Advocate. She's doing three sessions at JavaOne in October on microservices and cloud native development and she previews them in this discussion. She also talks about her experiences with the Java community and JavaOne.  JavaOne 2022 from October 17-20 in Las Vegas JavaOne 2022: Registration and Sessions JavaOne 2022 Updates at Inside Java Emily Jiang, Developer Advocate, IBM  @emilyfhjiang Java Development and Community OpenJDK Inside Java Dev.Java @java on Twitter Java on YouTube Duke's Corner Podcast Host Jim Grisanzio, Oracle Java Developer Relations, @jimgris

We get the details behind Thunderbird acquiring K-9 Mail, share the best new features of Plasma 5.25, check-in on Ubuntu's RISC-V development status, and discuss Photoshop coming to Linux via the web.

We get the details behind Thunderbird acquiring K-9 Mail, share the best new features of Plasma 5.25, check-in on Ubuntu's RISC-V development status, and discuss Photoshop coming to Linux via the web.

Robert Bye is the Project Manager of Native Apps at Figma. Figma is a collaborative design tool aimed primarily at website and app designers.This episode of iPad Pros is sponsored by Agenda, an elegant new take on notes for iPad, iPhone, and the Mac. Learn more at www.agenda.com. Agenda 14 is now available as a free download for macOS, iPadOS, and iOS. The focus of this release is powerful organization and navigation, with major updates to tags, and new features like autocompletion and back-linking.Bonus content and early episodes with chapter markers are available by supporting the podcast at www.patreon.com/ipadpros. Bonus content and early episodes are also now available in Apple Podcasts! Subscribe today to get instant access to iPad Possibilities, iPad Ponderings, and iPad Historia! New episodes of the bonus shows release the first week of every month. Show notes are available at www.iPadPros.net. Feedback is welcomed at iPadProsPodcast@gmail.com.Chapter Markers00:00:00: Opening00:01:17: Agenda 14 Now Available00:01:30: Robert Bye00:07:01: Figma00:08:51: FigJam00:10:16: Collaboration 00:12:35: Different uses of FigJam00:14:11: Templates00:14:57: Figma - web app on iPad?00:19:12: Exporting Figma into Playgrounds?00:20:48: Making "fake" apps in Figma00:22:39: Sponsor - Agenda 1400:25:27: Timer in FigJam00:27:30: How do you use Figma internally?00:29:34: FigJam Tools00:31:11: Widgets00:32:34: Stamps00:33:56: Code Snippets 00:34:53: Media Importing00:36:57: Apple Pencil00:37:39: Gestures00:38:35: Keyboard Shortcuts00:40:22: Apple Shortcuts and Automation?00:41:00: FigJam Links00:41:45: FigJam Stories00:43:21: Moving Data from FigJam to Figma?00:46:38: Anything else?00:47:21: Closing00:48:11: Pricing Model?00:49:20: Closing See acast.com/privacy for privacy and opt-out information.

In this fantastic episode, AWS Hero and Community Builder Luc van Donkersgoed (@donkersgood) gives us a view into how his company has incorporated integration testing into their serverless AWS environments! Resources: https://twitter.com/donkersgood https://bitesizedserverless.com/

We're talking with Thomas Steiner of Google's Project Fugu about native apps or web apps. What is Project Fugu? Hardware limitations or requirements for using game controllers on the web. Working with new hardware API's. Reasons to choose a native app. As well as Thomas' SVG web app he's built.

Rob Vettor, a Cloud Solution Architect at Microsoft, has a lot to say about Cloud Native Apps and tells us how to host them on Azure. Media file: https://azpodcast.blob.core.windows.net/episodes/Episode385.mp3 YouTube: https://youtu.be/nZjUkAyt4Jc Resources: Cloud Native eBook: https://docs.microsoft.com/en-us/dotnet/architecture/cloud-native/ Dapr eBook: https://docs.microsoft.com/en-us/dotnet/architecture/dapr-for-net-developers/ DotNet Conf on Microservices – 6 hour training class (June 30th, 2020)• Microservices Workshop Module 1: Introducing microservices https://www.youtube.com/watch?v=jMDufMYAsmw&t=168s • Microservices  Module 2: Modeling and architecting microservices https://www.youtube.com/watch?v=u7MM21aIsqk• Microservices  Workshop Module 3: Microservice communication https://www.youtube.com/watch?v=iL3Kxd4Auys• Microservices Workshop Module 4: Deploying microservices to Kubernetes https://www.youtube.com/watch?v=3G7NB4waGbk• Microservices Workshop Module 5: Deploying service mesh to Kubernetes https://www.youtube.com/watch?v=qwEfynnevEU• Microservices Module 6: Distributed data https://www.youtube.com/watch?v=7kVmb747vfM Blog: www.thinkingincloudnative.com   Other updates: General availability: Azure Spring Cloud Pricing Model Change | Azure updates | Microsoft Azure Public preview: Azure Spring Cloud New Relic One integration and additional feature updates | Azure updates | Microsoft Azure General availability: Application Insights integration with App Services for Java & Node.js apps | Azure updates | Microsoft Azure Public preview: Create AKS clusters without local user accounts | Azure updates | Microsoft Azure Public preview: Azure Kubernetes Service (AKS) smart defaults | Azure updates | Microsoft Azure   Drive growth with the most partner-focused business platform https://azure.microsoft.com/en-us/blog/drive-growth-with-the-most-partnerfocused-business-platform/   Manage RDP and SSH connectivity at scale with Azure Bastion  https://azure.microsoft.com/en-us/blog/manage-rdp-and-ssh-connectivity-at-scale-with-azure-bastion/   Innovate from cloud to edge on your terms with Azure https://azure.microsoft.com/en-us/blog/innovate-from-cloud-to-edge-on-your-terms-with-azure/   Public preview: API Management and Event Grid integration  https://azure.microsoft.com/en-us/updates/public-preview-api-management-and-event-grid-integration/

In this episode of The Business of Cloud Native, Chris Holmes talks about bootstrapping Decipher Technology Studies and their core product, intelligent service mesh Greymatter.io. He also talks about why it's so important for brownfield and greenfield apps to talk to one another and the many similarities between public sector and private sector organizations. Highlights: How Greymatter combines business intelligence and security controls.The difference between working with public sector customers and private sector / enterprise customers — and why there are more similarities than differences. How segmentation is sometimes necessary for any highly security-conscious organization, including both government organizations and financial services companies in the private sector. Why we need to respect legacy applications — because they tend to be the mission-critical applications that drive revenue. Why connecting brownfield and greenfield applications is critical, because not all ‘legacy' apps will ever be moved to the cloud.What ‘returns' a company is looking for when evaluating ROI on cloud migrations. What we mean when we talk about an “ROI” on security tools. Why Kubernetes' terrible networking is part of why Chris could see that service meshes would be necessary even back in 2015. Links:Chris on LinkedIngreymatter.io 

The cloud is eating enterprise IT, and while on-premise applications are going to be around for a long time to come, the importance of being able to successfully take advantage of cloud technologies should not be understated. However, it's one thing to simply port an existing application to the cloud, but developing software to be run in cloud environments is a different matter altogether.In this week's episode, Adam and guest host Keumars Afifi-Sabet talk to Red Hat senior solutions architect Erica Langhi, to find out how organisations need to adjust their thinking when developing for the cloud, which tools and processes are best-suited to the task, and how new technologies like containers and microservices are making the job easier than ever.Elsewhere, we also discuss the ‘Fujiwhara' of patches that IT professionals have been hit with this week, the public spat between Slack and Microsoft Teams, and the ongoing clash over the government's controversial digital services tax.For links to everything we've mentioned in this week's episode, head to https://bit.ly/ITPP-cloudapps.

Do you know what cloud native apps are? Well, we don’t really either, but today we’re on a mission to find out! This episode is an exciting one, where we bring all of our different understandings of what cloud native apps are to the table. The topic is so interesting and diverse and can be interpreted in a myriad of ways. The term ‘cloud native app’ is not very concrete, which allows for this open interpretation. We begin by discussing what we understand cloud native apps to be. We see that while we all have similar definitions, there are still many differences in how we interpret this term. These different interpretations unlock some other important questions that we also delve into. Tied into cloud native apps is another topic we cover today – monoliths. This is a term that is used frequently but not very well understood and defined. We unpack some of the pros and cons of monoliths as well as the differences between monoliths and microservices. Finally, we discuss some principles of cloud native apps and how having these umbrella terms can be useful in defining whether an app is a cloud native one or not. These are complex ideas and we are only at the tip of the iceberg. We hope you join us on this journey as we dive into cloud native apps! Follow us: https://twitter.com/thepodlets Website: https://thepodlets.io Feeback: info@thepodlets.io https://github.com/vmware-tanzu/thepodlets/issues Hosts: Carlisia Campos Bryan Liles Josh Rosso Nicholas Lane Key Points From This Episode: What cloud native applications mean to Carlisia, Bryan, Josh, and Nicholas. Portability is a big factor of cloud native apps. Cloud native applications can modify their infrastructure needs through API calls. Cloud native applications can work well with continuous delivery/deployment systems. A component of cloud native applications is that they can modify the cloud. An application should be thought of as multiple processes that interact and link together. It is possible resources will begin to be requested on-demand in cloud native apps. An explanation of the commonly used term ‘monolith.’ Even as recently as five years ago, monoliths were still commonly used. The differences between a microservice approach and a monolith approach. The microservice approach requires thinking about the interface at the start, making it harder. Some of the instances when using a monolith is the logical choice for an app. A major problem with monoliths is that as functionality grows, so too does complexity. Some other benefits and disadvantages of monolith apps. In the long run, separating apps into microservices gives a greater range of flexibility. A monolith can be a cloud native application as well. Clarification on why Brian uses the term ‘microservices’ rather than cloud native. ‘Cloud native’ is an umbrella term and a set of principles rather than a strict definition. If it can run confidently on someone else’s computer, it is likely a cloud native application. Applying cloud native principles when building an app from scratch makes it simpler. It is difficult to adapt a monolith app into one which uses cloud native principles. The applications which could never be adapted to use cloud native principles. A checklist of the key attributes of cloud native applications. Cloud native principles are flexible and can be adapted to the context. It is the responsibility of thought leaders to bring cloud native thinking into the mainstream. Kubernetes has the potential to allow us to see our data centers differently. Quotes: “An application could be made up of multiple processes.” — @joshrosso [0:14:43] “A monolith is simply an application or a single process that is running both the UI, the front-end code and the code that fetches the state from a data store, whether that be disk or database.” — @joshrosso [0:16:36] “Separating your app is actually smarter than the long run because what it gives you is the flexibility to mix and match.” — @bryanl [0:22:10] “A cloud native application isn’t a thing. It is a set of principles that you can use to guide yourself to running apps in cloud environments.” — @bryanl [0:26:13] “All of these things that we are talking about sound daunting. But it is better that we can have these conversations and talk about things that don’t work rather than not knowing what to talk about in general.” — @bryanl [0:39:30] Links Mentioned in Today’s Episode: Red Hat — https://www.redhat.com/en IBM — https://www.ibm.com/ VWware — https://www.vmware.com/ The New Stack — https://thenewstack.io/ 10 Key Attributes of Cloud-Native Applications — https://thenewstack.io/10-key-attributes-of-cloud- native-applications/ Kubernetes — https://kubernetes.io/ Linux — https://www.linux.org/ Transcript: EPISODE 16 [INTRODUCTION] [0:00:08.7] ANNOUNCER: Welcome to The Podlets Podcast, a weekly show that explores Cloud Native one buzzword at a time. Each week, experts in the field will discuss and contrast distributed systems concepts, practices, tradeoffs and lessons learned to help you on your cloud native journey. This space moves fast and we shouldn’t reinvent the wheel. If you’re an engineer, operator or technically minded decision maker, this podcast is for you. [EPISODE] [0:00:41.4] NL: Hello and welcome back, my name is Nicholas Lane. This time, we’ll be diving into what it’s all about. Cloud native applications. Joining me this week are Brian Liles. [0:00:53.2] BL: Hi. [0:00:54.3] NL: Carlisia Campos. [0:00:55.6] CC: Hi everybody, glad to be here. [0:00:57.6] NL: And Josh Rosso. [0:00:58.6] JR: Hey everyone. [0:01:00.0] NL: How’s it going everyone? [0:01:01.3] JR: It’s been a great week so far. I’m just happy that I have a good job and able to do things that make me feel whole. [0:01:08.8] NL: That’s awesome, wow. [0:01:10.0] BL: Yeah, I’ve been having a good week as well in doing a bit of some fun stuff after work. Like my soon to be in-laws are in town so I’ve been visiting with them and that’s been really fun. Cloud native applications, what does that mean to you all? Because I think that’s an interesting topic. [0:01:25.0] CC: Definitely not a monolith. I think if you have a monolith running on the clouds, even if you start it out that way, I wouldn’t say it’s a cloud native app, I always think of containerized applications and if you’re using the container system then it’s usually because you want to have a smaller systems in more of them, that sort of thing. Also, when I think of cloud native applications, I think that they were developed the whole strategy of the development in the whole strategy of deploying and shipping has been designed from scratch to put on the cloud system. [0:02:05.6] JR: I think of it as applications that were designed to run in container. And I also think about things like services, like micro services or macro services to know what you want to call them that we have multiple applications that are made to talk not just with themselves but with other apps and they deliver a bigger functionality through their coordination. Then what I also want to go cloud native apps, I think of apps that we are moving to the cloud, that’s a big topic in itself but applications that we run in the cloud. All of our new fancy services and our SaaS offerings, a lot of these are cloud native apps. But then on the other side, I think about applications, they are cloud native are tolerant to failure and on the other side, can actually talk about sells of their health and who they’re talking to. [0:02:54.8] CC: Gets very complicated. [0:02:56.6] BL: Yeah. That was the side of that I haven’t thought about. [0:03:00.7] JR: Actually, it’s for me that always come to mind are obviously portability, right? Wherever you're running this application, it can run somewhat consistently, be it on different clouds or even a lot of people, you know, are running their own cloud which is basically their on-prem cloud, right? That application being able to move across any of those places and often times, containerization is one of the mechanisms we use to do that, right? Which is what we all stated. Then I guess the other thing too is like, this whole cloud ecosystem, be it a cloud provider or your own personal – are often times very API driven, right? So, the applications, maybe being able to take advantage of some of those API’s should they need to. Be it for scaling purposes otherwise. It’s really interesting model. [0:03:43.2] NL: It’s interesting, for me like this question because so far, everyone is getting similar but also different answers. And for me, I’m going to give a silent answer to me, a cloud native application is a lot of things we said like portable. I think of micro services when II] think of a cloud native application. But it’s also an application that can modify the infrastructure it needs via API calls, right? If your application needs a service or needs a networking connection, it can – the application itself can manifest that via cloud offering, right? That’s what I always thought of as a cloud native application, right? If you need like a database, the application can reach out to like AWS RDS and spin up the database and that was an aspect of I always found very fascinating with cloud native applications, it isn’t necessarily the definition but for me, that’s the part that I was really focused on I think is quite interesting. [0:04:32.9] BL: Also, CI/CD cloud native apps are made to work well with our CI, our seamless integration and our continuous delivery/deployment systems as well, that’s like another very important aspect of cloud native applications. We should be able to deploy them to production without typing anything in. should be some kind of automated process. [0:04:56.4] NL: Yeah, that is for sure. Carlisia, you mentioned something that I think it’s good for us to talk about a little bit which is terminology. I keeping coming back to that. You mentioned monolithic apps, what are monoliths then? [0:05:09.0] CC: I am so hung up on what you just said, can we table that for a few minutes? You said cloud native applications for you is an application that can interact with the infrastructure and maybe for example, is the database. I wonder if you have an example or if you could expand on that, I want to – if everybody agrees with that, I’m not clear on what that even is. Because as a developer which is always my point of view is what I know. It’s a lot of responsibility for the application to have. And for example, when I would think cloud native and I’m thinking now, maybe I’m going off on a tangent here. But we have Kubernetes, isn’t that what Kubernetes is supposed to do to glue it all together? So, the application only needs to know what it needs to do. But spinning up an all tight system is not one of the things it would need to do? [0:05:57.3] BL: Sure, actually, I was going to use Kubernetes as my example for cloud native application. Because Kubernetes is what it is, an app, right? It can modify the cloud that it’s running. And so, if you have Kubernetes running in AWS, you can create ELB’s, elastic load balancers. It can create new nodes. It can create new databases if you need, as I mentioned. Kubernetes itself is my example like a cloud native application. I should say that that’s a good callout. My example of what a cloud native application isn’t necessarily like that’s a rule. All cloud native applications have to modify the cloud in which they exist in. It’s more that they can modify. That is a component of a cloud native application. Kubernetes is being an example there. I don’t know, I guess things like operators inside of Kubernetes like the rook operator will create storage for you when you spin up like root create a Ceph cluster, it will also spin up like the ELB’s behind it or at least I believe it does. Or that kind of functionality. [0:06:57.2] CC: I can see what you're saying because for example, if I choose to use the storage inside something like Kubernetes, then you will be required of my app to call an SDK and connect so that their storage somehow. So, in that sense I guess, you are using your app. Someone correct me if I’m wrong but that’s how the connection is created, right? You just request – but you’re not necessarily saying I want this thing specific, you just say I want this sort of thing like which has their storage and then you define that elsewhere. So, your applications don’t need to know details bit definitely needs to say, I need this. I’m talking about again, when your data storage is running on top of Kubernetes and not outside of it. [0:07:46.4] BL: Yeah. [0:07:47.3] NL: That brings up an interesting part of this whole term cloud native app. Because it’s like everything else in the space, our terms are not super concrete and an interesting piece about this is that an application – does an application half the map one to one with the running process? What is an application? [0:08:06.1] NL: That is interesting because it could say that a serverless app or a serverless rule, whatever serverless really is, I guess we can get into that in another episode. Are those cloud native applications? They’re not just running anywhere. [0:08:19.8] JR: I will punt on that because I know my boundaries are and that definitely not in my boundaries. But the reason I bring this up is because a little while ago, it’s probably year ago in a Kubernetes [inaudible 0:08:32] apps, we actually have a conversation about what an application was. And the consensus from the community and from the group members was that actually, an application could be made up of multiple processes. So, let’s say you were building this large SaaS service and because you’re selling dog food online, your application could be your dog food application. But you have inventory management. You have a front end, maybe you haven’t had service, you have a shipping manager and things like that. Sales tax calculator. Are those all applications? Or is it one application? The piece about cloud application are cloud native applications because what we found in Kubernetes is that the way we’re thinking about applications is, an application is multiple processes, that can be linked together and we can tell the whole story of how all those interact and working. Just something else, another way to think about this. [0:09:23.5] NL: Yeah, that is interesting, I never really considered that before but that makes a lot of sense. Particularly with the rise of things like GRPC and the ability to send dedicated messages to are like well codified messages too different processes. That gives rise to things like this multi-tenant process as an application. [0:09:41.8] BL: Right. But going back to your idea around cloud native applications being able to commandeer the resources that they’re needing. That’s something that we do see. We see it within Kubernetes right now. I’ll give you above and beyond the example that you gave is that whenever you create a staple set. And Kubernetes, the operator behind staple set that actually goes and provisions of PPC for you, you requested a resource and whatever you change the number of instances from one to like five, guess what? you get four more PPC’s. Just think about it, that is actually something that is happening, it’s a little transparent with people. but I can see to the point of we’re just requesting a new resource and if we are using cloud services to watch our other things, or our cloud native services to watch our applications, I could see us asking for this on demand or even a service like a database or some other type of queuing thing on demand. [0:10:39.2] CC: When I hear things like this, I think, “ Wow, it sounds very complicated. "But then I start to think about it and I think it’s really neat because it is complicated but the alternative would have been way more complicated. I mean, we can talk about, this is sort of how it’s done now. I mean, it’s really hard to go into details on a one-hour episode. We can’t cover the how it’s done or make conceptually, we are sort of throwing a lot of words out there sort of conceptualize it but we can also try to talk about it in a conceptual way how it is done in a non-cloud native world. [0:11:15.3] NL: Yeah, I kind of want to get back to the question I posed before, what is a monolithic app, what is a none cloud native app? And not all none cloud native apps are monoliths but this is actually something that I’ve heard a lot and I’ll be honest. I have an idea of what a monolithic app is but I think I don’t have a very good grasp of it. We kind of talked a bit about like what a cloud native app is, what is a none cloud native or what came before a cloud native applications. What is a monolith? [0:11:39.8] CC: I’m personally not a big fan of monoliths. Of course, I worked with them but once micro services started becoming common and started developing in that mode. I am much more of a fan of breaking things down for so many different reasons. It is a controversial topic for sure. But to go back to your question, the monolith is basically, you have an app, sort of goes to what Brian was saying, it’s like, what is an app? If you think of an app and like one thing, Amazon is an app, right? It’s an app that we use to buy things as consumers. And you know, the other part is the cloud. But let’s look at it like it’s an app that we use to buy things as consumers, we know it’s broken down to so many different services. There is the checkout service, there is the cart service. I mean, I’m imagining, these I can imagine thought, the small services that compose that one Amazon app. If it was a monolith, those services that you know – those things are different systems that are talking together. The whole thing would be on one code base. It would reside in same code base or it will be deployed together. It will be shipped together. If you make a change in one place and you needed to deploy that, you have to deploy the whole thing together. You might have teams that are working on separate aspects but they’re working against the same code base. And maybe because of that, that will lend itself to teams not really specializing on separate aspects because everything is together so you might make one change of the impacts another place and then you have to know that part as well. So, there is a lot less specialization and separation of teams as well. [0:13:32.3] BL: Maybe to give an example of my experience and I think it aligns with a lot of the details Carlisia just went over. Even taking five years back, my experience at least was, we’d write up a ticket and we’d ask somebody to make a server space for us, maybe run [inaudible 0:13:44] on it, right? We’d write all this Java code and we’d package it into these things that run on a JDL somewhere, right? We would deploy this whole big application you know?Let’s call it that dog food app, right? It would have maybe even like a state layer and have the web server layer, maybe have all these different pieces all running together, this big code base as Carlisia put it. And we’d deploy it, you know, that process took a lot of time and was very consuming especially when we needed to change stuff, we didn’t have all these modern API’s and this kind of decoupled applications, right? But then, over time, you know, we started learning more and more about the notion of isolating each of these pieces or layers. So that we could have the web server, isolated in its how, put some site container or a unit and then the state layer and the other layers even isolated, you know, the micro service approach more or less. And then we were able to scale independently and that was really awesome. so we saw a lot of the gains in that respect. We basically moved our complexity to other areas, we took our complexity that you need to all happen in the same memory space and we moved a lot of it into the network with this new protocols of that different services talk to one another. It’s been an interesting thing kind of seeing the monolith approach and the micro service approach and how a lot of these micro service apps are in my opinion a lot more like cloud native aligned, if that makes sense? Just seeing how the complexity shows around in that regard. [0:15:05.8] CC: Let me just say one more thing because it’s actually the biggest aspect of micro services that I like the most in comparison, you know, the aspect of monolith that I hate the most and that I don’t hate it, I appreciate the least, let’s put it that way. Is that, when you have a monolith, it is so easy because design is hard so it’s so easy to couple different parts of your app with other parts of your app and have couples cold and coupled functionality. When you break this into micro services, that is impossible. Because it was working with separate code bases. If you force to think what is your interface, you’re always thinking about the interface and what people need to consume from you, your interface is the only way into your app, into your system. I really like the aspect that it forces you to think about your API. And people will argue, “Well you can’t put the same amount of effort into that if you have a monolith.” Absolutely, but in reality, I don’t see it. And like Josh was saying, it is not a walk on the park, but I’d much rather deal with those issues, those complexities that Microsoft has create then the challenges of running a big – I’m talking about big monoliths, right? Not something trivial. [0:16:29.8] JR: I will come to distil this about how I look at monoliths and how it fits into this conversation. A monolith is simply an application that is or a single process in this case that is running both the UI, the front-end code and the code that fetches the state from a data store, whether that be disk or database. That is what a monolith is. The reasons people use monoliths are many but I can actually think of some very good reasons. If you have code reuse and let’s say you have a website and you were trying to – you have farms and you want to be able to use those form libraries or you have data access and you want to be able to reuse that data access code, a monolith is great. The problem with monoliths is as functionality becomes larger, complexity becomes larger and not at the same rate. I’m not going to say that it is not linear but it’s not quite exponential. Maybe it logs into or something like that. But the problem is that at a certain point, you’re going to have so much functionality, you’re not going to be able to put it inside of one process, see Rails. Rails is actually a great example of this where we run into the issues where we put so much application into a rail source directory and we try to run it and we basically run up with these huge processes. And we split them up. But what we found is that we could actually split out the front-end code to one process. We could spit out the middle ware, see multiple process in the middle, the data access layer to another process and we could use those, we could actually take advantage of multiple CPU cores or multiple computers. The problem with this is that with splitting this out, it’s complexity. So, what if you have a [inaudible 0:18:15] is, what I’m trying to say here in a very long way is that monoliths have their places. As a matter of fact, the encourage, at least I still encourage people to start with the monolith. Put everything in one place. Whenever it gets too big, you spit it out. But in a cloud native world, because we’re trying to take advantage of containers, we’re trying to take advantage of cords on CPUs, we’re trying to take advantage of multiple computers to do that in the most efficient way, you want to split your application up into smaller pieces so that your front end versus your middle layer, versus your data access layer versus your data layer itself can run on as many computers and as many cores as possible. Therefore, spreading thee risk and spreading the usage because everything should be faster. [0:19:00.1] NL: Awesome. That is some great insight into monolithic apps and also the benefit and pros and cons of them. Like something I didn’t have before. Because I’ve only ever heard of a praise monolithic apps and then it’s like said in hushed tones or what the swear word directly after it. And so, it’s interesting to hear the concept of it being that each way you deploy your application is complex but there are different tradeoffs, right? It’s the idea that I was like, “Why don’t you want to turn your monolithic into micro services? Well, there’s so much more overhead, so much more yak shaving you have to do to get there to take advantage of micro services. That was awesome, thank you so much for that insight. [0:19:39.2] CC: I wanted to reiterate a couple aspects of what Brian said and Josh said in regards to that. One huge advantage, I mean, your application needs to be substantial enough that you feel like you need to do that, you’re going to get some advantage from it. when you had that point, and you do that, you’re clearing to services like Josh was saying and Brian was saying, you have the ability to increase your capabilities, your process capabilities based on one aspect of the system that needs it. So, you have something that requires very low processing, you run that service with certain level of capabilities. And something that like your orders process or your orders micro service. You increase the processing power for that much more than some other part. When it comes to running this in the cloud native world, I think this is more an infrastructure aspect. But my understanding is that you can automate all of that, you can determine, “Okay, I have analyzed my requirements based on history and what I need is stacks. So, I’m going to say tell the cloud native infrastructure, this is what I need in the automation will take care of bringing the system up to that if anything happens.” We are always going to be healing your system in an automated way and this is something that I don’t think gets talked about enough like we say, we talk about, “Oh things split up this way and they’re run this way but in an automated mode that these makes all of the difference. [0:21:15.4] NL: Yeah that makes a lot of sense actually. So, basically analytic apps don’t give us the benefit of automation or automated deployment versus like micro services kind of give us and cloud native applications give us the rise. [0:21:28.2] BL: Yes, and think about this, whenever you have five micro services delivering your applications functionality and you need to upgrade the front-end code for the HTML, whatever generates the HTML. You can actually replace that piece or replace that piece and that not bring your whole application down. And even better yet, you can replace that piece one at a time or two at a time, still have the majority of your applications still running and maybe your users won’t even know at all. So, let’s say you have a monolith and you are running multiple versions of this monoliths. When you take that whole application down, you literally take the whole application down not only do you lose front-end capacity, you also lose back-end capacity as well. So, separating your app is actually smarter than the long run because what it gives you is the flexibility to mix and match and you could actually scale the front end at a different level than you did at the backend. And that is actually super important in [inaudible 0:22:22] land and actually Python land and .NET land if you’re writing monoliths. You have to scale at the level of your monolith and if you can scale that then you are having wasted resources. So smaller micro services, smaller cloud native apps makes the run of containers, actually will use less resources. [0:22:41.4] JR: I have an interesting question for us all. So obviously a lot of cloud native applications usually maybe look like these micro services we’re describing, can a monolith be a cloud native application as well? [0:22:54.4] BL: Yes, it can. [0:22:55.1] JR: Cool. [0:22:55.6] NL: Yeah, I think so. As long as the – basically monolith can be deployed in the mechanism that we described like CSAD or can take advantage of the cloud. I believe the monolith can be a cloud native application, sure. [0:23:08.8] CC: There are monolith – because I am glad you brought that up because I was going to bring that up because I hear Brian using the micro services in cloud native apps interchangeably and it makes it really hard for me to follow, “Okay, so what is not cloud native application or what is not a cloud native service and what is not a cloud native monolith?” So, to start this thread with the question that Josh just asked, which also became my question: if I have a monolith app running a cloud provider is that a cloud native app? If it is not what piece of puzzle needs to exists for that to be considered a cloud native app? And then the follow up question I am going to throw it out there already is why do we care? What is the big deal if it is or if it isn’t? [0:23:55.1] BL: Wow, okay. Well let’s see. Let’s unpack this. I have been using micro service and cloud native interchangeably probably not to the best effect. But let me clear up something here about cloud native versus micro services. Cloud native is a big term and it goes further than an application itself. It is not only the application. It is also the environment of the application can run in. It is the process that we use to get the application to production. So, monoliths can be cloud native apps. We can run them through CI/CD. They can run in containers. They can take advantage of their environment. We can scale them independently. but we use micro services instead this becomes easier because our surface area is smaller. So, what I want to do is not use that term like this. Cloud native applications is an umbrella term but I will never actually say cloud native application. I always say a micro service and the reason why I will say the micro service is because it is much more accurate description of that process that is running. Cloud native applications is more of the umbrella. [0:25:02.0] JR: It is really interesting because a lot of the times that we are working with customers when they go out and introduce them to Kubernetes, we are often times asked, “How do I make my application cloud native?” To what you are talking about Brian and to your question Carlisia, I feel like a lot of times people are a little bit confused about it because sometimes they are actually asking us, “How do I break this legacy app into smaller micro services,” right? But sometimes they are actually asking like, “How do I make it more cloud native?” And usually our guidance or the things that we are working with them on is exactly that, right? It is like getting that application container so we can get it portable whether it is a monolith or a micro service, right? We are containerizing it. We are making it more portable. We are maybe helping them out with health checks that the infrastructure environment that they are running in can tap into it and know the health of that application whether it’s to restart it with Kubernetes as an example. We are going through and helping them understand those principles that I think fall more into the umbrella of cloud native like you are saying Brian if I am following you correctly and helping them kind of enhance their application. But it doesn’t necessarily mean splitting it apart, right? It doesn’t mean running it in smaller services. It just means following these more cloud native principles. It is hard talk up so that was continuing to say cloud native right? [0:26:10.5] BL: So that is actually a good way of putting it. A cloud native application isn’t a thing. It is a set of principles that you can use to guide yourself to running apps in cloud environments. And it is interesting. When I say cloud environments I am not even really particularly talking about Kubernetes or any type of scheduler. I am just talking about we are running apps on other people’s computers in the cloud this is what we should think about and it goes through those principles. Where we use CI/CD, storage maybe most likely will be ephemeral. Actually, you know what? That whole process, that whole virtual machine that we are running on that is ephemeral too, everything will go away. So, cloud native applications is basically a theory that allows us to be strategic about running applications with other people’s computers and storage and networking and compute may go away. So, we do this at this way, this is how to get our 5-9’s or 4-9’s above time because we can actually do this. [0:27:07.0] NL: That is actually a great point. The cloud native application is one that can confidently run on somebody else’s computer. That is a good stake in the ground. [0:27:15.9] BL: I stand behind that and I like the way that you put it. I am going to steal that and say I made it up. [0:27:20.2] NL: Yeah, go ahead. We have been talking about monoliths and cloud native applications. I am curious, since you all are developers, what is your experience writing cloud native applications? [0:27:31.2] JR: I guess for green field projects where we are starting from scratch and we are kind of building this thing, it is a really pleasant experience because a lot of things are sort of done for us. We just need to know how to interact with the API or the contract to get the things we need. So that is kind of my blanket statement. I am not trying to say it is easy, I am just saying like it has become quite convenient in a lot of respects when adopting these cloud native principles. Like the idea that I have a docker file and I build this container and now I am running this app that I am writing code for all over the place, it’s become such a more pleasant experience and at least in my experience years and years ago with like dropping things into the tomcat instances running all over the place, right? But I guess what’s also been interesting is it’s been a bit hard to convert older applications into the cloud native space, right? Because I think the point Carlisia had started with around the idea of all the code being in one place, you know it is a massive undertaking to understand how some of these older applications work. Again, not saying that all older applications are only monoliths. But my experience has been that they generally are. Their bigger code base is hard to understand how they work and where to modify things without breaking other things, right? When you go and you say, “All right, let’s adopt some cloud native principles on this app that has been running on the mainframe for decades” right? That is a pretty hard thing to do but again, green field projects I found it to be pretty convenient. [0:28:51.6] CC: It is actually easy, Josh. You just rewrite it. [0:28:54.0] JR: Totally yes. That is always a piece of cake. ,[0:28:56.9] BL: You usually write it in Go and then it is cloud native. That is actually the secret to cloud native apps. You write it in Go, you install it, you deploy in Kubernetes, mission accomplish, cloud native to you. [0:29:07.8] CC: Anything written in Go is cloud native. We are declaring that here, you heard that here first. [0:29:13.4] JR: That is a great question, it’s like how do we get there? That is a hard question and not one that I would basically just wave a magic set of words over and say that we are there. But what I would say is that as we start thinking of moving applications to cloud native first, we need to identify applications that cannot be called updated and I could actually give you some. Your Windows 2003 applications and yes, I do know some of you are running 2003 still. Those are not cloud native and they never will be and the problem is that you won’t be able to run them in a containerized environment. Microsoft says stop using 2003, you should stop using it. Other applications that won’t be cloud native are applications that require a certain level of machine or server access. We have been able to attract GPU’s. But if you’re working on the IO level like you are actually looking at IO or if you are looking at hardware interrupts. Or you are looking at anything like that, that application will never be cloud native. Because there is no way that we can in a shared environment, which most likely your application will be running in, in the cloud. There is no way that first of all that the hypervisor that is actually running your virtual machine wants to give you that process or give you that access or that is not being shared from one to 200 other processes on that server. So, applications that want low level access or have real time, you don’t want to run those in the cloud. They cannot be cloud native. That still means a lot of applications can be. [0:30:44.7] CC: So, I keep thinking of if I own a tech stack and I every once in a while stop and evaluate, if I am squeezing as most tech as I can out of my system? Meaning am I using the best technology out there to the extent that fits my needs? If I am that kind of person and I don’t know – it’s like when I say I am a decision maker and even if I was a tech person like I am also a tech person, I still would not have – unless I am one of the architects. And sometimes even the architects don’t have an entire vision. I mean they have to talk to other architects who have a greater vision of the whole system because systems that can be so big. But at any rate, if I am an architect or I own the tech stack one way or another, my question is, is my system a cloud native system? Is my app a cloud native app? I am not even sure that we clarified enough for people to answer that. I mean it is so complicated, maybe we did hopefully we helped a little bit. So basically, this will be my question, how do I know if I am there or not? Because my next step would be well if I am not there then what am I missing? Let me look into it and see if the cost benefit is worth it. But if I don’t know what is missing, what do I look at? How do I evaluate? How do I evaluate if I am there and if I am not, what do I need to do? So, we talked about this a little bit on episode one, which we talked about cloud native like what is cloud native in general and now we are talking about apps. And so, you know, there should be a checklist of things that cloud native should at least have these sets of things. Like the 12-factor app, what do you need to have to be considered 12 factor app. We should have a checklist, 12 factor app I think having that checklist is being part of micro-service in the cloud native app. But I think there needs to be more. I just wish we would have that not that we need to come up with that list now but something to think about. Someone should do it, you know? [0:32:57.5] JR: Yeah, it would be cool. [0:32:58.0] CC: Is it reasonable or now to want to have that checklist? [0:33:00.6] BL: So, there is, there is that checklist that exist I know that Red Hat has one. I know that IBM has one. I would guess VMware has one on one of our web pages. Now the problem is they’re all different. What I do and this is me trying to be fair here. The New Stack basically they talk about things that are happening in the cloud and tech. If you search for The New Stack in cloud native application, there is a 10-bullet list. That is what I send to people now. The reason I send that one rather than any vendor is because a vendor is trying to sell you something. They are trying to sell you their vision of cloud native where they excel and they will give you products that help you with that part like CI/CD, “oh we have a product for that.” I like The New Stack list and actually, I Googled it while you were talking Carlisia because I wanted it to bring it up. So, I will just go through the titles of this list and we’ll make sure that we make this link available. So, there is 10 Key Attributes of Cloud-Native Applications. Package as light weight to containers. Developed with best-of-breed languages and frameworks, you know that doesn’t mean much but that is how nebulous this is. Designed as loosely coupled microservices. Centered around API’s for interaction and collaboration. Architected with clean separation of stateless and stateful services. Isolated from server and operating system dependencies. Deployed on self-service elastic cloud infrastructure. Managed through agile DevOps processes. Automated capabilities. And the last one, Defined policy-driven resource allocation. And as you see, those are all very much up for interpretation or implementations. So, a cloud native app from my point of view tries to target most of these items and has an opinion on most of these items. So, a cloud native app isn’t just one thing. It is a mindset that I am running. Like I said before, I am running my software on other people’s computers, how can I best do this.? [0:34:58.1] CC: I added the link to our shownotes. When I look at this list, I don’t see observability. That word is not there. Does it fall under one of those points because observability is another new-ish term that seems to be in parcel of cloud native? Correct me here, people. [0:35:19.1] JR: I am. Actually, the eighth item, ‘Manage through agile DevOps processes,’ is actually – they don’t talk about monitoring observability. But for an application for a person who is not developing application, so whether you have a dev ops team or you have an SRE practice, you are going to have to be able to communicate the status and the application whether it be through metrics logs or metrics logs or whatever the other one is. I am thinking – traces. So that is actually I think is baked in it is just not called out. So, to get the proper DevOps you would need some observability that is how you get that status when you have a problem. [0:35:57.9] CC: So, this is how obscure these things can be. I just want to point this out. It is so frustrating, so literally we have item eight, which Brian has been, as the main developer so he is super knowledgeable. He can look at that and know what it means. But I look at that and the words log metrics, observability none of these words are there and yet Brian knew that that is what it means that that is what he meant. And I don’t disagree with him. I can see it now but why does it have to be so obscure? [0:36:29.7] JR: I think a big thing to consider too is like it very much lands on spectrum, right? Like something you would ask Carlisia is how do I qualify if my app is cloud native or what do I need to do? And you know a lot of people in my experience are just adopting parts of this list and that’s totally fine. You know worrying about whether you fully qualify as a cloud native app since we have talked about it as more of a set of principles is something – I don’t know if there is too too much value in worrying about whether you can block that label onto your app as much as it is, “Oh I can see our organization our applications having these problems.” Like lacking portability when we move them across providers or going back to observability, not being able to know what is going on inside of the application and where the network packets are headed and they switched to being asked we’re late to see these happening. And as those problems come on, really looking at and adopting these principles where it is appropriate. Sometimes it might not be with the engineering efforts without them, one of the more cloud native principles. You know you just have to pick and choose what is most valuable to you. [0:37:26.7] BL: Yes, and actually this is what we should be doing as experts, as thought-leaders, as industry movers and shakers. Our job is to make this easier for people coming behind us. At one time, it was hard to even start an application or start your operating system. Remember when we had to load AN1, you know? Remember we had to do that back in the day on our basic, on our Comado64’s or Apple or Apple2. Now you turn your computer on and it comes with instantly. We click on application and it works. We need to actually bring this whole cloud movement to that point where things like if you include these libraries and you code with these API’s you get automatic observability. And I am saying that with air quotes but you get the ability to have this thing to monitor it in some fashion. If you use this practice and you have this stack, CI/CD should be super simple for you and we are just not quite there yet. And that is why the industry is definitely rotating around this and that is why there has been a lot of buzz around cloud native and Kubernetes is because people are looking at this to actually solve a lot of these problems that we’ve had. Because they just haven’t been solvable because everybody stacks are too different. But this one though, the reason Linux is I think ultimately successful is because it allowed us to do things and all of these Linux things we liked and it worked on all sorts of computers. And it got that mindset behind it behind companies. Kubernetes could also do this. It allows us to think about our data centers as potentially one big computer or fewer computers that allows us to make sure things are running. And once we have this, now we can develop new tools that will help us with our observability, with our getting software into production and upgraded and where we need it. [0:39:17.1] NL: Awesome. So, on that, we are going to have to wrap up for this week. Let’s go ahead and do a round of closing thoughts. [0:39:22.7] JR: I don’t know if I have any closing thoughts. But it was a pleasure talking about cloud native applications with you all. Thanks. [0:39:28.1] BL: Yeah, I have one thought is that all of these things that we are talking about it sounds kind of daunting. But it is better that we can have these conversations and talk about things that don’t work rather than not knowing what to talk about in general. So this is a journey for us and I hope you come for more of our journey. [0:39:46.3] CC: First I was going to follow up on Josh and say I am thoughtless. But now I want to fill up on Brian’s and say, no I have no opinions. It is very much what Brian said for me, the bridging of what we can do using cloud native infrastructure in what we read about it and what we hear about it like for people who are not actually doing it is so hard to connect one with the other. I hope by being here and asking questions and answering questions and hopefully people will also be very interactive with us. And ask us to talk about things they want to know that we all try to connect it too little by little. I am not saying it is rocket science and nobody can understand it. I am just saying for some people who don’t have multi background experience, they might have big gaps. [0:40:38.7] NL: And that is for sure. This was a very useful episode for me. I am glad to know that everybody else is just as confused at what cloud native applications actually mean. So that was awesome. It was a very informative episode for me and I had a lot of fun doing it. So, thank you all for having me. Thank you for joining us on this week of the Kublets Podcast. And I just want to wish our friend Brian a very happy birthday. Bye you all. [0:41:03.2] CC: Happy birthday Brian. [0:41:04.7] BL: Ahhhh. [0:41:05.9] NL: All right, bye everyone. [END OF EPISODE] [0:41:07.5] ANNOUNCER: Thank you for listening to The Podlets Cloud Native Podcast. Find us on Twitter at https://twitter.com/ThePodlets and on the http://thepodlets.io/ website, where you'll find transcripts and show notes. We'll be back next week. Stay tuned by subscribing. [END]See omnystudio.com/listener for privacy information.

In this episode, we cover the following topics: AWS offers not one, but two, managed services for secrets management. Systems Manager Parameter Store and AWS Secrets Manager have similar functionality, making it sometimes confusing to know which to use. We compare and contrast the two services to help guide your choice. The three types of sensitive data injection supported by Elastic Container Service (ECS). Understanding when sensitive data is injected into the container and how to handle updates to secrets (such as credential rotation). The required configuration changes and IAM permissions you need to enable ECS integration with Parameter Store and Secrets Manager. A walkthrough of the specific steps you need to take to update your ECS application to support secrets integration. Detailed Show NotesWant the complete episode outline with detailed notes? Sign up here: https://mobycast.fm/show-notes/Support Mobycasthttps://glow.fm/mobycastEnd SongStraddling by Derek RussoMore InfoFor a full transcription of this episode, please visit the episode webpage.We'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

Support Mobycast-> https://glow.fm/mobycast

What does it mean to build a cloud-native application? While at NDC in London, Carl and Richard talked to Scott Guthrie about the latest features available in Azure. While there are always the Infrastructure-as-a-Service options of VMs and the like, you don't really get the power of the cloud until you move into more of the platform features. Scott describes how existing applications and be lifted-and-shifted into VMs in the cloud, and then broken apart to take advantage of various services. The ultimate manifestations use technologies that are cloud-specific, like CosmosDB and Logic App features so that you focuses solely on your code.Support this podcast at — https://redcircle.com/net-rocks/donations

What does it mean to build a cloud-native application? While at NDC in London, Carl and Richard talked to Scott Guthrie about the latest features available in Azure. While there are always the Infrastructure-as-a-Service options of VMs and the like, you don't really get the power of the cloud until you move into more of the platform features. Scott describes how existing applications and be lifted-and-shifted into VMs in the cloud, and then broken apart to take advantage of various services. The ultimate manifestations use technologies that are cloud-specific, like CosmosDB and Logic App features so that you focuses solely on your code.Support this podcast at — https://redcircle.com/net-rocks/donations

AppStories Episode 12 – The State of Non-Native Apps

For our sixth podcast we asked Matt Cowger @mcowger (VCDX #52!) to pick something relevant about Cloud Native applications that might be of the beaten path a bit.  Matt suggested that we discuss NoSQL, SQL, Message Queues and how they fit into modern application structures.  We cover a wide list of technology such as Redis, RIAK, […]

Live from Macworld|iWorld 2014 Rene talks to Don Melton, former director of internet technology at Apple, and Matt Drance, former Apple evangelist, about web apps, native apps, hybrid apps, CarPlay, Oculus rift, and what comes next!

This week we talk to Scott Jenson about the future of mobile, Internet of Things, connected devices, Internet connected toasters and infrastructure policy.