Software Architecture Insights

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.com

Companies mentioned in this episode:

• Amazon.com

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.com
• softwarearchitectureinsights.com

Companies mentioned in this episode:

• Upload Care
• Zillow

Please consider donating in order to keep this podcast...and other content by Lee Atchison...arriving in your inbox.

Please Donate Here

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.com

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.com

Companies mentioned in this episode:

• Gartner Health
• Stripe
• Meta
• Capital One
• Snowflake
• Zocdoc
• EPIC

The increasing use of AI in software development has led to significant changes in the industry, with 62% of developers now utilizing AI tools. While this has enhanced productivity, it has also resulted in greater code complexity and a decline in code quality. Recent findings from the 2025 GitClear AI Code Quality Research report reveal alarming trends: as AI usage rises, so does the duplication of code, leading to more time spent on refactoring rather than creating new code. This shift indicates a troubling pattern where the ability to manage and simplify complex systems is becoming more critical than simply writing new code. In this discussion, we will explore these challenges and the importance of maintaining high code quality in an AI-driven environment.

The landscape of software development has notably transformed in 2024, with 62% of developers now leveraging AI in their workflows. While this integration has significantly boosted productivity, it has also raised concerns regarding code quality and complexity. The discussion reflects on findings from the recent 2025 GitClear AI Code Quality Research report, which analyzed over 211 million lines of code and revealed a troubling trend: as AI usage increases, so does the complexity of software systems. Developers are now dedicating more time to refactoring existing code rather than creating new features. This shift highlights a critical issue in the industry: as AI generates more code, it often leads to duplication and violates the fundamental principle of not repeating oneself. Consequently, the reliance on AI tools may inadvertently increase maintenance challenges and bug vulnerability, requiring developers to adapt their roles and focus on system-level understanding and refactoring expertise to ensure sustainable software development practices.

Takeaways:

• In 2024, 62% of professional developers are using AI in their development process, significantly impacting productivity.
• The increased use of AI has led to more complex code and larger codebases, affecting overall code quality.
• Developers are now spending more time refactoring existing code rather than writing new features, which alters their workflow.
• The 2025 GitClear report shows a troubling rise in code duplication as AI-generated code becomes more common.
• AI coding tools struggle to understand the full context of projects, leading to increased code duplication and complexity.
• To address these challenges, organizations must focus on long-term maintainability, including reducing duplication and improving test coverage.

Links referenced in this episode:

• softwarearchitectureinsights.com
• 2025 GitClear AI Code Quality Research Report

That's right, the content you know and love from Software Architecture Insights will be available in podcast format for your on-the-go listening convenience. In addition, we will bring you interviews with industry movers and shakers that are changing the course of what it means to be a software architect and what it means to lead and drive a software development organization.

Topics include:

• The importance of AI as a tool to modern application architecture.
• Use of AI in designing, building, and operating modern applications at scale.
• Modern application security best practices and tools.
• Building and operating highly scaled SaaS and similar applications.
• Process and systems necessary to operate an application at scale.
• The importance of managing the complexity of your IT infrastructure and application ecosystem.

The podcast will be hosted by leading cloud and software architecture expert, Lee Atchison. Each episode will be in one of several formats:

• 1-1 discussion between Lee and leading technologists and industry experts on a variety of important, timely topics.
• A direct-to-listener conversation with Lee on a specific topic.
• Important industry news and current event important in this fast moving industry.

Whether interviewing a special guest, covering material from a recent article, or giving an update on a new industry trend, you will be able to depend on Lee for relevant, important content for software architects, technical software leaders, and lead developers alike.

Software Architeture Insights ‒ The Podcast, coming this fall.

Please consider donating in order to keep this podcast...and other content by Lee Atchison...arriving in your inbox.

Please Donate Here

Modern Digital Applications is changing and coming back after its year long hiatus. Join us for the launch of Modern Digital Business!

Modern Digital Business will be coming later this summer. If you'd like to be informed when it's ready to launch, please go to mdb.fm/launch.

We hope to see you there!

My guest today is Kevin Goslar. Kevin is the Senior Vice President for Technology Strategy at Originate, a digital agency that helps organizations with digital transformation best practices. He has a PhD in business informatics, and is an avid software developer. He currently is the maintainer for Git Town, an open-source project that provides a high-level CLI for Git. Previously, Kevin worked as a software developer at Google, which is where he was exposed to Mono-repos.

Kevin is a Git expert and process advocate, and he’s here to discuss with me the pros and cons of monorepos vs polyrepos. 

This is part 2 of my interview with Kevin.

My guest today is Kevin Goslar. Kevin is the Senior Vice President for Technology Strategy at Originate, a digital agency that helps organizations with digital transformation best practices. He has a PhD in business informatics, and is an avid software developer. He currently is the maintainer for Git Town, an open-source project that provides a high-level CLI for Git. Previously, Kevin worked as a software developer at Google, which is where he was exposed to Mono-repos.

Kevin is a Git expert and process advocate, and he’s here to discuss with me the pros and cons of monorepos vs polyrepos. 

My guest today is Beth Long. Beth worked at New Relic where she held roles in both engineering and marketing, including two years leading the Reliability Engineering team, which owned the tooling and process for incident response and analysis. She also led New Relic's collaboration with the SNAFU Catchers, a group of researchers in- vestigating how tech companies learn from incidents.

Beth recently left New Relic to join the startup Jeli.io, where she leads the engi- neering team working on the industry's first incident analysis platform.

Links

• Beth Long, Engineering Manager at Jeli.io
• LinkedIn: https://www.linkedin.com/in/beth-adele-long/
• Twitter: https://twitter.com/BethAdeleLong
• Featured in this episode: Jeli.io (https://jeli.io)
• Learning From Incidents with Jeli (https://leeatchison.com/atscale/2020/12/07/learning-from-incidents-with-jeli/)
• S3 Outage Mentioned in this Episode (https://thenewstack.io/dont-write-off-aws-s3-outage-fat-finger-folly/)