<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Justin Menestrina on Medium]]></title>
        <description><![CDATA[Stories by Justin Menestrina on Medium]]></description>
        <link>https://medium.com/@jmenestr?source=rss-6fb66f8ada6d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*8kY_JbEj9iY8rMe5keKxxg.jpeg</url>
            <title>Stories by Justin Menestrina on Medium</title>
            <link>https://medium.com/@jmenestr?source=rss-6fb66f8ada6d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 08:42:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jmenestr/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Moving our Guild SPAs from Heroku to AWS]]></title>
            <link>https://medium.com/extra-credit-by-guild/moving-our-guild-spas-from-heroku-to-aws-a0ae5973975b?source=rss-6fb66f8ada6d------2</link>
            <guid isPermaLink="false">https://medium.com/p/a0ae5973975b</guid>
            <category><![CDATA[single-page-applications]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[frontend-architecture]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[software-architecture]]></category>
            <dc:creator><![CDATA[Justin Menestrina]]></dc:creator>
            <pubDate>Thu, 01 Oct 2020 19:06:36 GMT</pubDate>
            <atom:updated>2020-10-01T19:06:36.380Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Migrating Single-Page Applications from Heroku to AWS</strong></h3><p>In the second quarter of 2020, Guild Education began transitioning our Single-Page Application (SPA) hosting stack from Heroku over to AWS. For us, SPAs were only the first major step in migrating all of our deployment infrastructure to the new platform. We chose AWS, despite several robust and fully-featured alternatives like Heroku and Netlify, for the following reasons:</p><ul><li><strong>Cost. </strong>When Guild started in 2016 and had only a handful of applications, cost was not a major factor. But we now have 14+ deployed SPAs, with more coming online each year.</li><li><strong>Flexibility and capacity to scale. </strong>As we scale our teams and capabilities, custom tooling built to align with our needs and use cases enables our business and engineering teams to move faster</li><li><strong>Access control, auditability, and compliance (e.g. </strong><a href="https://en.wikipedia.org/wiki/System_and_Organization_Controls"><strong>SOC</strong></a><strong>). </strong>Serving a broad spectrum of employers, university partners, and students means more responsibility to keep our data safe and secure.</li></ul><h3>AWS Migration Goals</h3><p>After settling on AWS as our new platform of choice, we set several main goals for our re-architected SPA deployment:</p><ol><li><strong>Decouple application <em>hosting</em> from application <em>routing. </em></strong>Today, Guild relies on <a href="https://www.cloudflare.com/lp/overview-l/?&amp;_bt=444210169424&amp;_bk=cloudflare&amp;_bm=e&amp;_bn=g&amp;_bg=104534019073&amp;_placement=&amp;_target=&amp;_loc=1013859&amp;_dv=c&amp;awsearchcpc=1&amp;gclid=CjwKCAjw_NX7BRA1EiwA2dpg0qoFTT4I2Wx64t_HsDl16GfdZMAKFiPuejb4lsGvz-IdMqwK1nRs_RoCllcQAvD_BwE&amp;gclsrc=aw.ds">Cloudflare</a> to handle our routing (e.g. ensuring that when a user hits a url, they land where we want them to). But we saw a future where we could replace Cloudflare with AWS technologies like<a href="https://aws.amazon.com/route53/"> Amazon Route 53</a> and<a href="https://aws.amazon.com/lambda/edge/#:~:text=Lambda%40Edge%20is%20a%20feature,improves%20performance%20and%20reduces%20latency.&amp;text=Lambda%40Edge%20runs%20your%20code,content%20delivery%20network%20%28CDN%29."> Lambda@edge</a>. To allow for this evolvability, we wanted our routing implementation to be replaceable without affecting our hosting infrastructure. To accomplish this, we created an API interface between the routing and hosting layers.</li><li><strong>Establish a standard pattern for how SPAs are deployed and configured. </strong>With our previous Heroku solution, our SPAs had many divergent deployment and configuration patterns. These differences made it harder for engineers to work across teams because of the overhead of needing to learn new patterns. Examples of some differences include: a) Different tooling chains for CI/CD (GitHub actions vs CircleCi); b) Some applications used Cloudflare<a href="https://www.cloudflare.com/dns/"> DNS</a> for routing while others used Cloudflare<a href="https://blog.cloudflare.com/introducing-cloudflare-workers/"> workers</a>; c) Teams had their own URL patterns and webpack configurations for how they handled test/pull request applications. We deemed the migration an excellent opportunity to rethink our frontend deployment patterns and standards and improve developer experience.</li><li><strong>Continue to support Guild’s multiple URL patterns. </strong>Guild serves web applications via two main URL patterns: subdomain-based URLs and path-based URLs. Our new infrastructure had to support both in order to be successful. The subdomain serves as the unique identifier in determining what application a subdomain-based URL serves. Subdomain based URLs take the form<a href="https://subdomain.guildeducation.com/"> https://subdomain.guildeducation.com</a>. Path-based URLs take on the form<a href="https://subdomain.guildeducation.com/path"> https://subdomain.guildeducation.com/path</a>. The path serves as the unique identifier in determining which application gets served. This means different subdomains could serve the same application if the path is the same. For example, we host our programs catalog at <a href="https://subdomain.guildeducation.com/catalog">https://walmart.guildeducation.com/catalog</a> and<a href="https://subdomain.guildeducation.com/catalog"> https://disney.guildeducation.com/catalog</a><strong>, </strong>but both URLs serve the same application code.</li></ol><h3>New Architectural Overview</h3><p>With our platform and technologies chosen, requirements set, and our goals defined, we set out to design a solution that would meet these goals.</p><figure><img alt="Overview diagram of our SPA deployment architecture." src="https://cdn-images-1.medium.com/max/1024/1*uyMNRKLi0LudTeyflxDfIA.png" /><figcaption>Overview of our SPA deployment architecture.</figcaption></figure><p>Our deployment architecture can be divided into two main categories:</p><ol><li><strong>SPA hosting</strong></li><li><strong>URL Routing</strong></li></ol><p>As mentioned earlier, this split comes from the desire to separate our hosting and routing layers. By splitting them up, we are better able to design for future changes.</p><h3>SPA Hosting</h3><p>“Hosting” simply refers to where the SPA files (html, css, and javascript files, etc.) physically live, and a URL that can be hit to access them.</p><p>Our new design uses Amazon Simple Storage Service (S3) for hosting. Each SPA is given its own S3 bucket. Some of the key advantages of S3 are its high availability (99.9%) and robust backups. For any public-facing website, where being available at all times is critical, these features provide major advantages. S3’s biggest drawback is that it can only host static artifacts. Because our SPAs are <a href="https://dzone.com/articles/client-side-vs-server-side-rendering-what-to-choos">client-side rendered</a>, this limitation is ok.</p><p>For URL access, SSL security, and caching, Guild uses <a href="https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/Introduction.html">Cloudfront</a> (not to be confused with Cloud<em>flare</em>, already mentioned, for DNS and routing). AWS Cloudfront provides us with a unique URL that can be used to access the application hosted in a bucket.</p><p><strong>Tips for S3 hosting</strong></p><ul><li>Keep separate buckets for each SPA. Doing so will help keep each SPA isolated and allows for independent deployment lifecycles.</li><li>Enforce naming standards to enable discoverability. You want it to be fairly obvious what a bucket does, just by looking at the name. We name our SPA buckets after the Github repo they serve, and the domain name they are hosted on. (E.g. {github-repo-name}.{domain-name}.com). This allows us to easily identify which application a bucket hosts.</li><li>Remember to make use of <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingMetadata.html">object “metadata”</a>. We use metadata to provide HTTP headers like <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types">MIME types</a> and <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control">cache control headers</a>.</li></ul><h3>URL Routing</h3><p>URL routing emerged as the most challenging aspect of our deployment architecture. It also proved to be the most vital in accomplishing the decoupling we were going for.</p><p>Previously, each application employed its own unique way of routing its public-facing URL (i.e. the route a user visited to see a page) to the URL that Heroku provided for an application deployment.</p><p>To address these challenges, we broke up URL routing into two parts:</p><ol><li><strong>Translating a public request</strong></li><li><strong>Translating an asset request</strong></li></ol><h3>Translating a public request</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vIavlZYLSg9wtCyDbVm-pg.png" /><figcaption>Diagram showing that a user-friendly url is translated into a more complex Cloudfront url that points to an S3 bucket</figcaption></figure><p>A public request refers to the process of translating a public URL into the Cloudfront URL that the requested application is served from.</p><p>To better understand how this works, let’s walk through the following scenario:</p><p>I am a user who visits <a href="https://walmart.guldeducation.com/programs-catalog">https://walmart.guildeducation.com/catalog</a>. The code that this URL serves lives in a Github repository called programs-catalog. How does that source code make it to my browser when I visit <a href="https://walmart.guldeducation.com/programs-catalog">https://walmart.guldeducation.com/catalog</a>?</p><ol><li>A Cloudflare worker translates the public URL <a href="https://walmart.guldeducation.com/programs-catalog">https://walmart.guldeducation.com/catalog</a> into a<strong> standardized internal URL:</strong> <a href="https://programs-catalog.guildeducation.com/">https://programs-catalog.guildeducation.com</a></li><li>Next, a Cloudflare DNS entry translates the standard internal URL <a href="https://programs-catalog.guildeducation.com/">https://programs-catalog.guildeducation.com</a> to the correct Cloudfront URL in AWS</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FLN9cyuYYfBDfDRrxklokQ.png" /></figure><p><strong>The core idea is that we created a standardized internal URL that uniquely identifies a Github repository.</strong> We settled on the format https://{github-repo}.guildecucation.com. For this example, the standardized internal URL is <a href="https://progams-catalog.guildeducation.com/">https://progams-catalog.guildeducation.com</a></p><p>We chose this pattern because Github repos are unique within orgs, and it’s an easy way to identify which repository a URL refers to.</p><h3>Translating an asset request</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A2fXYUF-udOs7W2ysM3GYw.png" /></figure><p>Continuing with our example from above, once <a href="https://walmart.guildeducation.com/program-catalog">https://walmart.guildeducation.com/catalog</a> has been translated and its index.html page has been returned to the user, the user’s browser now needs to get the static assets that are required to render the page.</p><p>A static asset is a file that is loaded via a link or script from an HTML document. Examples of assets include javascript files, css files, and images.</p><p>Because we need to support path-based applications like in this example, we need to use absolute links for our static assets.</p><p><strong>The key insight is that we can reuse our standardized internal URL to create an absolute link for all our assets</strong>. As demonstrated above, the Cloudflare DNS record correctly translates that internal URL to the Cloudfront URL. By utilizing this strategy, we are able to standardize the way all of our SPAs create links to their assets.</p><h3>Putting it all together</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z89TTe4PBf8SqnY3pWi-Wg.png" /></figure><p>The solution outlined above accomplishes several of the architectural goals we set out to achieve.</p><h4>Decouples routing, application builds, and hosting infrastructure</h4><p>We created two primary interfaces that serve to decouple the hosting and the routing layers:</p><p><strong>Standardized Internal URL</strong></p><p>This serves as a way for the routing to map assets and public URLs back to the correct DNS record for an application. Applications need to know only about this URL. Because it’s simply a standard, it can be reused even if the routing layer is replaced.</p><p><strong>Cloudflare DNS record</strong></p><p>The hosting infrastructure automatically creates a DNS record in Cloudflare when it’s created. The consequences of this interface means that if the routing layer gets replaced later, we only need to change where the hosting infrastructure creates this DNS record.</p><h4>Establish a standard pattern for how all SPAs are deployed and configured</h4><p>All applications, regardless of their public URL requirements, are configured in the same standardized way: a standardized internal URL representation. This creates better uniformity across teams, which helps increase velocity as we scale.</p><h3>Conclusion</h3><p>Our migration from Heroku to AWS enabled us to redefine best practices and standards in how we deploy SPAs. Our utilization of AWS and Cloudflare fit our needs well, but isn’t necessarily recommended for everyone. Most existing patterns for hosting SPAs in AWS recommended using all AWS services. If you’re able to do this greenfield, I’d recommend using AWS-first technologies for DNS and routing, like S3 and Edge.</p><p>However, hopefully this pattern serves as a guide for other teams or companies that are looking for migration strategies to AWS and ways to create a more decoupled SPA deployment architecture.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a0ae5973975b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/extra-credit-by-guild/moving-our-guild-spas-from-heroku-to-aws-a0ae5973975b">Moving our Guild SPAs from Heroku to AWS</a> was originally published in <a href="https://medium.com/extra-credit-by-guild">Extra Credit-A Tech Blog by Guild</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design System Metrics]]></title>
            <link>https://medium.com/extra-credit-by-guild/design-system-metrics-1321efd38ae0?source=rss-6fb66f8ada6d------2</link>
            <guid isPermaLink="false">https://medium.com/p/1321efd38ae0</guid>
            <category><![CDATA[metrics]]></category>
            <category><![CDATA[component-libraries]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Justin Menestrina]]></dc:creator>
            <pubDate>Mon, 06 Apr 2020 14:42:58 GMT</pubDate>
            <atom:updated>2020-04-06T14:42:58.597Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t9p6oAb6UVTL5xhxl9y0zw.jpeg" /></figure><p>Last November, the Recess team began working on Recess 5.0. Over 12 teams use Recess, and our goal for this release was to improve the developer experience while also progressing on major design and product initiatives, including updated accessibility, a navigation overhaul, and various component deprecations.</p><p>In late January, we released Recess 5.0. While the upgrades generally went smoothly, we encountered a few hiccups. We introduced some unexpected breaking changes to the component APIs that would require significant updates to be made to the applications consuming those components. A few teams delayed upgrading to Recess 5.0 because the scope of the work required to upgrade to Recess 5.0 exceeded what had been estimated. As a team, we knew we could do better. We asked ourselves what had caused these misses and what we could learn from this experience.</p><h3><strong>Release Takeaways</strong></h3><p>Looking back at the upgrade, we realized that we lacked the data to make nuanced decisions. We hadn’t reached out to the right teams for feedback on API changes. Teams were promised a universally easy upgrade path, but in actuality, teams that used more Recess components were more heavily impacted. We looked for ways to improve future releases in order to improve the overall developer experience.</p><p>In order to understand the impacts of the changes we were making to Recess, we needed to know how developers were using the library. Without accurate information on usage, estimating the impact of a new release of Recess on any given team was based on our best guess of how the team was using Recess. This handicapped our ability to help product managers accurately estimate the amount of work it would take to upgrade Recess.<strong> </strong>However, manually tracking down the usage of Recess within the engineering org was tedious. It would take significant work to identify how API changes and deprecations would affect teams. We needed robust metrics.</p><h3><strong>Why Metrics Matter</strong></h3><p>With relevant metrics, we can better allocate our limited resources towards the highest value initiatives. We can prioritize the components with the highest usage, provide accurate estimates to product about upgrade efforts, and communicate directly with the teams about the changes impacting them.</p><h3><strong>Measuring Recess Usage</strong></h3><p>To address our lack of information about usage, we envisioned a dashboard to surface key metrics about Recess usage across Guild. The goal was to surface the data needed for smarter decisions about new features and to more effectively communicate the work effort to product managers.</p><p>We decided on four key metrics to achieve our goal:</p><h4><strong>Global component usage by team</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NpBCrZxXCLwNvwrwjKVndA.png" /><figcaption>Component usage by team</figcaption></figure><p>Tracking component usage by team allows us to identify the teams that are most affected by recess updates and changes. In addition, teams with higher recess usage are likely to have more feedback to give about the design system, making them high value targets for feedback.</p><h4><strong>Global component usage by version</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KNiQRsaNgZerCJoN-52LvA.png" /><figcaption>Component usage by version</figcaption></figure><p>With widely used design systems, many versions are in production at any given time. Tracking component usage by version tells us which versions are still in use so that we can continue to support those versions. Or in the case of older versions that we are planning to deprecate, we can coordinate with teams and plan accordingly if we can know that they are still in use.</p><h4><strong>Component usage over time</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bXHoHfnPfyCWzt5OK7BZSA.png" /><figcaption>Component usage over time</figcaption></figure><p>The purpose of Recess is to help our teams develop products faster. Quantitatively measuring how a design system helps our teams move faster is challenging. By measuring component usage over time, we can begin quantifying how the adoption of recess is evolving. These metrics allow us to start asking deeper questions about the effectiveness of the library.</p><h4><strong>Component usage per component</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vWJ8a6PK63Cv9JNYNaoEnQ.png" /></figure><p>Tracking granular component usage allows us to see the scale at which any given component is used across teams and versions. This information is vital for estimating the potential scale of API changes and component deprecations and gives us more accurate estimates when communicating to product managers and engineering teams about how much a team may be impacted.</p><h3><strong>Conclusion</strong></h3><p>As Guild has grown, and Recess is adopted by more teams, the decisions we make have multiplicative effects. Having metrics helps us identify where we should focus our efforts and allows us to measure the effectiveness of those decisions. Metrics serve as a toolkit to help us advance and better our design system.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1321efd38ae0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/extra-credit-by-guild/design-system-metrics-1321efd38ae0">Design System Metrics</a> was originally published in <a href="https://medium.com/extra-credit-by-guild">Extra Credit-A Tech Blog by Guild</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>