News for hackers. Stuff that matters.

A comment on New Grad vs. Senior Dev. Parent comment

Re:New Grad vs. Senior Dev by rumanator on Sunday March 29, 2020 @01:00PM (#22720539)
If your application is stateless following your definition then it's trivial to break the monolith down to microservices that focus on a bounded contexts while sharing a common db. This is a very well known microservices pattern.

https://microservices.io/patterns/data/shared-database.html

[ Parent | on HN ]
Re:New Grad vs. Senior Dev by erpellan on Sunday March 29, 2020 @04:39PM (#22722504)
Yes, and what does that buy you? Instead of a single deployable unit that owns the database, there are many deployable units, none of which can own the database. That doesn't seem like an improvement.
[ Parent | on HN ]
Re:New Grad vs. Senior Dev by JamesBarney on Sunday March 29, 2020 @01:53PM (#22720997)
Martin Fowler lists the benefits of microservices as

Strong module boundaries

Independent deployment

Technology diversity

And with a single database you severely limit the benefits from strong module boundaries and independent deployments. Suddenly you have to synchronize deployments, and anyone can pull or change any data in the database which now must be enforced with discipline which gets you into the same boat as a monolith.

[ Parent | on HN ]
Re:New Grad vs. Senior Dev by bogdanu on Sunday March 29, 2020 @06:54PM (#22723526)
> which gets you into the same boat as a monolith

Only worse because you don't have tools (IDEs, linters, etc) telling you what parts of the code have to be changed.

[ Parent | on HN ]