# Design Patterns Published articles for Design Patterns. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 15 Common Software Design Patterns Explained with Java Examples DevFeed: [15 Common Software Design Patterns Explained with Java Examples]() Original publisher: [Read original article]() Author: Ashish Pratap Singh Published: 2026-08-25T04:01:49Z Content type: tutorial Language: en Sources: [AlgoMaster Newsletter]() Topics: [Architecture & Design](), [Software Engineering](), [Java](), [Programming]() Tags: [article](), [code](), [design](), [design-patterns](), [java](), [programming](), [software-design]() ### AI overview This tutorial explains 15 commonly used software design patterns, covering their categories and practical use cases. It uses Java code examples and discusses patterns including Singleton, Builder, and Factory Method, along with cautions about global access and hidden dependencies. ### Source excerpt In this article, I'll break down 15 of the most important design patterns I've come across in interviews and throughout my 9+ years as a Software Engineer. ## Modular Monoliths: Creating Real Boundaries Before Reaching for Microservices DevFeed: [Modular Monoliths: Creating Real Boundaries Before Reaching for Microservices]() Original publisher: [Read original article]() Author: Freek Van der Herten (freek@spatie.be) Published: 2026-08-20T13:48:25Z Content type: article Language: en Sources: [freek.dev - all blogposts]() Topics: [Architecture & Design](), [Microservice](), [Database]() Tags: [apis](), [architecture](), [database](), [design-patterns](), [microservices](), [migration](), [modular](), [monolith](), [tests]() ### AI overview This article examines modular monoliths as a way to establish real architectural boundaries before adopting microservices. It covers module APIs, database ownership, cross-module communication, architecture tests, incremental migration, and signals that may justify a move to microservices. ### Source excerpt A deep dive into modular monoliths, from module APIs and database ownership to cross-module communication, architecture tests, incremental migration, and the signals that justify microservices. Read more ## Immutability in PHP Beyond readonly DevFeed: [Immutability in PHP Beyond readonly]() Original publisher: [Read original article]() Author: Freek Van der Herten (freek@spatie.be) Published: 2026-08-17T12:12:30Z Content type: article Language: en Sources: [freek.dev - all blogposts]() Topics: [PHP]() Tags: [best-practices](), [deep-dive](), [design-patterns](), [immutability](), [php](), [properties](), [value](), [value-objects]() ### AI overview A deep dive into immutability in PHP, covering readonly properties, interior mutability, immutable value objects and collections, dates, cloning, boundaries, and testing. ### Source excerpt A deep dive into immutability in PHP, from readonly properties and interior mutability to immutable value objects, collections, dates, cloning, boundaries, and testing. Read more ## No, People Don't Want More AI In Their Life DevFeed: [No, People Don't Want More AI In Their Life]() Original publisher: [Read original article]() Author: hello@smashingmagazine.com (Vitaly Friedman) Published: 2026-07-15T10:00:00Z Content type: opinion Language: en Sources: [Articles on Smashing Magazine -- For Web Designers And Developers]() Topics: [Artificial Intelligence](), [User experience (UX)](), [systems]() Tags: [ai](), [data-quality](), [design](), [design-patterns](), [hallucinations](), [systems](), [ux]() ### AI overview The article argues that people generally do not want more AI when it arrives as disconnected features, separate tools, or imposed workflows. It links low adoption and retention to high delivery costs, reputation risks, fragmented systems, technical debt, poor data quality, and the effort required to check and correct AI-generated output. It also describes resistance and anxiety connected to fears that AI may replace work. ### Source excerpt Many companies assume everyone craves new AI features. But the reality is that most people don't want more AI -- at least not in the way most AI leaders envision it. Brought to you by Design Patterns For AI Interfaces, **friendly video courses on UX** and design patterns by Vitaly. ## 7 of the best AI-powered website builders for 2026 DevFeed: [7 of the best AI-powered website builders for 2026]() Original publisher: [Read original article]() Author: Webflow Team Published: 2026-07-14T00:00:00Z Content type: comparison Language: en Sources: [Webflow Blog]() Topics: [Artificial Intelligence](), [Web](), [web design](), [Content Management System](), [Scalability](), [User Experience](), [hosting]() Tags: [ai](), [design](), [design-patterns](), [digital-experiences](), [features](), [generate](), [guide](), [hosting](), [how-to](), [integrations](), [launch](), [platform](), [scalability](), [user-experience](), [web](), [web-design](), [website-builders]() ### AI overview A comparison of seven AI-powered website builders for 2026, covering ease of use, features, applications, design quality, scalability, content management, hosting, and the role of human review. ### Source excerpt Compare seven of the best AI-powered website builders for 2026. Learn about their ease of use, key features, and applications, then choose the right fit. ## Making ServiceLoader usable: a provider factory DevFeed: [Making ServiceLoader usable: a provider factory]() Original publisher: [Read original article]() Author: Stefano Fago Published: 2026-07-12T00:00:00Z Content type: tutorial Language: en Sources: [Nicolas Fränkel]() Topics: [Java](), [Code](), [JSON Web Tokens](), [JSON]() Tags: [decoupling](), [design-patterns](), [java](), [json](), [jwt](), [plugin](), [plugins](), [serviceloader](), [spi]() ### AI overview This article presents a provider-factory pattern for Java ServiceLoader. Instead of loading a service implementation directly, ServiceLoader loads a small factory with a no-argument constructor; the factory then constructs the service and can support implementation selection and custom constructors. The pattern is illustrated with a mock payments system and is related to decoupling JSON and JWT capabilities from concrete libraries. ### Source excerpt I keep coming back to java.util.ServiceLoader. I have used it to put a JSON layer behind a contract, so the core code carries no direct dependency on any particular JSON library, and I can swap the implementation without touching callers. The same shape works for JWT handling, where the concrete library might be jose4j or another JOSE implementation, and you can easily find other decoupling use-cases. ## Users Don't Need More Tools: They Need Seamless Integrations DevFeed: [Users Don't Need More Tools: They Need Seamless Integrations]() Original publisher: [Read original article]() Author: hello@smashingmagazine.com (Vitaly Friedman) Published: 2026-07-03T13:00:00Z Content type: article Language: en Sources: [Articles on Smashing Magazine -- For Web Designers And Developers]() Topics: [User experience (UX)](), [Artificial Intelligence](), [anthropic](), [Microsoft]() Tags: [ai](), [claude](), [design](), [design-patterns](), [integrations](), [mental-models](), [microsoft](), [ux](), [workflow]() ### AI overview The article argues that users need seamless integrations of useful capabilities rather than more standalone tools. It contrasts disruptive "AI-first" products with "Quiet AI," which works unobtrusively within existing workflows and mental models, and presents folder instructions as a way to automate context-specific file tasks. ### Source excerpt A closer look at why users don't need more tools in their daily lives. What they need are seamless integrations of useful features to match already existing, established mental models. Brought to you by Design Patterns For AI Interfaces, **friendly video course on UX** and design patterns by Vitaly. ## How do you turn AI coding chaos into a repeatable playbook? DevFeed: [How do you turn AI coding chaos into a repeatable playbook?]() Original publisher: [Read original article]() Author: Eira May Published: 2026-07-02T07:40:00Z Content type: article Language: en Sources: [Stack Overflow Blog]() Topics: [AI-assisted coding](), [ci](), [incident]() Tags: [agents](), [ai](), [ai-coding](), [best-practices](), [business](), [design-patterns](), [engineering-leadership](), [incident-response](), [leaders-of-code](), [podcast](), [testing]() ### AI overview A podcast discussion of Snowflake's five-stage approach to making AI-assisted engineering repeatable across an organization. It covers coding-agent design patterns, adoption practices, validation automation, and a proposed maturity model for on-call and incident response. ### Source excerpt Vivek Raghunathan, SVP of engineering at Snowflake, joins Leaders of Code at Snowflake Summit to break down the five-stage framework his org used to go from "let chaos reign" to a repeatable, org-wide system for AI-assisted engineering. ## How To Make Your Design System AI-Ready DevFeed: [How To Make Your Design System AI-Ready]() Original publisher: [Read original article]() Author: hello@smashingmagazine.com (Vitaly Friedman) Published: 2026-06-03T13:00:00Z Content type: tutorial Language: en Sources: [Articles on Smashing Magazine -- For Web Designers And Developers]() Topics: [User interface design](), [AI-assisted coding](), [Figma]() Tags: [accessibility](), [ai](), [code](), [design](), [design-patterns](), [design-systems](), [documentation](), [guide](), [how-to](), [prototypes](), [ux]() ### AI overview A practical guide to making design systems more reliable inputs for AI-generated prototypes. It recommends documenting decisions in reusable spec files, maintaining a token layer, and auditing design-system quality with FigmaLint. ### Source excerpt Practical guide on how to reduce drifts, minimize mistakes, maintain context, and improve the quality of AI-generated prototypes. Brought to you by Design Patterns For AI Interfaces, **friendly video course on UX** and design patterns by Vitaly. ## Four Levels Of Customer Understanding DevFeed: [Four Levels Of Customer Understanding]() Original publisher: [Read original article]() Author: hello@smashingmagazine.com (Vitaly Friedman) Published: 2026-05-22T13:00:00Z Content type: article Language: en Sources: [Articles on Smashing Magazine -- For Web Designers And Developers]() Topics: [User experience (UX)](), [data]() Tags: [customer](), [design](), [design-patterns](), [ux]() ### AI overview The article presents four levels of customer understanding for uncovering the reasons behind user behavior. It argues that what people say, feel, think, and do can differ substantially, so teams should look beyond direct answers and surface opinions to investigate hidden motivations, root causes, and behavioral evidence. ### Source excerpt What people say, feel, think, and do are often very different things. To understand the underlying reasons for user behavior, it helps to look beyond the surface and explore hidden motivations, root causes, and the different layers of reality that shape how people act. Brought to you by Measuring UX Impact, **friendly video course on UX** and design patterns by Vitaly. ## Deploying cloud-based engineering workbenches with the Virtual Engineering Workbench on AWS DevFeed: [Deploying cloud-based engineering workbenches with the Virtual Engineering Workbench on AWS]() Original publisher: [Read original article]() Author: Andrea Meroni Published: 2026-04-21T21:38:49Z Content type: tutorial Language: en Sources: [AWS Open Source Blog]() Topics: [Deployment](), [Embedded Software Dev](), [Amazon API Gateway](), [Domain-driven design (DDD)](), [Authorization]() Tags: [amazon-api-gateway](), [amazon-dynamodb](), [amazon-eventbridge](), [aws](), [aws-lambda](), [cloud](), [deployment](), [design-patterns](), [embedded](), [open-source](), [react](), [serverless]() ### AI overview A tutorial for deploying the open-source Virtual Engineering Workbench on AWS. It describes a self-service platform for publishing and provisioning preconfigured development environments, its serverless architecture, and creating and launching a workbench. ### Source excerpt Introduction Organizations in automotive, manufacturing, and embedded systems increasingly rely on cloud-based development environments to reduce hardware dependency and accelerate software delivery. As vehicle architectures shift toward software-defined platforms, engineering teams need access to specialized toolchains, virtual hardware models, and simulation environments that are consistent across sites and reproducible across projects. Provisioning these environments manually [...] ## The Illusion of Choice: How Micro-Decisions Guide Macro-Control DevFeed: [The Illusion of Choice: How Micro-Decisions Guide Macro-Control]() Original publisher: [Read original article]() Author: Tushar Deshmukh Published: 2026-04-21T06:23:51Z Content type: opinion Language: en Sources: [UX Magazine]() Topics: [User experience (UX)](), [Usability](), [User interface design](), [A/B Testing]() Tags: [a-b-testing](), [article](), [design-patterns](), [interfaces](), [usability](), [ux]() ### AI overview This article examines how small interface decisions can influence user behavior and create an illusion of choice. It argues that choice architecture, including button prominence, wording, navigation order, and default states, can steer users toward predetermined outcomes, and calls for UX practices that balance usability with responsibility. ### Source excerpt Part 8 of the "Ethical UX Series." "The greatest enemy of freedom is a happy slave." -- Friedrich von Schiller What is "ethical UX," and why this series matters In the design world, we often speak about empathy, innovation, and delight. But underneath the surface of many successful interfaces lies a subtle, often unchecked force The post The Illusion of Choice: How Micro-Decisions Guide Macro-Control appeared first on UX Magazine. ## Multi-Tenant Billing Architecture: Design Patterns for SaaS DevFeed: [Multi-Tenant Billing Architecture: Design Patterns for SaaS]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-04-15T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Architecture & Design](), [Multi-tenancy](), [Software as a service](), [event driven]() Tags: [architecture](), [design-patterns](), [event-driven](), [multi-tenancy](), [saas](), [saas-billing](), [usage-based-billing]() ### AI overview A guide to designing billing systems for multi-tenant SaaS applications. It compares centralized billing services, event-driven pipelines, and external billing platforms, and discusses product catalogs, subscription management, usage metering, tenant isolation, and build-versus-buy decisions. ### Source excerpt Design patterns for building multi-tenant billing systems in SaaS. Covers tenant isolation, metering, event-driven billing, and when to build vs buy billing infrastructure. ## Sharing ViewModels Across Android and iOS in Kotlin Multiplatform Projects DevFeed: [Sharing ViewModels Across Android and iOS in Kotlin Multiplatform Projects]() Original publisher: [Read original article]() Published: 2026-03-02T00:00:00Z Content type: opinion Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [MVVM](), [multiplatform](), [Mobile](), [android-development](), [Compose]() Tags: [android](), [architecture](), [compose](), [design-patterns](), [ios](), [kmp](), [kotlin-multiplatform](), [multiplatform](), [mvvm](), [viewmodel]() ### AI overview This article explains the MVVM pattern and examines how sharing ViewModels across Android and iOS affects developer experience in Kotlin Multiplatform projects. It discusses separation of concerns, binders, Compose, SKIE, and Android ViewModel lifecycle behavior, including configuration changes. ### Source excerpt Sharing ViewModels between platforms affects the iOS developer experience. In this post we will discuss this topic and some possible solutions in KMP projects that respect the native feel of iOS and Android. ## What Should Repositories Return in Domain-Driven Design? DevFeed: [What Should Repositories Return in Domain-Driven Design?]() Original publisher: [Read original article]() Author: Furkan Kolcu Published: 2025-09-09T16:41:47Z Content type: article Language: en Sources: [Furkan Kolcu - Software Engineer Blog]() Topics: [Domain-driven design (DDD)](), [Repositories](), [Persistence]() Tags: [aggregates](), [clean-architecture](), [design-patterns](), [domain-driven-design](), [domain-driven-design-ddd](), [examples](), [lightweight](), [practical](), [repositories](), [repository-pattern](), [software-architecture](), [software-engineering](), [technology]() ### AI overview This article examines what repositories should return in Domain-Driven Design. It compares aggregates, DTOs or arrays, and primitives or special results, concluding that repositories should return aggregates when domain behavior is needed and primitives when they express valid domain-level answers. ### Source excerpt Repositories are a core part of Domain-Driven Design, but what they should return is often debated. Should it be aggregates, DTOs, or simple values? In this post, I share practical guidelines, examples, and tradeoffs to help clarify how to keep repositories focused on serving the domain. ## Design Patterns Are Everywhere in Laravel. The Artisan of the Day Is Mary Perry. DevFeed: [Design Patterns Are Everywhere in Laravel. The Artisan of the Day Is Mary Perry.]() Original publisher: [Read original article]() Author: Ana Tavares Published: 2025-08-07T12:49:56Z Content type: article Language: en Sources: [Laravel Blog]() Topics: [Laravel](), [Code](), [Dependency injection](), [Databases]() Tags: [architecture](), [code](), [community](), [database](), [dependency-injection](), [design-patterns](), [developer](), [ecosystem](), [framework](), [laravel]() ### AI overview This Laravel article profiles Mary Perry and her Laracon talk about the design patterns embedded in Laravel's architecture. It describes singleton and factory patterns, facades as encapsulation, dependency injection through the service container, and the builder pattern in the middleware pipeline. ### Source excerpt When it comes to finding the poetry hidden in Laravel's architecture, Mary Perry sees what others miss. ## Now in Android #117 -- Google I/O 2025 Part I DevFeed: [Now in Android #117 -- Google I/O 2025 Part I]() Original publisher: [Read original article]() Author: Daniel Galpin Published: 2025-06-05T17:28:56Z Content type: article Language: en Sources: [Android Developers - Medium]() Topics: [Android](), [Material Design](), [Development](), [Google](), [Artificial Intelligence](), [Android XR](), [Large Screen](), [User experience (UX)]() Tags: [2025](), [adaptive](), [ai](), [android](), [android-16](), [android-xr](), [design-patterns](), [development](), [featured](), [gemini](), [google](), [google-i-o](), [google-io-2025](), [material-design](), [now-in-android](), [ux]() ### AI overview This first part of a special Google I/O 2025 edition of Now in Android surveys updates across Material Design, Android form factors, adaptive app development, Android XR, on-device and cloud-based AI, and Android 16. It highlights Material 3 Expressive, including new motion physics, typography, shapes, colors, and component configuration capabilities. ### Source excerpt Now in Android #117 -- Google I/O 2025 Part IDesign, Watches, Cars, Tablets, Adaptive Apps, Android XR, Gemini, and Android 16 Welcome to part one of a special two-part Google I/O 2025 edition of Now in Android. This first post will cover a bunch of changes related to the latest evolution of Material Design, watches, cars, tablets, laptops, and connected displays, the latest in adaptive app development, XR development, how to take advantage of on-device and cloud based AI, and Android 16. https://medium.com/media/f4779f9096112bf2cfff21aec7eeb199/hrefhttps://medium.com/media/d23b17afda66e01541bb4c84ecea4974/href Most of the content of this post is available in the form of a video or podcast, so feel free to watch or listen rather than read on. (Or do all three to help you remember! There won't be a quiz.) The Android Show: I/O Edition -- what Android devs need to know! 🤖 We began the I/O season with a special edition of The Android Show, where we introduced the latest evolution of Material Design, Material 3 Expressive. https://medium.com/media/815112dc9a5b3a849cced5343837f4e6/href The Android Show: I/O Edition - what Android devs need to know! https://medium.com/media/906cc031e2cbb814b2a4964db156a2cc/href Material 3 Expressive adds a new motion physics system, new type styles for variable and static fonts, an expanded shape library with morphing animations, and an expanded range of colors. Fifteen new or updated components now feature more configuration capabilities, shape options, emphasized text, and other expressive updates. The Material team has a post where you can read all about it, including design tactics. M3 Expressive: Engaging UX Design At I/O Build next-level UX with Material 3 Expressive covered how to use the new expressive design patterns; breaking down the research, explaining new guidelines, and including new design files + code. https://medium.com/media/4ce31edc8b396f71acc6192d1ac6160f/href The first beta of the Q3 Android 16 update contains much of ## The Role and Responsibilities of a Software Architect DevFeed: [The Role and Responsibilities of a Software Architect]() Original publisher: [Read original article]() Author: LucaVaccaDeveloper Published: 2025-02-18T09:18:07Z Content type: opinion Language: en Sources: [Backend Job: skill, salary and insights - Codemotion Magazine]() Topics: [Architecture & Design](), [Development](), [Programming]() Tags: [architecture](), [design-patterns](), [development](), [docker](), [kubernetes](), [microservices](), [programming](), [software-architecture]() ### AI overview This commentary examines the role of the software architect, comparing it with a structural engineer in construction. It argues that software architecture is often handled by senior developers rather than dedicated architects, and describes the architect's responsibilities, including designing robust and scalable systems, understanding business and client needs, evaluating technologies, and working with architectural patterns, databases, cloud services, and containers. ### Source excerpt Making an analogy with the construction world, there's always a structural engineer in the design phase who is responsible for calculating and defining the necessary foundations for the work before building a structure. This practice is not only logical but fundamental: you cannot build a house or a building without considering its architecture or the... Read more The post Software Architect: A Mythological Figure? appeared first on Codemotion Magazine. ## Announcing a new operation: Workflow Update DevFeed: [Announcing a new operation: Workflow Update]() Original publisher: [Read original article]() Author: Dan Davison Published: 2025-01-14T00:00:00Z Content type: release Language: en Sources: [Temporal Blog]() Topics: [async](), [reliability](), [Low Latency]() Tags: [announce](), [async](), [asynchronous](), [blog](), [blog-post](), [design-patterns](), [error](), [product-news](), [reliability](), [update](), [workflow]() ### AI overview Temporal announces that Workflow Update is generally available. The operation lets clients send a message to a Workflow, wait for handling to complete, and receive a result or error. The article explains how Update differs from Queries and Signals, demonstrates executing Activities, and discusses validators and design patterns. ### Source excerpt Discover the latest workflow update designed to simplify operations and boost reliability in Temporal. ## Object-Oriented Programming in Kotlin DevFeed: [Object-Oriented Programming in Kotlin]() Original publisher: [Read original article]() Published: 2024-05-22T00:00:00Z Content type: tutorial Language: en Sources: [Kodeco | High quality programming tutorials: iOS, Android, Swift, Kotlin, Unity, and more]() Topics: [Kotlin](), [Programming](), [Code]() Tags: [best-practices](), [code](), [course](), [design-patterns](), [developers](), [kotlin](), [learn](), [programming]() ### AI overview A course module on writing good object-oriented code in Kotlin, covering best practices and introducing design patterns. ### Source excerpt Learning to write code is easy, but learning to write "good" code is a different story entirely. In this course, developers will learn best practices when writing object-oriented code as well as be introduced to design patterns. ## Keeping the codebase consistent with Pattern Parties DevFeed: [Keeping the codebase consistent with Pattern Parties]() Original publisher: [Read original article]() Author: Kelsey Mills Published: 2023-10-03T13:15:49Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [Code](), [Refactoring]() Tags: [blog-post](), [code](), [design-patterns](), [engineering](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [outage](), [post-mortem](), [refactoring](), [slack-incident]() ### AI overview The article describes Pattern Parties, a focused, team-wide practice at incident.io for synchronizing diverging design patterns across a codebase. These two-day sessions update pattern documentation, improve consistency, and help engineers learn and internalize the patterns while managing migration work in manageable increments. ### Source excerpt As a codebase evolves, it's common to see some divergence in the design patterns within it. ## Workflows as Actors: Is it really possible? DevFeed: [Workflows as Actors: Is it really possible?]() Original publisher: [Read original article]() Author: Fitz Published: 2023-06-27T22:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [Actor](), [systems](), [Object-oriented programming (OOP)](), [Complex Systems]() Tags: [actor](), [blog-post](), [concurrent](), [design-patterns](), [object-oriented](), [parallel](), [temporal-concepts](), [workflows]() ### AI overview This article introduces the Actor Model and compares actors with objects, focusing on message passing, state, actor creation, and encapsulation. It then explains how Temporal Workflows can be built to behave like actors. ### Source excerpt An overview on how to use Temporal Workflows in the form of an Actor Model ## Scaling Teams Mobile Development -- The Mental Model DevFeed: [Scaling Teams Mobile Development -- The Mental Model]() Original publisher: [Read original article]() Author: Anand Nath Published: 2023-03-03T02:22:43Z Content type: article Language: en Sources: [Android@Microsoft - Medium]() Topics: [Mobile](), [Development](), [App](), [Code](), [interfaces]() Tags: [android](), [code](), [design-patterns](), [development](), [integration](), [interfaces](), [ios](), [mobile](), [mobile-development](), [modularization](), [patterns]() ### AI overview This article presents a mental model for scaling partner integrations in the Microsoft Teams mobile codebase. It describes the existing tight coupling between feature producers and consumer entry points, then proposes decoupling them through interfaces, a producer registry, and a manager that handles feature discovery and coordination. ### Source excerpt Scaling Teams Mobile Development -- The Mental Model In the article Scaling Teams Mobile Development -- Evolving the design pattern we explored how multiple partner teams working on a large code base can be streamlined by employing the contributor design pattern. I decided to write this article as a prequel. In this article we will discuss the problem statement in a more generic way and draw some parallels with popular design patterns. Photo by Xavi Cabrera on Unsplash We started with the following mission statement in mind: Make partner integrations with Teams mobile easier, well segregated, with clear protocols. Teams is a complex mobile application with a LOT of integration points. Partner teams surface their features through these entry points. The following image highlight few entry points available in Teams. Few entry points in Teams mobile app When we looked at the partner integration story in Teams codebase, it became evident that the whole integration story is a Producer-Consumer design pattern which is not implemented correctly. Producer -- Consumer deep coupling Here is the mental model that we built: Entry points are consumers of features and partner teams are producers of features. In the existing method, each partner team directly integrated with the entry point. This meant each consumer had to know the producers directly and when a new producer was added, the consumer had to be updated. This resulted in tight coupling. This is not a scalable model. N x N relationship between Producers and Consumers For the system to scale we need to decouple the producers and the consumers and build strong contracts between them. We wanted to safeguard changes to the consumer. At the same time, we wanted to make the producers independent and able to churn out their features fast. We also wanted to centralize control on producers and its features for deciding their ordering, filtering, enablement etc. So, we evolved this design pattern, where we define multiple Feature in ## Week of Java: Part 4 - A Multi-layer Core for Your Function DevFeed: [Week of Java: Part 4 - A Multi-layer Core for Your Function]() Original publisher: [Read original article]() Author: Juan Sebastián Urrego Escobar Published: 2022-05-12T00:00:00Z Content type: tutorial Language: en Sources: [Serverless Blog]() Topics: [Java](), [Code](), [configuration](), [Microservice]() Tags: [architecture](), [aws](), [aws-lambda](), [cloud-computing](), [code](), [configuration](), [design-patterns](), [engineering](), [faas](), [function-as-a-service](), [infrastructure-as-code](), [java](), [patterns](), [serverless](), [serverless-architecture](), [serverless-framework]() ### AI overview Part 4 of a five-part Java series begins implementing a function architecture in code and configuration, using design patterns and a Function as a Microservice style. ### Source excerpt Part 4 of 5 with our series and its time to start implementing our architecture in code and configuration using some appropriate design patterns and following a Function as a Microservice style. [Next page]()