- Feature Articles
- CodeSOD
-
Error'd
- Most Recent Articles
- Stop Poking Me!
- Operation Erred Successfully
- A Dark Turn
- Nothing Doing
- Home By Another Way
- Coast Star
- Forsooth
- Epic
- Forums
-
Other Articles
- Random Article
- Other Series
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
Frlast!
Admin
How's that a WTF? The architect was rewarded and promoted, and Azure got a bigger check, which I (as a former Microsoftian) wholeheartedly welcome.
Admin
"Everything is always for the better."
Just not necessarily for YOUR better :)
Admin
I've never related more to a post before.
Admin
If you want it to operate at webscale, it should be Frlast! Frlast! Frlast! Frlast! Frlast! Frlast! Frlast! Frlast! Frlast! Frlast! Frlast! Frlast! Frlast!
Admin
A group of ex-colleagues got together and the concensus was that the original system, scaled to 3x peak load, 20 years later, would be fit to cope with 2.75x peak load. The cost and size of the architecture today is orders of magnitude greater. We've gained all the downsides of a distributed architecture. Not sure if the business has gained anything. Most techies have gained great CVs though
Admin
Agree, how is that a WTF? Only 75% more spend, What kind of figures of related spend for managing what % of turnover on what total company turnover?
No write up on any points that improved nor direct soundbite from the lead designer. Just one sided whinging to probably a little biased.
Maybe it was 50k a month cloud spend, now it's 87k5 a month, on a 100 employee business, managing 95% of the total 35mil turnover? That would not be a WTF manuvre.
Admin
Not to mention everyone who worked on the project got a few more bullet points for their résumé which is about to come in handy.
Admin
Well in mu compsny everybody is Trzinu to convince ne that we need kibernetski. And our scalibg problema Will be solved. All i'm saying is that the problemm is scalibg which is od highly spiky nature on memory front. But quite tepeatwble on bi weekly basist. And that evertyhig we need is to store the memory per minute per day for a month. And instead od using auto scaler use the scaler api to scale the servers. Up front
Admin
It seems the senior architect Alvin has found this article and added his perspective. :)
Admin
According to the vid "Don't build a Distributed Monolith: How to avoid doing microservices completely wrong", having the (relevant) admin data replicated across all databases that use it is the way it's supposed to go... but certainly not by manually updating all of them for each change.
You're supposed to propagate the changes through an event bus, or I guess automatic replication at the database level can work too, as long as you keep in mind that updates are not supposed to be instant.
Oh, and microservices actually calling each other is a big no-no.
Admin
calculate online islamic inheritance with inheritance calculator.Distribution laws to ensure fair and legal wealth distribution under islamic principles https://islamic-inheritance.mohammadharoon.com/en/