Nathaniel Schutta

Nathaniel T. Schutta is a software architect focused on cloud computing and building usable applications. A proponent of polyglot programming, Nate has written multiple books and appeared in various videos. Nate is a seasoned speaker regularly presenting at conferences worldwide, No Fluff Just Stuff symposia, meetups, universities, and user groups. Driven to rid the world of bad presentations, Nate coauthored the book Presentation Patterns with Neal Ford and Matthew McCullough.

  • "Should that be a Microservice?" Part 6: Simplify Interactions with External Dependencies (aka the Façade Pattern)

    "Should that be a Microservice?" Part 6: Simplify Interactions with External Dependencies (aka the Façade Pattern)

    When choosing an application architecture, six factors can help you decide when to use microservices. This post explores one factor in-depth: external dependencies.

    Read More
  • Should that be a Microservice? Part 5: Failure Isolation

    Should that be a Microservice? Part 5: Failure Isolation

    When choosing an application architecture, six factors can help you decide when to use microservices. This post explores one factor in-depth: failure isolation.

    Read More
  • "Should that be a Microservice?" Part 4: Independent Scalability

    "Should that be a Microservice?" Part 4: Independent Scalability

    When choosing an application architecture, six factors can help you decide when to use microservices. This post explores one factor in-depth: independent scalability.

    Read More
  • Should that be a Microservice? Part 3: Independent Life Cycles

    Should that be a Microservice? Part 3: Independent Life Cycles

    When choosing an application architecture, six factors can help you decide when to use microservices. This post explores one factor in-depth: independent life cycles.

    Read More
  • "Should that be a Microservice?" Part 2: Multiple Rates of Change

    "Should that be a Microservice?" Part 2: Multiple Rates of Change

    When choosing an application architecture, six factors can help you decide when to use microservices. This post explores one factor in-depth: multiple rates of change.

    Read More
  • Should that be a Microservice? Keep These Six Factors in Mind

    Should that be a Microservice? Keep These Six Factors in Mind

    There are many good reasons to use a microservices architecture. In this post, we examine 6 factors to help you decide when to use - and when not to use - microservices.

    Read More
  • loading
    Loading More...