Software Architecture Insights

• Navigating AI Development with InWorld's Kylan Gibbs

  Today, we explore the evolving landscape of conversational AI with Kylan Gibbs, the CEO and founder of InWorld AI. We focus on how InWorld develops AI products that enhance the creation of scalable applications, particularly in consumer contexts where user interaction is increasingly conversational. Kylan shares insights into the importance of real-time performance and how expectations differ between consumer and business applications. He emphasizes that while businesses often prioritize automation and factuality, consumer applications demand speed and engagement, requiring a nuanced approach to AI design. Join us as we delve into the technical challenges and innovations that are shaping the future of AI interactions.The podcast features a deep dive into the evolving landscape of software architecture, focusing on the role of AI in modern applications. Our guest, Kylan Gibbs, the CEO of InWorld AI, discusses how his company builds AI products that facilitate real-time conversational experiences for users. Kylan emphasizes that the majority of consumer interactions with AI now occur through conversational interfaces, such as chatbots and voice assistants. He explains that InWorld specializes in creating scalable applications that not only meet user demands but also adapt to varying contexts, such as customer support, gaming, and educational applications. This adaptability is crucial because user expectations differ significantly across different scenarios. The conversation further explores the intricate balance between performance and user experience, highlighting how different user expectations influence the design and functionality of AI-driven applications. Kylan shares insights into the engineering challenges that come with real-time AI interactions, emphasizing the need for robust performance engineering to deliver smooth conversational flows. He believes that as AI technology progresses, the focus should shift towards enhancing user engagement while maintaining high performance standards. Overall, this episode offers valuable insights into how software architects can navigate the complexities of integrating AI into consumer-facing applications while ensuring that the user experience remains at the forefront.Takeaways: InWorld AI focuses on creating conversational interfaces that improve user engagement in applications. The performance of real-time conversational AI is crucial, requiring fast and precise responses. Consumer AI applications need to adapt to various contexts, changing user expectations significantly. Optimizing AI performance often requires using low-level programming languages like C for better control. AI spending is increasingly shifting towards consumer applications, presenting new opportunities for developers. Understanding the nuances of AI architecture is essential for creating effective conversational agents. Links referenced in this episode:softwarearchitectureinsights.cominworld.aiCompanies mentioned in this episode: InWorld AI OpenAI Google Mentioned in this episode:How do you operate a modern organization at scale?Read more in my O'Reilly Media book "Architecting for Scale", now in its second edition. http://architectingforscale.com Architecting for ScaleWhat do 160,000 of your peers have in common?They've all boosted their skills and career prospects by taking one of my courses. Go to atchisonacademy.com.Atchison Academy

  --------  

  40:36

  --------

  40:36
• Get Rid of Your Users - The Role of Transactional vs Experiential Applications

  Not all applications are created equal. Some applications process transactions and maintain state, while others aim to deliver content, data, or experiences to users. For software architects and engineering leaders, recognizing these core application types is essential for making informed decisions regarding scalability, infrastructure, security, and data management. Understanding whether an application is experiential or transactional influences its design and architecture. This distinction is vital for ensuring that applications meet user expectations effectively and efficiently.Understanding the distinction between experiential and transactional applications is crucial for software architects and engineering leaders. Each type of application serves a different purpose and is designed to meet specific user expectations. Experiential applications aim to keep users engaged for extended periods, providing value through interaction and content delivery. Examples include social media platforms, where the longer users stay, the more advertising revenue the platform generates. The architecture of such applications needs to prioritize low latency, high availability, and the ability to deliver personalized content efficiently. This requires strong data management practices and the use of advanced technologies like machine learning to enhance user experience.On the other hand, transactional applications focus on speed and efficiency. They are designed for users to complete tasks quickly, such as checking an order status or making a purchase. The underlying architecture must ensure reliability and data integrity, as even minor delays can frustrate users. Key architectural considerations for transactional applications include low latency APIs, robust database management for consistency, and the ability to handle asynchronous processes effectively. Understanding these differences is essential for architects to design systems that align with user expectations and business goals.The implications of choosing the right application type extend beyond product management; they are foundational to the overall architecture and infrastructure strategy. A misalignment can lead to performance issues and user dissatisfaction, making it vital for software leaders to understand not just how to build functional software but how to build software that meets the specific needs of its users. As we explore these themes, we recognize that the architectural decisions made today will shape the user experiences of tomorrow, influencing everything from scalability to data management.Takeaways: Not all applications are created equal; they serve different purposes and user needs. Experiential applications aim to engage users for longer periods, enhancing value over time. Transactional applications prioritize speed and efficiency, allowing users to complete tasks quickly. Understanding the type of application informs architectural decisions about scalability and data management. Application design impacts user experience; architects must align their strategies with user expectations. Misaligning application type with architectural choices can lead to performance and satisfaction issues. Links referenced in this episode:softwarearchitectureinsights.comCompanies mentioned in this episode: Amazon.com Mentioned in this episode:How do you operate a modern organization at scale?Read more in my O'Reilly Media book "Architecting for Scale", now in its second edition. http://architectingforscale.com Architecting for Scale

  --------  

  12:28

  --------

  12:28
• Why File Uploads Are Hard: Lessons from Uploadcare's Founder Igor Debatur

  Igor Debatur, the founder of Uploadcare, joins us to discuss the complexities and challenges of file management in modern applications. Uploadcare specializes in making the file upload experience seamless for users. Igor shares how their journey started from being an agency that built products for clients to creating a comprehensive solution for file management that addresses the needs of engineers today. We delve into the intricacies of file uploads, which may seem straightforward but are fraught with challenges such as security, compliance, and scalability. Igor emphasizes the growing demand for efficient file handling as applications increasingly require users to upload larger files, including images and videos. He explains how Uploadcare's services help developers avoid the pitfalls of building file management systems from scratch, allowing them to focus on their core business rather than dealing with tedious technical issues. This episode provides valuable insights into why many companies should consider using a managed solution like Uploadcare instead of attempting to build their own file management solutions, especially when they can save time and resources in the process.Takeaways: Uploadcare helps engineers manage file uploads, making the process more efficient and reliable. The growing demand for video and image uploads means tools like Uploadcare are essential for developers. Igor emphasized that building file management systems from scratch is often not practical for companies. Uploadcare offers a modular file uploader that integrates easily with various JavaScript frameworks like React and Angular. The service provides real-time image transformations and document conversions to streamline user experiences. Using Uploadcare saves companies valuable engineering time, allowing them to focus on their core business needs. Links referenced in this episode:uploadcare.comsoftwarearchitectureinsights.comCompanies mentioned in this episode: Upload Care Zillow Please DonatePlease consider donating in order to keep this podcast...and other content by Lee Atchison...arriving in your inbox.Please Donate Here

  --------  

  24:10

  --------

  24:10
• Five Best Practices for Mastering Configuration in Cloud Native Applications

  Managing configuration in cloud-native applications can be overwhelming due to its complexity and abundance. This episode focuses on five essential best practices to help simplify configuration management. We discuss the importance of maintaining a single source of truth, using automation to handle variations, and implementing revision control for tracking changes. Centralizing configurations and deploying them through automated systems are also highlighted as key strategies. By treating configurations with the same discipline as source code, we can significantly reduce complexity and enhance the reliability of our applications.Navigating the complexities of software configuration in cloud-native applications is a significant challenge for architects and developers alike. Throughout this discussion, I explore the various types of configurations that exist within modern applications, from network interconnections to database permissions and application secrets. As cloud-native architectures often employ microservices, the sheer volume of configurations can lead to confusion and potential errors. I emphasize the importance of managing this complexity by implementing five best practices that can greatly aid in organizing and controlling configurations more effectively. The first practice I highlight is establishing a single source of truth for all configuration data. By avoiding redundant copies of configurations scattered across multiple servers, we can minimize the risks of configuration drift and ensure that changes are uniformly applied. Next, I discuss the use of automation to handle variations within configurations, which allows for a single configuration file to be adapted for multiple use cases without the need for numerous duplicates. This not only simplifies management but also reduces potential errors. Additionally, I advocate for the use of revision control systems to track changes to configuration files, ensuring that we have a clear history of modifications that can be referenced in case of issues. Centralizing configurations in a well-known location and employing automated distribution systems further solidify our ability to manage configurations with confidence. By treating configurations with the same discipline as we do our code, we can enhance the reliability and security of our applications, ultimately leading to better software architecture outcomes.Links referenced in this episode:softwarearchitectureinsights.comMentioned in this episode:How do you operate a modern organization at scale?Read more in my O'Reilly Media book "Architecting for Scale", now in its second edition. http://architectingforscale.com Architecting for Scale

  --------  

  9:50

  --------

  9:50
• From Finance to Healthcare: Navigating the Shift with Michi Kono

  Michi Kono, the CTO of Garner Health, joins us to discuss the intersection of technology and healthcare. Garner Health leverages advanced data management techniques to help employers find the best healthcare providers for their employees. Michi shares insights from his extensive background in the financial sector, where he led significant tech initiatives, and explains how those experiences inform his current work in healthcare. We explore the complexities of the U.S. healthcare system, including data accessibility and the challenges posed by outdated practices. Michi emphasizes the importance of modernizing data systems and the role of startups in driving innovation in this vital industry.The conversation with Michi Kono, CTO of Garner Health, delves into the intersection of technology and healthcare. Michi shares his transition from the financial sector, where he played significant roles at companies like Capital One and Stripe, to the healthcare field. At Garner Health, he leads initiatives that leverage data analysis to guide employees in choosing quality healthcare providers. The discussion highlights the importance of utilizing modern data management techniques to improve healthcare outcomes, underscoring how data-driven approaches can enhance the quality of life for millions. Michi explains how the complexities of the US healthcare system, including regulation and privacy concerns, present unique challenges compared to the financial industry. The episode also touches on the evolution of healthcare data management and the need for modernization within healthcare organizations to keep up with technological advancements.Takeaways: Michi Kono transitioned from financial technology to healthcare to make a meaningful impact on people's lives. Garner Health utilizes data science to analyze medical outcomes and recommend quality healthcare providers. The healthcare industry is complex and unique, reflecting challenges in data access and integration compared to finance. Modern data management in healthcare is evolving, yet many systems still rely on outdated practices, slowing innovation. Healthcare startups face unique challenges but have opportunities to leverage new technologies for improved patient outcomes. Understanding data flow and machine learning basics is essential for future engineers in both healthcare and financial technology. Links referenced in this episode:softwarearchitectureinsights.comCompanies mentioned in this episode: Gartner Health Stripe Meta Capital One Snowflake Zocdoc EPIC Mentioned in this episode:What do 160,000 of your peers have in common?They've all boosted their skills and career prospects by taking one of my courses. Go to atchisonacademy.com.Atchison AcademyHow do you operate a modern organization at scale?Read more in my O'Reilly Media book "Architecting for Scale", now in its second edition. http://architectingforscale.com Architecting for Scale

  --------  

  31:14

  --------

  31:14

More Business podcasts

Trending Business podcasts

About Software Architecture Insights

Software Architecture Insights: Podcasts in Family