cooljacob204

Something to consider is a monolith can have different entry points and a focused area of work. Like my web application monolith can also have email workers, and background job processers all with different container specs and scaling but share a code base.

And coming from a background where I work heavily with Postgres a bunch of smaller segregates databases sound like a nightmare data integerity wise. Although I'm sure it can be done cleanly there are big advantages with having all your tables in one database.

Imo if your doing it right your monolith is also broken up into chunks that are segmented with clear defined apis and well tested (apis in this context are whatever your public functions/method/top level objects). With clean internal apis and properly segmented code it should be easy to read and do what you need.

I don't know if I agree with the infra level. What makes you say it has advantages there?

Biggest two advantages to micro services in my mind is you can use different tools / languages for different jobs and making it easier for multiple teams to work in parallel. Two biggest disadvantages in my mind is you lose code sharing and services become more siloded to different teams which can make it more difficult to roll out changes that need multiple services updated.

There is also the messaging problem with micro services. Message passing through the network rather then in memory. (Ex calling the user_service object vs user_service micro service)

One other big disadvantage of a monolith I also can think of is build time and developer tools can struggle with them. A lot more files/objects to keep track of and it can often make for an annoying development flow.

My preference is to monolith most things and only split off something into a micro service if you really get a big benefit from another tool or language for a specific task.

And in practice micro services become a fragile mess and takes longer to develop new products due to low code share and higher complexity.

Ofc not always the case, just like large monoliths can exist without being a mess.

Imo it should be shortened to hard 15-30 years regardless of life or author.

I already switched to Firefox a while back. The new tracking system bullshit was the last straw. Chrome team is too busy trying to invasively track us rather then actually improving the browser for consumers.

Because the source of entertainment matters less then you think.

Plenty of artists are using ai to augment their workflow and I believe that will be the future for art.

I mean it's the only viable alternative. And it's unquestionably that Microsoft has been making Windows worse recently.

That said. I'm not convinced Microsoft is doing this to hurt users. I think it's probably the correct assumption that they have seen a high number of crashes with 24H2 and these software packages.

And generation is going to win eventually.

Is there costs associated with this?

I'm in a ton of servers and it performs pretty okay for me. No real issues.

Have you programmed with rust a day in your life? Once you introduce one library that requires Tokio async you have to start wrapping all your calls that involve it in async shit.

So many better concurrency patterns out there.

And these libraries are not easily avoidable. Ex: most AWS libraries require it.

And forgive me for a stupid typo, I have had little sleep the last week but you are an asshole that thinks belittling people somehow makes you right so it doesn't really matter.