<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Architecture on Piotr Kosmowski</title>
    <link>/docs/notes/architecture/</link>
    <description>Recent content in Architecture on Piotr Kosmowski</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>pl-pl</language><atom:link href="/docs/notes/architecture/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>API Management</title>
      <link>/docs/notes/architecture/api-management/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/notes/architecture/api-management/</guid>
      <description>API Management refers to the practices and tools that enable an organization to govern and monitor its Application Programming Interfaces (APIs). Today, the term almost always means management of RESTful APIs using the JSON language.
API Management controls how the gateway passes calls to the back-end service and then hands off the response back to the invoker site. Most large companies have built out APIs for their customers and for internal use.</description>
    </item>
    
    <item>
      <title>Microservices</title>
      <link>/docs/notes/architecture/microservices/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/notes/architecture/microservices/</guid>
      <description> Decomposition # Decomposition strategies # Bounded context # Separate Value Stream # Separate Failure Domains # Anti-Corruption Layers # Facade # Decomposition reasons # Independent Rate of Change # Independent Life Cycle # Independent Scalability # Isolated Failure # Independant technologies # References # https://builttoadapt.io/whats-your-decomposition-strategy-e19b8e72ac8f https://dwmkerr.com/the-death-of-microservice-madness-in-2018/ https://content.pivotal.io/blog/should-that-be-a-microservice-keep-these-six-factors-in-mind </description>
    </item>
    
    <item>
      <title>OAuth</title>
      <link>/docs/notes/architecture/oauth/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/notes/architecture/oauth/</guid>
      <description>Thesaurus # OAuth 2.0 # Specs: https://tools.ietf.org/html/rfc6749#section-1.4
OAuth2 is an open standard for authorization. Confusingly, OAuth2 is also the basis for OpenID Connect, which provides OpenID (authentication) on top of OAuth2 (authorization) for a more complete security solution.
OpenID # OpenID is an open standard for authentication, promoted by the non-profit OpenID Foundation. As of March 2016, there are over a billion OpenID-enabled accounts on the internet, and organizations such as Google, WordPress, Yahoo, and PayPal use OpenId to authenticate users.</description>
    </item>
    
  </channel>
</rss>
