cooljacob204

Does it work for cycling?

It won't get paywalled. Instead they will let it get useful then start injecting ads into it once people trust it.

Late game performance and dsyncs comes to mind.

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.

Both Hamas and Israel have rejected a ton of different versions of a cease fire. Kinda hard to keep track of them all.

Both have also accepted terms for one version which the other one does not agree with. Resulting in headlines like "(Hamas/Israel) rejects cease fire".

:(

I hope you found a new area to invest in.

Honestly I always fuck this up so I avoid that joker.

The one if the big reason that people are brushing over is latency. You can have a billion super computers simulator something but the latency between them will prevent you from simulating at a reasonable speed an interconnected system like a bunch of neurons.

Holy crap he is taking what he did at Twitter and applying it to Tesla. Good luck...

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