# Package Architecture Published articles for Package Architecture. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## One Substrate No Longer Rules Them All DevFeed: [One Substrate No Longer Rules Them All]() Original publisher: [Read original article]() Author: Gregory Haley Published: 2026-09-28T07:01:09Z Content type: article Language: en Sources: [Semiconductor Engineering]() Topics: [Chip design](), [AI Infrastructure]() Tags: [advanced-packaging](), [amkor](), [applied-materials](), [brewer-science](), [bridges](), [capacity](), [chip](), [chiplets](), [executive](), [glass-substrates](), [intel-foundry](), [interconnect](), [interposers](), [lam-research](), [layers](), [limits](), [manufacturing-packaging-and-materials](), [matching](), [material](), [materials](), [mitsubishi-chemical-group](), [osats](), [package-architecture](), [power-delivery](), [prismark](), [process](), [scaling](), [semiconductor](), [server](), [servers](), [shinko-electric](), [silicon](), [substrates](), [synopsys](), [top-stories]() ### AI overview Advanced package substrates are becoming application-specific as larger package bodies, more layers, finer routing, and embedded functions raise capability requirements. In AI and server packages, rising substrate value reflects greater material use and structure, while capacity alone does not ensure a supplier can meet a package's materials, dimensions, and process limits. ### Source excerpt Larger packages, finer routing, and embedded functions are pushing advanced substrates toward application-specific designs. The post One Substrate No Longer Rules Them All appeared first on Semiconductor Engineering. ## Ep. 3: Mastering Kubernetes: Setting Up Environments with Kind DevFeed: [Ep. 3: Mastering Kubernetes: Setting Up Environments with Kind]() Original publisher: [Read original article]() Published: 2024-05-28T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Kubernetes](), [Learning](), [developer setup](), [Network](), [software-development]() Tags: [asynchronous](), [cli](), [code-modularity](), [compute-resources](), [cpu](), [deployments](), [development-environment](), [docker](), [go](), [go-development](), [go-projects](), [kind](), [kubernetes](), [kubernetes-architecture](), [kubernetes-cluster](), [memory](), [node](), [package-architecture](), [pod](), [pods](), [software-design](), [ultimate-software-design-series]() ### AI overview Bill explains Kubernetes clusters, nodes, and pods, then demonstrates creating a single-node development cluster with kind and allocating CPU and memory through Docker settings. He covers running a service in a pod, setting pod resource quotas, configuring service networking, and using the kube-control CLI and Customize to manage deployments and monitor their asynchronous progress. The excerpt also describes live troubleshooting demonstrations, but does not specify the commands or configuration details. ### Source excerpt Introduction: In this installment of the Ultimate Software Design series, Bill guides us through setting up a Kubernetes environment using Kubernetes inside Docker (kind). He breaks down the structure of Kubernetes and offers insights into effective cluster management, ensuring a robust and efficient development environment. Effective Cluster Management: Learn the basics of setting up and managing a Kubernetes cluster, essential for maintaining scalable and resilient Go applications. Pod and Node Configuration: Understand how to configure pods and nodes to optimize compute resources and ensure seamless application deployment. ## Ep. 2: Elevating Software Design in Go: Package Architecture in Modern Development DevFeed: [Ep. 2: Elevating Software Design in Go: Package Architecture in Modern Development]() Original publisher: [Read original article]() Published: 2024-05-21T00:00:00Z Content type: article Language: en Sources: [William Kennedy]() Topics: [Code Modularity](), [system-design-project](), [software-architecture](), [Maintainability](), [Software Engineering]() Tags: [architecture](), [code](), [code-modularity](), [components](), [design](), [designing](), [developers](), [development](), [firewalls](), [functionality](), [go](), [go-development](), [go-projects](), [maintainability](), [modularity](), [package](), [package-architecture](), [package-design](), [packages](), [pitfalls](), [software](), [software-design]() ### AI overview Bill explains that Go packages create boundaries between program components through encapsulation and modularity, supporting organization and reuse. He recommends packages with focused functionality and warns that generic "Utils" or "Common" packages can weaken code integrity, increase dependencies, and hurt maintainability. The excerpt also introduces a "flipping pyramid" as a caution about monolithic codebases and raises robust type systems as relevant to code integrity and efficiency, without detailing either topic. ### Source excerpt Introduction: In this insightful episode, Bill dives deep into the realm of package design, shedding light on its crucial role in software development. Here are three key takeaways for Go developers: Code Modularity: Learn how Go's packaging system creates essential firewalls between program components, enhancing maintainability. Focused Functionality: Discover the importance of designing packages that provide specific functionality, fostering code clarity. Avoiding Pitfalls: Bill warns against common package design mistakes like centralized "common" packages, promoting a layered approach to maintainable code.