Comment by 0xbadcafebee | Hacker News Reader

Comment by 0xbadcafebee | Hacker News Reader

You can start with a monolith and evolve it into microservices. Very broadly:

  1. Start the monolithic app
  2. Write internal classes and functions such that they mimic an independent API and schema
  3. Write an API wrapper around unique functionality
  4. Allow exposing APIs on unique service ports
  5. Run independent copies of your app, running one API at a time
  6. Separate the schema of each API into its own database and connect at runtime
  7. Now you have a microservice

And don't even go past '1' unless you have product market fit.

Hum... You don't get a choice on where you can stop. Most software requires #1 and #2 to be sustainable, but yes you can do a lot of it with #1 alone for some time. But there also exist software that needs all of those other options from the bare beginning, or they won't fulfill their job.

Build a functional core, isolated with values, and an imperative shell. Systems built this way can be pulled apart into microservices if you really need to.

Very quick talk on what it buys you: https://www.destroyallsoftware.com/talks/boundaries

PSA: Microservices architecture is a technique for scaling organizations, not systems.

Reply on news.ycombinator.com