In Part I of this series, we explored how Collective Health implemented a micro-frontend architecture to make our internal applications easier to maintain. Here, we discuss the side effects of our solution.
One objective from the start was keeping the platform consistent and unified from the end user’s perspective. On the engineering side, that meant creating a library of shared, framework-agnostic layout and UI elements that would ensure consistent page layout with a header and optional navigation components. This was another great use case for Web Components.
When creating components with libraries like React or Angular, we are used to passing a lot of data and callbacks. But complex data structures, like arrays, objects, or functions, cannot be passed as attributes to web components (or any other HTML element). To solve this, we decided to split our components into multiple, purely presentational elements and rely on slots for inserting content into them, managing all state changes (e.g., selecting an active navigation item) from the child app itself. This solution had the added bonus of making our components very flexible (as apps might have different routing patterns) and resilient to future changes. …
Meet the Collective is our series highlighting the great people who make up Collective Health. Today, we’re sitting down with Ben Katz, VP of Network & Program Partners.
Where are you from?
I’m a lifelong Californian, starting out in West LA. Some 20 years ago, I moved to the East Bay Area for an exciting job opportunity, and the region has been home ever since.
What happened in your career that led you to Collective Health?
I was previously at an incumbent plan leading efforts to create network and benefits solutions for employers who were interested in a specific healthcare experience. I also worked at a large integrated medical group driving changes in how quality, cost efficiency, and the patient experience were achieved for a new business segment. In both cases, the status quo, institutional inertia, and fear of change all limited the scope of meaningful advancements at these organizations. I was drawn to Collective Health because it’s reimagining the full customer experience in ways more established organizations are unwilling or unable to pursue. …
This is a two-part series about creating applications for fast-growth companies that can evolve easily to support increasing complexity without degrading product quality.
In the business world, growth is good and means we’re doing something right. Apps get new features, capabilities, and content, and teams reorganize into more specialized focus areas. …