I made up some architecture and want an opinion

[tame oxide]

<@&987246841693360200> please have a look, thanks.

[crude pecan]

https://polylith.gitbook.io/polylith/

[white ridge]

Microservices are expensive to host because each service is more complicated, and runs more code than it would in a monolith.

The serialization, network sockets, etc, all that extra stuff is what makes it expensive.

It doesn't sound like writing code for this would be like writing code for a monolith, because serialization and asynchronous calls across module boundaries would still be a thing

This already seems pretty complicated as well, I would throw it in the cloud and see how it compares to microservices in cost.

[white ridge]

The concept of microservices initially spawned out of groups that practiced evolutionary design. Which means only building technical complexity when necessary, and removing extra complexity when not necessary.

As such their code was already organized into something like microservices, but inside a single process, and without the serialization/network complexity.

Because their code was already well organized, and they already tested the contracts between the different "services", it was trivial to take a group of objects and deploy them into another web service as the company grew.

If you're thinking about the context of a startup, and how to make the development experience better without incurring a ton of extra hosting cost, I would explore Evolutionary Design.
https://www.thoughtworks.com/en-us/insights/books/building-evolutionary-architectures

[solid maple]

oooh this is cool

thanks

anyways deciding to leave this chat because after an hour now i can't be bothered

[tame oxide]

Closed the thread.

Closed the thread.