Readit NewsAnd ideally, your logging library should rarely need to update. If you need unique integrations per service, use a plug-in architecture and keep the plug-ins local to each service.
If you must to deploy every service because of a library change, you don't have services, you have a distributed monolith. The entire idea of a "shared library" which must be kept updated across your entire service fleet is antithetical to how you need to treat services.
You still have to deal with all the tooling you are talking about, right? You’ve just moved the goalpost to the BE.
And just like the specific use cases you mentioned for client routing I can also argue that many sites don’t care about SEO or first paint so those are non features.
So honestly I would argue for SPA over a server framework as it can dramatically reduce complexity. I think this is especially true when you must have an API because of multiple clients.
I think the DX is significantly better as well with fast reload where I don’t have to reload the page to see my changes.
People are jumping into nextjs because react is pushing it hard even tho it’s a worse product and questionable motives.
The New town we moved to is great. Oldest kid in accelerated programs, accelerating. Younger kid got the support she needed to catch up. :chefs_kiss:
Taking a step back, I don’t know how ‘equity’ got twisted into creating a lowering tide for all vs. a rising tide for all. So confusing.
Back in the day of only a handful of newspapers and of 1 camera per 1 million people (at least on the average day, the average person wouldn't lug their camera around with them), we had sightings of Yeti, Bigfoot, Nessie, El Chupacabra, etc.
Now we have the internet, an unstoppable torrent of crappy news and the mother of all tabloids, everyone has a high resolution camera in their pockets at all times, and cryptoids are all but gone.
I would have expected 16k HDR resolution photos of Yeti by now.
I feel betrayed! :-p