Breaking News: Grepper is joining You.com. Read the official announcement!
Check it out

When to Use and When NOT to Use Microservices: No Silver Bullet

Pragya Keshap answered on February 21, 2023 Popularity 1/10 Helpfulness 1/10

Contents


More Related Answers

  • When Not to Use Microservices Architectures ?
  • When not to choose Microservice?

  • When to Use and When NOT to Use Microservices: No Silver Bullet

    0

    When to Use Microservices Architecture  

    1. Make Sure You Have a “Really Good Reason” for Implementing Microservices

    2. Iterate with Small Changes and Keep the Single-Process Monolith as Your “Default”

    3. Required to Independently Deploy New Functionality with Zero Downtime

    4. Required to Independently Scale a Portion of Application

    5. Required to Data Partitioning with different Database Technologies

    6. Technology Diversity

    7. Required to Autonomous Teams with Organizational Upgrade


    When Not to Use Microservices — Anti-Patterns of Microservices  , 
    1. 
    Don’t do Distributed Monolith

    2. Don’t do microservices without DevOps or cloud services

    3. Limited Team sizes, Small Teams

    4. Brand new products or startups

    5. The Shared Database anti-pattern

    https://medium.com/design-microservices-architecture-with-patterns/when-to-use-and-when-not-to-use-microservices-no-silver-bullet-3ae293faf6d

    Popularity 1/10 Helpfulness 1/10 Language whatever
    Source: Grepper
    Link to this answer
    Share Copy Link
    Contributed on Feb 21 2023
    Pragya Keshap
    0 Answers  Avg Quality 2/10


    X

    Continue with Google

    By continuing, I agree that I have read and agree to Greppers's Terms of Service and Privacy Policy.
    X
    Grepper Account Login Required

    Oops, You will need to install Grepper and log-in to perform this action.