cooljacob204

Does it work for cycling?

Honestly it's best to not bring up anything other then work at work lol.

I keep it pretty much complete separated from my real life.

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

Is that sarcasm? Because the auto industry is known for it.

She unfortunately has a ton of influence.

Only matters when it's the 2nd amendment

Putting the flag upside down isn't disrespecting the flag but kneeling during the anthem is. These people are so pathetic.

Late game performance and dsyncs comes to mind.

This money really needs to come with more strings attached. Like promises not to do mass layoffs.

If only I believed in Karma.

Too many disgusting people get to die comfortable and old for me to ever have any hope.

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.