<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Al Tsang</title>
    <description>The latest articles on DEV Community by Al Tsang (@lunchbadger).</description>
    <link>https://dev.to/lunchbadger</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F20322%2Fb1d52c87-8398-40de-8de8-58d7f1ba3a5a.jpg</url>
      <title>DEV Community: Al Tsang</title>
      <link>https://dev.to/lunchbadger</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/lunchbadger"/>
    <language>en</language>
    <item>
      <title>New Plugins, New Release - Say Hello to Express Gateway 1.2.0!</title>
      <dc:creator>Al Tsang</dc:creator>
      <pubDate>Thu, 21 Sep 2017 08:32:47 +0000</pubDate>
      <link>https://dev.to/lunchbadger/new-plugins-new-release---say-hello-to-express-gateway-120</link>
      <guid>https://dev.to/lunchbadger/new-plugins-new-release---say-hello-to-express-gateway-120</guid>
      <description>

&lt;p&gt;Since &lt;a href="http://www.prnewswire.com/news-releases/new-express-gateway-open-source-initiative-simplifies-apis-300494946.html?tc=eml_cleartime"&gt;the official launch in July&lt;/a&gt; at the San Francisco Node.js Summit, we've been hard at work with &lt;a href="www,express-gateway.io"&gt;Express Gateway&lt;/a&gt;, an open source API Gateway built entirely on &lt;a href="http://expressjs.com/"&gt;Express.js&lt;/a&gt;. It's not just us over here at LunchBadger. We've seen some pretty interesting feedback from the &lt;a href="https://gitter.im/ExpressGateway/express-gateway"&gt;developer community&lt;/a&gt; already. So, we're excited to pump up the jam on this and start burning down &lt;a href="http://www.express-gateway.io/express-gateway-roadmap-overview"&gt;that backlog from the Community Roadmap.&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Now, that you've got the gist of it - our latest release (also broadcasted over Product Hunt) includes an extensible Plugin Framework. &lt;/p&gt;

&lt;h2&gt;
  
  
  What the hell is this Plugin Framework?
&lt;/h2&gt;

&lt;p&gt;The &lt;a href="http://www.express-gateway.io/docs/plugins/"&gt;Plugin&lt;/a&gt; Framework enables developers to take Express middleware and integrate them into Express Gateway as plugins. &lt;/p&gt;

&lt;p&gt;Express Gateway plugins contain entities and also allow event subscription. SO, one way to kung fu the crap out of that is to think of &lt;em&gt;a plugin as a container of Express Gateway entities.&lt;/em&gt; They extend the core by adding entities and providing event handlers.&lt;/p&gt;

&lt;h2&gt;
  
  
  What does that mean for Express Gateway?
&lt;/h2&gt;

&lt;p&gt;So, Express Gateway 1.2.0 adds a new plugin engine that allows anyone to add their own extension entities within a plugin. Then you can install  and utilize it dynamically within Express Gateway.&lt;br&gt;
An Express Gateway plugin acts as a container and has three key things:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Package.json&lt;/li&gt;
&lt;li&gt;A folder for each entity extension&lt;/li&gt;
&lt;li&gt;Manifest.js&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The package.json declares all dependencies that the plugin requires, just like any Node modules.&lt;/p&gt;

&lt;p&gt;We got to work breaking down all of the installation, entity extension point folders, manifest.js, and more of that magic.&lt;/p&gt;

&lt;h2&gt;
  
  
  Curious to Build Your Own?
&lt;/h2&gt;

&lt;p&gt;Express Gateway is a thin layer on top of ExpressJS Node.JS framework and uses a lot of concepts from it. So it is good to have &lt;strong&gt;some&lt;/strong&gt; idea of it, especially Express.js Middleware.&lt;/p&gt;

&lt;p&gt;To understand when different parts of plugin are registered and loaded check out the &lt;a href="http://www.express-gateway.io/docs/runtime/boot-sequence"&gt;Express Gateway Boot Sequence explanation&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Here's the short version:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Initial Phase &lt;em&gt;(Config Loading,Plugin registration)&lt;/em&gt;
&lt;/li&gt;
&lt;li&gt;Express Gateway Initialization &lt;em&gt;(Gateway ExpressJS server initialize, Loading extensions for Gateway, Pipeline engine initialization, Gateway Server start, Events)&lt;/em&gt;
&lt;/li&gt;
&lt;li&gt;Admin API initialization&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;~Fin&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;You can also check out more extension points covered in the &lt;a href="http://www.express-gateway.io/docs/plugins/plugin-development"&gt;Development Guide&lt;/a&gt;, or &lt;a href="http://www.express-gateway.io/docs/plugins/policy-development"&gt;build custom policies&lt;/a&gt;. Here is an &lt;a href="https://github.com/ExpressGateway/express-gateway-plugin-example"&gt;Example Plugin on Github&lt;/a&gt; with all of those awesome extension points being utilized.&lt;/p&gt;

&lt;p&gt;Before it's over, if you'd like to go &lt;strong&gt;&lt;a href="https://www.producthunt.com/posts/express-gateway"&gt;check out the latest release on Product Hunt&lt;/a&gt;&lt;/strong&gt; and share your thoughts on the project, new release.&lt;/p&gt;


</description>
      <category>javascript</category>
      <category>apis</category>
      <category>expressjs</category>
      <category>node</category>
    </item>
  </channel>
</rss>
