<?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 Yonatan Arbel on Medium]]></title>
        <description><![CDATA[Stories by Yonatan Arbel on Medium]]></description>
        <link>https://medium.com/@yonatanarbel?source=rss-6ea77653723------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*iBM7i56JR28daIthLZZdZQ@2x.jpeg</url>
            <title>Stories by Yonatan Arbel on Medium</title>
            <link>https://medium.com/@yonatanarbel?source=rss-6ea77653723------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 18:00:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yonatanarbel/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[ Custom Secrets Scanners in JFrog Xray: Extending a Proven Engine]]></title>
            <link>https://medium.com/@yonatanarbel/custom-secrets-scanners-in-jfrog-xray-extending-a-proven-engine-41750d5bc746?source=rss-6ea77653723------2</link>
            <guid isPermaLink="false">https://medium.com/p/41750d5bc746</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[secrets]]></category>
            <category><![CDATA[jfrog]]></category>
            <category><![CDATA[secret-scanning]]></category>
            <category><![CDATA[devsecops]]></category>
            <dc:creator><![CDATA[Yonatan Arbel]]></dc:creator>
            <pubDate>Mon, 21 Apr 2025 07:24:04 GMT</pubDate>
            <atom:updated>2025-04-21T07:38:58.335Z</atom:updated>
            <content:encoded><![CDATA[<h3>🔐 Custom Secrets Scanners in JFrog Advanced Security: Extending a Proven Engine</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ipSpxrDWrGSF6aR6" /></figure><p>At <a href="https://medium.com/u/e0a8dd860d37">JFrog</a>, we’ve invested years in building a <strong>best-in-class secrets detection engine</strong>, one that already detects <strong>thousands of common secret formats</strong> out of the box: AWS keys, GitHub tokens, private API credentials, and more.</p><p>But what happens when your organization uses something custom?</p><p>That’s where our new <a href="https://jfrog.com/help/r/jfrog-security-user-guide/products/advanced-security/configure-advanced-security/initiate-advanced-scans/custom-secrets-scanner"><strong>Custom Secrets Scanner</strong></a> comes in, an <em>extension</em> of the powerful detection already built into Advanced Security. You now have the ability to define your own patterns using RE2-compliant regular expressions, giving you control over the detection of organization-specific credentials, tokens, and secret formats.</p><blockquote><strong><em>Even without custom scanners, JFrog Advanced Security identifies most commonly used secrets and exposed credentials.</em></strong><em><br> The custom scanner feature is an </em>optional layer of enhancement<em> for teams with unique needs.</em></blockquote><h3>🤔 Hey? Why Do I Need a Secret Scanner Anyway?</h3><p>You might be thinking, ‘<em>We already have secret scanning in GitHub, aren’t we covered?’</em> That’s exactly what someone asked me at our booth at KubeCon EU 2025. And honestly, it’s a fair question…</p><p>But here’s the reality: <strong>secrets don’t only live in source code.</strong></p><p>They slip into build artifacts, container layers, ZIP files, environment variables, logs, and even compiled binaries. A token that was removed from a .env file might still be sitting inside a packaged .jarAnd once it’s embedded in a binary or published image, it’s <em>live</em> and potentially exposed.</p><p>This is where <strong>binary-level secret scanning</strong> comes in.</p><p>While tools like <a href="https://medium.com/u/8df3bf3c40ae">GitHub</a>’s secret scanning are powerful for catching issues <em>at the source</em>, JFrog Xray adds another layer of protection that inspects your <strong>actual build outputs</strong>. Together, this dual approach ensures you’re covering <strong>100% of your software footprint</strong>, not just the part sitting in your VCS.</p><blockquote><em>The truth is: if you’re only scanning your source, you’re only seeing half the picture.</em></blockquote><h3>🧪 What Makes Advanced Security Different?</h3><p>Xray’s Advanced Security built-in secret detection has already proven its value in the real world.</p><ul><li>We identified exposed <a href="https://blog.pypi.org/posts/2024-07-08-incident-report-leaked-admin-personal-access-token/"><strong>PyPI maintainer tokens</strong></a> that could have allowed hijacking of thousands of packages.</li><li>We’ve helped organizations uncover hardcoded credentials in their Docker images and source archives.</li><li>We detect secrets even when buried in <strong>binary blobs</strong>, not just plain text.</li></ul><p>This isn’t just scanning, it’s deep, forensic-grade inspection. And now, you can extend that with your own logic.</p><h3>🧠 Custom Patterns: Your Org, Your Rules</h3><p>With Custom Secrets Scanners, you can:</p><ul><li>Define unique secret patterns (e.g., myOrg_API_XXXX)</li><li>Tailor detection to internal standards or legacy systems</li><li>Apply RE2 regex safely and consistently across your artifacts and source code</li><li>Flag internal tokens or prefixes that no public scanner would recognize</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l7QHDchT-9kt9Q_xn1NsYg.png" /><figcaption>Example of custom scanner creation</figcaption></figure><h3>📌 Example: Scanning for Internal API Keys</h3><p>Say your team uses internal API keys that look like this:</p><pre>API_KEY_aB8djf39DKsl29XxqpWmE7nZq5HtYRuC</pre><p>You can create a custom rule:</p><pre>API_KEY_[a-zA-Z0-9]{32}</pre><p>This will catch:</p><ul><li>✅ API_KEY_x7YpQs9aF4bZtLdRfV6k8hRzXcSdFgTq</li><li>✅ API_KEY_ABCdef1234567890XYZuvw0987654321</li></ul><p>And block them from being shipped or committed, just like any other critical issue.</p><h3>💬 Bottom Line</h3><p>This isn’t about fixing a weakness, it’s about <strong>enhancing an already powerful detection system</strong> with the patterns that matter <em>only to you</em>.</p><p>Whether you use it or not, JFrog Xray continues to scan your binaries and source with one of the most comprehensive secret detection engines in the industry, proven in the wild, backed by research wins, and battle-tested at scale.</p><blockquote><strong><em>Now, you’re getting a more customizable and capable system, tuned to your team, your tokens, your world.</em></strong></blockquote><p><strong>Curious to learn more? Head over to </strong><a href="https://jfrog.com/devops-native-security"><strong>jfrog.com/devops-native-security</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41750d5bc746" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[No, Nigel, JFrog Is Cloud Native. Here’s the Evidence You Missed.]]></title>
            <link>https://medium.com/@yonatanarbel/no-nigel-jfrog-is-cloud-native-heres-the-evidence-you-missed-15a898150c7a?source=rss-6ea77653723------2</link>
            <guid isPermaLink="false">https://medium.com/p/15a898150c7a</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[technical-integrity]]></category>
            <category><![CDATA[cloud-native]]></category>
            <category><![CDATA[modern-saas]]></category>
            <dc:creator><![CDATA[Yonatan Arbel]]></dc:creator>
            <pubDate>Wed, 16 Apr 2025 17:13:46 GMT</pubDate>
            <atom:updated>2025-04-16T21:54:23.021Z</atom:updated>
            <content:encoded><![CDATA[<h3>Important Update:</h3><p>Less than 10 minutes after this response went live, Nigel, Developer Advocate at Cloudsmith and the author of the original article, deleted his entire Medium account.</p><p>No clarification. No defense. Just gone.</p><p>I think that says everything you need to know, about the credibility of the original post, and about the standards Nigel and Cloudsmith are willing to stand behind when challenged with facts.</p><h3>Why This Blog Exists?</h3><p>Anyone can share their opinion, and that’s a beautiful thing, until <strong>someone with limited knowledge and a loud microphone 🎤 starts spreading false information with a commercial goal in mind</strong>.</p><p>That’s exactly what happened in<a href="https://medium.com/@nigel.douglas/is-jfrog-cloud-a-cloud-native-artifact-management-solution-544178e26e28"> this blog post</a> by Nigel Douglas, who works for<a href="https://www.linkedin.com/company/cloudsmith"> Cloudsmith</a> (more on that later…). His article attempts to argue that JFrog Cloud isn’t truly cloud native.</p><p><strong>Before we move on, Nigel, please don’t insult your readers.<br></strong>When you say things like <em>“I stumbled upon the Cloudsmith platform”</em> or <em>“According to Cloudsmith’s website, they offer…”</em> come on, man… they literally pay your salary, the same as JFrog pays mine. Tell that upfront to readers!</p><p>I see you’ve only been in the role for two months, so let me offer a word of advice:<br><strong>This community values transparency and honesty.<br></strong>We developers can smell a sales pitch or misinformation from 100 miles away, so tread carefully.</p><p>The problem? <strong>Your blog is riddled with technical inaccuracies, flawed assumptions, and a shallow understanding of what cloud-native architecture actually means.</strong></p><p>I’m not here to play personal games. I’m here to protect the integrity of our industry and ensure developers aren’t misled by <strong>amateur-level analysis dressed up as an expert opinion</strong>.</p><h3>Section 1: The Claim — “JFrog Cloud runs on VMs, not containers. It’s lift-and-shift.”</h3><p>What Nigel says:</p><blockquote>“JFrog Cloud tends to run on traditional infrastructure like Virtual Machines (VMs) instead of containers. While containerised workloads aren’t the only basis for ensuring a web app is cloud-native, you can often tell in the cloud version of JFrog that it’s a lift-and-shift.”</blockquote><h4>The reality:</h4><p>This is either pure speculation or an outright fabrication.<br>Because the truth is simple:</p><ul><li>JFrog Cloud has run on containers since October 2018</li><li>It has been deployed on Kubernetes since the same date, and is one of the first companies to adopt Kubernetes in production</li><li>It uses KEDA (Kubernetes Event-Driven Autoscaling) for dynamic, Resource-efficient scaling. It was designed from day one for high-scale, cloud-native workloads</li></ul><p>So when <strong>you</strong> throw around “lift-and-shift,” what you are really exposing is this:<br> <strong>You didn’t do the homework</strong>.<br> Not even basic validation. Not even a glance at public talks, docs, or<a href="https://jfrog.com/help/viewer/book-attachment/7niiauCYgwHdSk6c2gosSA/Jz_Y_tzxThes44AdRW~MxA-7niiauCYgwHdSk6c2gosSA"> architecture discussions</a>. This is not an opinion, this is an observable fact:</p><ul><li><a href="https://jfrog.com/help/r/jfrog-artifactory-documentation/kubernetes-helm-chart-repositories">JFrog Helm charts</a></li><li><a href="https://jfrog.com/integrations/kubernetes-docker-registry/">JFrog on Kubernetes</a></li><li><a href="https://jfrog.com/blog/jfrog-cloud-native-innovation/">Internal scaling using KEDA</a>, Helm, and Prometheus event triggers (used across environments)</li></ul><p>This is not a VM-first platform retrofitted to survive in the cloud.<br>JFrog is a container-first, Kubernetes-native, horizontal-scaling SaaS built to power some of the world’s most demanding software supply chain pipelines.<br>Psssst,<a href="https://jfrog.com/help/viewer/book-attachment/7niiauCYgwHdSk6c2gosSA/Jz_Y_tzxThes44AdRW~MxA-7niiauCYgwHdSk6c2gosSA"> <strong>it was all there</strong></a>. Just waiting for you to read it 😉</p><h3>Section 2: The Claim — “You still need to manage infrastructure”</h3><p>What Nigel says<strong>:</strong></p><blockquote><em>“</em>Even in managed cloud versions, it often requires more manual setup, scaling considerations, and maintenance than a truly cloud-native service<em>.”</em></blockquote><p><strong>The reality:</strong></p><ul><li><strong>Completely FALSE</strong> for JFrog Cloud SaaS.</li><li>JFrog customers do not manage nodes, clusters, upgrades, or scaling.</li><li>He confused <strong>on-prem/self-hosted setups</strong> with <strong>SaaS</strong> — a rookie mistake.</li><li>JFrog Cloud SaaS is <strong>fully modular</strong>, <strong>horizontally scalable</strong>, and <strong>Kubernetes-native</strong></li></ul><p>Yes, JFrog started as a monolithic app, like literally every major platform that was created before 2010, but today JFrog containerized services, with clear separation of responsibility and scaling logic per component</p><p>So yes, the product evolved. Because <em>that’s what great engineering teams do: </em>they constantly innovate and scale architecture to meet ever-changing demands. That’s not a weakness. That’s maturity.</p><p><strong>Here are some references for you:</strong></p><ul><li><a href="https://jfrog.com/cloud/">Zero maintenance with JFrog Cloud</a></li><li><a href="https://jfrog.com/blog/self-hosted-or-saas-jfrog-has-you-covered-2/">How upgrades and availability are handled in SaaS</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/0*zDjE9YY5FRK4mIdz" /><figcaption>Confusing SaaS with self-hosted since 2025</figcaption></figure><h3>Section 3: The Claim — “Stateful = not cloud native”</h3><p>What Nigel says<strong>:</strong></p><blockquote><em>“</em>JFrog’s design heavily depends on persistent storage and state, which isn’t inherently bad, but it’s less cloud-native than services built for ephemeral, stateless scaling<em>”</em></blockquote><p><strong>The reality:</strong></p><ul><li>This is either a <strong>misunderstanding of basic cloud-native architecture</strong> or a complete disconnect from reality</li><li>Stateful stores like <strong>PostgreSQL and of course bucket-based artifact storage</strong> are standard and <strong>mandatory</strong> in cloud-native platforms.</li><li>Cloud-native is about how services are designed and managed, <strong>not whether they persist data.</strong></li></ul><p><strong>References:</strong></p><ul><li>CNCF Cloud Native Definition:<a href="https://github.com/cncf/toc/blob/main/DEFINITION.md"> cloudnative.dev</a></li><li>Cloud-native stateful services:<a href="https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/"> Stateful Workloads on Kubernetes</a></li></ul><h3>Section 4: The Claim — “JFrog isn’t SaaS or multi-tenant”</h3><p>What Nigel says<strong>:</strong></p><blockquote><em>“</em>JFrog offers Artifactory and other tools in the cloud, and it’s also hosted on AWS, Azure, and GCP. So yes, <strong>it’s cloud-hosted</strong>, but as stated earlier that doesn’t automatically make it <strong>cloud-native</strong><em>.”</em></blockquote><p><strong>The reality:</strong></p><ul><li>JFrog Cloud is a <strong>fully managed, multi-tenant SaaS</strong> running across AWS, GCP, and Azure.</li><li>Customers can choose between multi-tenant, isolated-tenant, or hybrid options.</li><li>There is zero need for customers to manage or maintain infrastructure.</li></ul><p><strong>References:</strong></p><ul><li><a href="https://jfrog.com/blog/jfrog-cloud-native-innovation/">JFrog SaaS architecture overview</a></li><li><a href="https://jfrog.com/cloud/">JFrog Cloud landing page</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*Z2RsP-VKl3wyb03c" /><figcaption>The way Nigel sees it</figcaption></figure><h3>Final Thoughts: Why This Matters</h3><p>This blog isn’t about hurt feelings. It’s about <strong>integrity in technical discourse</strong>.</p><p>When someone publishes a post with such low technical rigor and high confidence, it doesn’t just reflect poorly on them — <strong>it pollutes the technical conversation</strong>.</p><p><strong><em>And when that person represents a competitor, it raises a real question:<br>Is this ignorance, or intentional misinformation?</em></strong></p><h3>To Nigel:</h3><p>You had the right to publish your thoughts, but <strong>responsibility comes with that privilege.<br></strong>Next time, do more than skim a few terms. Ask someone who’s built in the cloud. Read the documentation. Learn.</p><p>When you mix immaturity with a lack of technical depth and give it a platform, you create noise, not value.</p><p>This kind of behavior damages trust in our industry and makes it harder for engineers to make the right decisions.</p><p>Nigel, next time, please do your research.</p><p>Expertise takes time. Stability. Focus. <strong>Stay humble</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*oNv-03WI0uoMspM0" /><figcaption>When your marketing team says, ‘just write something that sounds technical.’</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15a898150c7a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Coming together: The JFrog Platform]]></title>
            <link>https://medium.com/@yonatanarbel/coming-together-the-jfrog-platform-fca63fb46175?source=rss-6ea77653723------2</link>
            <guid isPermaLink="false">https://medium.com/p/fca63fb46175</guid>
            <category><![CDATA[jfrog]]></category>
            <category><![CDATA[angularjs]]></category>
            <category><![CDATA[vue]]></category>
            <category><![CDATA[vuejs]]></category>
            <dc:creator><![CDATA[Yonatan Arbel]]></dc:creator>
            <pubDate>Fri, 06 Mar 2020 13:57:49 GMT</pubDate>
            <atom:updated>2020-03-06T14:20:00.024Z</atom:updated>
            <content:encoded><![CDATA[<p>As a Front End Developer for JFrog, I’ll share some of our journey and challenge which brought us to the new UI on the JFrog Platform UI we recently released.</p><p>It was another day at JFrog, back then I was a FED for Xray. My team leader took me aside and told me we were going to do something big. Something which would solve the pain of skipping between tabs, make a common and consistent language between all our products, and help our customers be much more productive.</p><p>When we decided to migrate all relevant parts of our products into one platform. We needed to consider the advantages and disadvantages of these two approaches:</p><h3>The Storming Solution</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fl0HlKge0lMXf3hW2k%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fl0HlKge0lMXf3hW2k%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2Fl0HlKge0lMXf3hW2k%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="326" frameborder="0" scrolling="no"><a href="https://medium.com/media/4d6048c3f06dbfb505d0782fc6a8acc5/href">https://medium.com/media/4d6048c3f06dbfb505d0782fc6a8acc5/href</a></iframe><p>Allocate a special task force, and replace all components.<br> <br><strong>Advantage</strong><br>A dedicated team that will spend a single sprint migrating all components in one effort.<br>This is a good solution when you have spare people on your team you can allocate exclusively to the mission and will not take part in other roadmap tasks.<br>When working that way, the dedicated team can plan the start and end of the project more clearly and precisely</p><p><strong>Disadvantage</strong><br>The dedicated team will be blocked for all other tasks while existing products also need development., Also, working on a 5-year-old application can lead to unplanned issues during the development process which can block and delay the whole project.</p><h3>The Hybrid Solution</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FZwOJMIy7K5HJfKM73G%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FZwOJMIy7K5HJfKM73G%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FZwOJMIy7K5HJfKM73G%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="435" frameborder="0" scrolling="no"><a href="https://medium.com/media/db0d9e6292e54e7d592a2759866e527e/href">https://medium.com/media/db0d9e6292e54e7d592a2759866e527e/href</a></iframe><p>Create a Vue app which will host the legacy AngularJS application inside. With that, we will be able to have the AngularJS legacy code running inside a Vue component</p><p><strong>Advantage</strong><br>Development time is faster, we can work in parallel with AngularJS and Vue and switch between old screens built in AngularJS to new screens built in Vue. In this way, we can be sure all logic still exists and users can still use the functionality while working on the new screen. <br>Additionally, we can invest more time in planning the new screens when we know there is a solution for the current screen (even though it’s written in AngularJS ).</p><p><strong>Disadvantage</strong><br>The main disadvantage is that we carry a lot of redundant legacy code from the AngularJS application just to have the AngularJS app running inside our Vue application. Additionally, it makes debugging more complex since Vue dev tools cannot inspect AngularJS controllers and data flow.</p><p>To support AngularJS screens from the legacy applications that hadn’t yet been converted to Vue components, we needed the ability to run AngularJS modules inside a Vue app. We came up with an idea of making an ng-micro-app component to wrap our AngularJS app and provide a communication layer to our Vue app.</p><p>Evgeni, our UI Architect, built a nice and easy to work with infrastructure, so the development process was pretty convenient.</p><p>We used Vuex as our state manager, and it also acts as our shared data layer so AngularJS can consume the data from the main Vue wrapper (i.e., container).</p><p>The biggest challenge was connecting all the pieces while keeping data between all application parts synced and flowing smoothly. We wanted users to feel they are working on the same platform, whether they’re using Xray for scanning, Artifactory for deploying, Distribution for releases or… ok, I think you get the idea :)</p><h3>Strategy</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jFEXq2mtW1SzEwRs" /><figcaption>Photo by <a href="https://unsplash.com/@crypticsy?utm_source=medium&amp;utm_medium=referral">Mesh</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>The Bad</h3><p>While we could immediately dive into the code and start the development process, this is a sure path for bugs and issues we cant expect.</p><h3>The Good</h3><p>We decided to mark areas we wanted to start changing. For example, all processes of creating a repository, configuring proxies, and other pages considered low-risk that could achieve a quick win and encourage future migrations.</p><p>We held a series of meetings between the UI team leaders, who collaborated on the design and allocated tasks to each team…</p><p>We used JIRA tickets for each flow with sub-tasks for the required components. This way we could track and see the progress of the flows that were ready for testing and make sure all previous needs and behavior were fully covered.</p><h3>A new point of Vue</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/593/1*xUOSgI0zAbQPrErd1QQiZQ.png" /></figure><p>I could dedicate a full blog post explaining why we choose to work with Vue, I promise to publish one in the future.<br>Was it the right decision? It was the right one for us, but for another team React or AngularJS might be the right decision.</p><p>One of the reasons we chose Vue was to ease the process for developers who come from the AngularJS world (the majority of us) and also let React developers who join us to feel more comfortable since they are already familiar with the world of UI components and state management so it will be easier for them to adopt.</p><h3>How can it be achieved</h3><p>When a route that still uses the AngularJS screen is selected, the correct wrapper will be shown to display the relevant page. <br>Think of an animal that transforms itself according to a situation.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F7utU8eTzIJAju%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F7utU8eTzIJAju%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F7utU8eTzIJAju%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="435" frameborder="0" scrolling="no"><a href="https://medium.com/media/287c7e3ea31e6bfc59d2b3eab6464d02/href">https://medium.com/media/287c7e3ea31e6bfc59d2b3eab6464d02/href</a></iframe><p>Our main Vue app component looks like this:</p><pre>&lt;div&gt;<br> &lt;ng-micro-app v-show=”isNgAppActive”<br> :active=”isNgAppActive”<br> :state=”ngAppState”<br> <a href="http://twitter.com/ng">@ng</a>-microstatus=”onMicroAppStatusUpdate”<br> <a href="http://twitter.com/ng">@ng</a>-micro-app-state=”onMicroAppStateUpdate”<br> <a href="http://twitter.com/ng">@ng</a>-micro-app-set-event-bus=”onMicroAppSetEventBus”<br> <a href="http://twitter.com/ng">@ng</a>-micro-app-event-bus-dispatch=”onMicroAppEventBusDispatch”&gt;<br> &lt;/ng-micro-app&gt;</pre><pre>&lt;div v-show=”!isNgAppActive” class=”vue-app”&gt;<br> &lt;router-view&gt;&lt;/router-view&gt;<br> &lt;/div&gt;<br>&lt;/div&gt;</pre><pre>The `isNgAppActive` flag is changed according to the current route which holds meta information in case its an AngularJS state.</pre><p>Here’s an example:</p><pre>// — — — — — — — Application Route — — — — — — — //<br> {<br> path: ‘path/to/myPage’,<br> name: ‘myAwesomePage’, ←- the Vue state<br> meta: {<br> isNgApp: true, ← — Indicating its an AngularJS route<br> state: ‘MyAwesomeOldPage’, ←- the AngularJS state<br> },<br> },<br> {<br> path: ‘path/to/win’,<br> name: ‘winningPage’, ←- the Vue state<br> component: WinningComponent, ←- the Component which will be rendered<br> meta: {<br> //No Meta Data for this route <br> },<br> },</pre><p>The big picture of our platform should look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/1*DNgXU2j9OMYxeoo0m9hO2Q.png" /></figure><h3>Whats Next?</h3><p>Our roadmap includes completely removing AngularJS from our application and using Vue exclusively. This enables us to remove the complexity and redundant logic of using both, to make debugging much easier and component flow much smoother.</p><p>To do so, we need to do it as if petting a hedgehog: slowly and carefully. That means making sure all our unit tests, QA tests, and integration tests pass, so the behavior stays the same and nothing gets broken.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FZNLtdUlnNw96XFbbd2%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FZNLtdUlnNw96XFbbd2%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FZNLtdUlnNw96XFbbd2%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="696" frameborder="0" scrolling="no"><a href="https://medium.com/media/8c8c49fd4280559023903afaa1f16902/href">https://medium.com/media/8c8c49fd4280559023903afaa1f16902/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fca63fb46175" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>