<?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: James Novino</title>
    <description>The latest articles on DEV Community by James Novino (@jamesnovino).</description>
    <link>https://dev.to/jamesnovino</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F114223%2Fa08b5999-8d2c-4264-a444-38fdf3dfdbb1.png</url>
      <title>DEV Community: James Novino</title>
      <link>https://dev.to/jamesnovino</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jamesnovino"/>
    <language>en</language>
    <item>
      <title>Expressing Business Flows using an F# DSL</title>
      <dc:creator>James Novino</dc:creator>
      <pubDate>Fri, 22 Mar 2019 19:24:43 +0000</pubDate>
      <link>https://dev.to/jamesnovino/expressing-business-flows-using-an-f-dsl-5hf4</link>
      <guid>https://dev.to/jamesnovino/expressing-business-flows-using-an-f-dsl-5hf4</guid>
      <description>&lt;p&gt;Over two years, the Order Management Team built and migrated to a new Workflow System, motivated by some reasons which I explain in an earlier post:&lt;br&gt;
Microservices to Workflows: The Evolution of Jet.com Order Management System&lt;/p&gt;

&lt;p&gt;TLDR: Expressing business domains as workflows simplifies development and improves the overall maintainability. Read the previous post for more details :).&lt;br&gt;
This post goes into the details about how we use F# to model our workflows as a DSL.&lt;/p&gt;

&lt;p&gt;To Read More: &lt;br&gt;
&lt;a href="https://medium.com/jettech/microservices-to-workflows-expressing-business-flows-using-an-f-dsl-d2e74e6d6d5e"&gt;https://medium.com/jettech/microservices-to-workflows-expressing-business-flows-using-an-f-dsl-d2e74e6d6d5e&lt;/a&gt;&lt;/p&gt;

</description>
      <category>fsharp</category>
      <category>workflows</category>
      <category>systems</category>
    </item>
    <item>
      <title>Abstracting IO using F#</title>
      <dc:creator>James Novino</dc:creator>
      <pubDate>Tue, 13 Nov 2018 01:41:56 +0000</pubDate>
      <link>https://dev.to/jamesnovino/abstracting-io-using-f-3bg3</link>
      <guid>https://dev.to/jamesnovino/abstracting-io-using-f-3bg3</guid>
      <description>

&lt;p&gt;In this post, I discuss approaches to unifying IO access pattern in F#. Unification allows us to abstract the underlying infrastructure implementations while enabling us to have consistent interfaces for all our IO patterns. Having shared access methods enabled consistent wrappings for things like retries, metrics, logging.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://medium.com/jettech/abstracting-io-using-f-dc841519610e"&gt;To Read More&lt;/a&gt;&lt;/p&gt;


</description>
      <category>f</category>
      <category>softwareengineering</category>
      <category>distributedsystems</category>
    </item>
  </channel>
</rss>
