<?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: Obed Osei Frimpong</title>
    <description>The latest articles on DEV Community by Obed Osei Frimpong (@oseifrimpong).</description>
    <link>https://dev.to/oseifrimpong</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%2F172525%2F8b45beca-cf2f-457f-ad5f-3d430068b256.jpeg</url>
      <title>DEV Community: Obed Osei Frimpong</title>
      <link>https://dev.to/oseifrimpong</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/oseifrimpong"/>
    <language>en</language>
    <item>
      <title>How do you document your Microservice cluster? </title>
      <dc:creator>Obed Osei Frimpong</dc:creator>
      <pubDate>Sun, 08 Mar 2020 06:45:58 +0000</pubDate>
      <link>https://dev.to/oseifrimpong/how-do-you-document-your-microservice-cluster-4l1m</link>
      <guid>https://dev.to/oseifrimpong/how-do-you-document-your-microservice-cluster-4l1m</guid>
      <description>&lt;p&gt;Looking at how microservice architecture has become a go-to pattern for projects, it has become apparent that documentation can't be left out. &lt;/p&gt;

&lt;p&gt;I would appreciate it if more light is thrown on how documentation is done when building a project implements a microservice architecture. &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Do you consider documenting only the API gateway? If so then why? &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Do you consider documenting each service/microservice and then all centralized? If so, how do you centralize all the documentation? Is there a tool for automating this?&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>discuss</category>
      <category>microservices</category>
      <category>help</category>
    </item>
    <item>
      <title>What makes some engineering teams so successful?</title>
      <dc:creator>Obed Osei Frimpong</dc:creator>
      <pubDate>Thu, 13 Feb 2020 18:32:06 +0000</pubDate>
      <link>https://dev.to/oseifrimpong/what-makes-some-engineering-teams-so-successful-1l76</link>
      <guid>https://dev.to/oseifrimpong/what-makes-some-engineering-teams-so-successful-1l76</guid>
      <description>&lt;p&gt;Be it small or large engineering teams, what is it that makes them more efficient than others? How do they collaborate so well?&lt;br&gt;
Could it be their manager or their tech lead who has years of experience and understands how to lead the other engineers? &lt;/p&gt;

&lt;p&gt;What are the variables that make them successful?&lt;/p&gt;

&lt;p&gt;Yes, every team has its challenges, how do they overcome them? I could make use of some examples in your various teams. &lt;/p&gt;

&lt;p&gt;Lately, these questions have been running through my mind. I would be grateful if I get some inputs here as to how this comes by. &lt;/p&gt;

&lt;p&gt;Links and books related to this can also be shared. &lt;/p&gt;

</description>
      <category>discuss</category>
      <category>productivity</category>
    </item>
    <item>
      <title>What are the factors to consider when designing a microservice architecture?</title>
      <dc:creator>Obed Osei Frimpong</dc:creator>
      <pubDate>Wed, 24 Jul 2019 22:12:05 +0000</pubDate>
      <link>https://dev.to/oseifrimpong/what-are-the-factors-to-consider-when-designing-a-microservice-architecture-29hh</link>
      <guid>https://dev.to/oseifrimpong/what-are-the-factors-to-consider-when-designing-a-microservice-architecture-29hh</guid>
      <description>&lt;p&gt;I want to work on a side project and this time around, I want to carefully design a very good architecture for this project. It will consist of an API and a frontend. What are the important factors to consider when architecting this project?&lt;/p&gt;

</description>
      <category>architecture</category>
      <category>beginners</category>
    </item>
  </channel>
</rss>
