--- title: adam bien's blog | daily.dev description: Business components (BCs) are top-level packages named after a single responsibility or feature rather than a technology layer. This approach, known as... canonical: https://daily.dev/posts/adam-bien-s-blog-iydrezxtr twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: adam bien's blog | daily.dev og:description: Business components (BCs) are top-level packages named after a single responsibility or feature rather than a technology layer. This approach, known as... og:url: https://daily.dev/posts/adam-bien-s-blog-iydrezxtr og:image: https://api.daily.dev/og/posts/IydrEzxtR.png og:image:alt: adam bien's blog og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # adam bien's blog **[Adam Bien](https://daily.dev/sources/adam-bien)** · 2 min read · 0 upvotes · 0 comments ## Summary Business components (BCs) are top-level packages named after a single responsibility or feature rather than a technology layer. This approach, known as Screaming Architecture, makes a system's purpose immediately readable from its package names. BCs are not designed upfront but emerge organically as new requirements arise. The zero-dependency Java builder 'zb' illustrates this: requirements for finding source code, compiling, packaging, and running post-build hooks each became their own component — discovery, compiler, packer, and hook — making the system's structure self-documenting. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is a business component in screaming architecture? A business component is a top-level package named after a single responsibility or feature rather than a technology layer, so reading the package names reveals what the system does. Examples include discovery, compiler, packer, and hook, the components that make up the zb zero-dependency Java builder. These components are not designed upfront but created incrementally as new requirements appear. _daily.dev surfaces architecture discussions like this for developers refining their own package structure._ ### How should I name a top-level package for a business component? A business component name should be short and descriptive, avoiding both compound names and cryptic abbreviations. For example, the JAR-creation component in the zb builder was first called 'jar creator' (too long), then 'jc' (too cryptic), before settling on 'packer'. The goal is a name a reader instantly understands without decoding context. _Developers debating package naming conventions can find similar architecture perspectives on daily.dev._ ## Similar posts on daily.dev - [Clean Architecture Explained: Building Software That Stands the Test of Time](https://daily.dev/posts/clean-architecture-explained-building-software-that-stands-the-test-of-time-acdblphuf) · Medium · 1 upvotes · 0 comments - [How Composable Architecture Accelerates Marketplace Time-to-Market](https://daily.dev/posts/how-composable-architecture-accelerates-marketplace-time-to-market-gapniyytj) · Netguru · 0 upvotes · 0 comments - [No, Your Domains and Bounded Contexts Don’t Map 1 on 1](https://daily.dev/posts/no-your-domains-and-bounded-contexts-don-t-map-1-on-1-rh3kxenlx) · Mathias Verraes · 0 upvotes · 0 comments - [From Java EE to Quarkus and LLMs: Adam Bien’s Playbook for Boring, Future‑Proof Systems](https://daily.dev/posts/from-java-ee-to-quarkus-and-llms-adam-bien-s-playbook-for-boring-future-proof-systems-0metu7xbn) · InfoQ · 16 upvotes · 0 comments - [Most teams put low-level architecture in the wrong place](https://daily.dev/posts/most-teams-put-low-level-architecture-in-the-wrong-place-5xi6noby2) · ITNEXT · 3 upvotes · 2 comments --- Tags: [#java](https://daily.dev/tags/java), [#architecture](https://daily.dev/tags/architecture), [#domain-driven-design](https://daily.dev/tags/domain-driven-design) [View this post on daily.dev](https://daily.dev/posts/adam-bien-s-blog-iydrezxtr) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"adam bien's blog","url":"https://daily.dev/posts/adam-bien-s-blog-iydrezxtr","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/adam-bien-s-blog-iydrezxtr"},"datePublished":"2026-07-24T06:38:10.197Z","dateModified":"2026-09-13T19:29:03.415Z","description":"Business components (BCs) are top-level packages named after a single responsibility or feature rather than a technology layer. This approach, known as...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/d365e8cabb5d95ba36aaa092c23f211d?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/d365e8cabb5d95ba36aaa092c23f211d?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Adam Bien","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Adam Bien","logo":"https://media.daily.dev/image/upload/s--CInnAL-q--/f_auto,q_auto/v1773644276/logos/adam-bien?_a=BAMAMiiu0","url":"https://daily.dev/sources/adam-bien"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/adam-bien-s-blog-iydrezxtr","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"java,architecture,domain-driven-design","timeRequired":"PT2M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Adam Bien","item":"https://daily.dev/sources/adam-bien"},{"@type":"ListItem","position":3,"name":"adam bien's blog"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/adam-bien-s-blog-iydrezxtr#faq","mainEntity":[{"@type":"Question","name":"What is a business component in screaming architecture?","acceptedAnswer":{"@type":"Answer","text":"A business component is a top-level package named after a single responsibility or feature rather than a technology layer, so reading the package names reveals what the system does. Examples include discovery, compiler, packer, and hook, the components that make up the zb zero-dependency Java builder. These components are not designed upfront but created incrementally as new requirements appear. daily.dev surfaces architecture discussions like this for developers refining their own package structure."}},{"@type":"Question","name":"How should I name a top-level package for a business component?","acceptedAnswer":{"@type":"Answer","text":"A business component name should be short and descriptive, avoiding both compound names and cryptic abbreviations. For example, the JAR-creation component in the zb builder was first called 'jar creator' (too long), then 'jc' (too cryptic), before settling on 'packer'. The goal is a name a reader instantly understands without decoding context. Developers debating package naming conventions can find similar architecture perspectives on daily.dev."}}]} ```