Don't apply #microservices architecture unless you have a project with multiple frontends and tens of thousands of lines of code and multiple developers who can handle the complexity of the connection between those microservices. It just brings a lot of headaches!

Don't go with #monolithic architecture unless you are granualizing your modules well from the starting point and you know the scalability needs of your services.

Probably making some #frontenddev somewhere cry right now. Got fed up with a gigantic #monolithic #CSS that was kinda a nightmare to navigate and grasp.

So now I'm rewriting it in #lesscss. Which probably is not the hip #tool anymore.

But at least I can wrap my head around the code, and where to change what.

My triumphant return to The New Stack: There's been a resumption of the debate among #infrastructure software #developers over whether decoupling an organization's functionality into #microservices in the name of #scalability reduces complexity or re-introduces it. This happened when Amazon Prime Video engineers made an architectural decision, and chronicled it in their blog. For a streaming video monitoring function, they moved _away_ from microservices, they said, and back toward a #monolithic architecture, for purposes of simplicity, speed, performance, and cost reduction.

Before long, the whole debate fired up again: Microservices only buys you so much scalability, some said, but eventually the complexity of its messaging between services eats any speed gains you had at the start.

At least that's what Prime Video's engineers appeared to be saying. But a close examination of their situation by world-class experts, including from Amazon Web Services (AWS), revealed that the devil was lurking outside the details after all and out in the open where we should have seen him: Yes, they had consolidated some #StepFunctions, but in so doing, they actually went the other direction. They made a microservice; the blog's author simply didn't realize it.

So what was this debate truly about, then? Do we not know a monolith when we see it anymore? Are we so quick to take sides in a debate that we've lost track of what we're actually arguing about?

No, that wasn't a digression. I'm still talking about #cloudcomputing infrastructure.

Anyway, do take some time today to read this article, which features an all-star cast including Donnie Berkholz @dberkholz,
Lori MacVittie from F5, David Mooter from Forrester, Laura Tacho, Ajay Nair from AWS,
@microsoft CVP
Brendan Burns, and one of the original microservices champions, Adrian Cockcroft @adrianco.

https://thenewstack.io/amazon-prime-videos-microservices-move-doesnt-lead-to-a-monolith-after-all/

Modern #programmers' penchant for #monolithic #software design vex me, exceedingly.

I find the modern #programmers' penchant for #monolithic #software design exceedingly vexing.

Probably for the majority of use cases (uniformly randomly selecting among all software projects), #monolithic architecture is a better fit than #microservices architecture.
https://nebu.substack.com/p/when-to-use-microservices-vs-monolithic?sd=pf

You should not use microservice as a default option. Use it when you want to have these abilities within your teams:
1. Zero downtime independent deployability. It is hard to deploy a giant #monolithic service without consequences. A small mistake may shut down the whole system.
2. Isolation of processing around data. For instance, a service that processes user's search queries doesn't need to access details of user payments data.

After lying in wait until now as yet another, self-defederated, #deprecated, #legacy #monolithic silo based on mastodon - an identical model to #GAB and #Truth_Social... #Counter_Social has finally stepped from the shadows to challenge #Twatter on it's own turf - to what end? Another big #silo?

Joining big #Fediverse servers does little to alleviate the #twittermigration and #twitugee problems.

Here's what does:

https://nitter.lacontrevoie.fr/Linboard/status/1603598950593744897

#tallship #FOSS #ActivityPub #smallweb #self_host

⛵

.

After lying in wait until now as yet another, self-defederated, #deprecated, #legacy #monolithic silo based on mastodon - an identical model to #GAB and #Truth_Social... #Counter_Social has finally stepped from the shadows to challenge #Twatter on it's own turf - to what end? Another big #silo?

Joining big #Fediverse servers does little to alleviate the #twittermigration and #twitugee problems.

Here's what does:

https://nitter.lacontrevoie.fr/Linboard/status/1603598950593744897

#tallship #FOSS #ActivityPub #smallweb #self_host

⛵

.

After lying in wait until now as yet another, self-defederated, #deprecated, #legacy #monolithic silo based on mastodon - an identical model to #GAB and #Truth_Social... #Counter_Social has finally stepped from the shadows to challenge #Twatter on it's own turf - to what end? Another big #silo?

Joining big #Fediverse servers does little to alleviate the #twittermigration and #twitugee problems.

Here's what does:

https://nitter.lacontrevoie.fr/Linboard/status/1603598950593744897

#tallship #FOSS #ActivityPub #smallweb #self_host

⛵

.

After lying in wait until now as yet another, self-defederated, #deprecated, #legacy #monolithic silo based on mastodon - an identical model to #GAB and #Truth_Social... #Counter_Social has finally stepped from the shadows to challenge #Twatter on it's own turf - to what end? Another big #silo?

Joining big #Fediverse servers does little to alleviate the #twittermigration and #twitugee problems.

Here's what does:

https://nitter.lacontrevoie.fr/Linboard/status/1603598950593744897

#tallship #FOSS #ActivityPub #smallweb #self_host

⛵

.

@Adman I'm unaware of those working on it for Qubes specifically but #XenHypervisor which #QubesOS uses does have some info on implementation.

https://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions_whitepaper

It seems like it's going to involve changing many aspects of #Qubes to work on ARM but from what i can tell it seems possible.

The user base is small in comparison to #Linux but it's definitely a better solution for #infosec folks wanting / needing #security vs a #Monolithic #kernel that can't be secured in the ways Qubes does

@blamp For those who take the time and are intelligent enough to actually understand it, i've also posted a short thread on #OpenHardware and a great video by #JoannaRutkowska of the #Qubes / #QubesOS / #Wildland project(s).

#IntelME isn't your friend, neither is #Microcode no one can #audit.

So for all the #FOSS #Trolls hating on this post, maybe level up and get real because if you're using a #monolithic #kernel on #linux, you're still not #secure.

@nixCraft Sometimes i rely on a #monolithic #kernel i can't #secure no matter how hard i or anyone else tries.

Other times, i use #QubesOS

@netrom I'm retired so for me it's something i enjoy coming from a tech background. Joanna Rutkowska is brilliant and i find her, Qubes, those working on it, and her new project #Wildland inspiring.

If i were working in #infosec and relied on a #monolithic #kernel without the #isolation #Qubes offers, i suspect i wouldn't sleep as well at night depending on my job. ;)

I think it's a great tool / option for anyone in #security.

@DorpMarfin12 I use #QubesOS. #Arch #Linux users with their insecure #Monolithic #Kernel bore me with their boasting.

There's nothing wrong with Arch, and i don't have anything against any other linux distro either. It's about what the user needs, wants and what works well on their hardware. Saying one is the best or superior is useless when all linux distros are insecure in some ways is my point.

#Security #Qubes #Infosec #Hypervisor #XenHypervisor #Isolation #Qube

@nixCraft Sometimes i rely on a #monolithic #kernel i can't #secure no matter how hard i try.

Other times, i use #QubesOS

@expertmanofficial Ah, saw your feed.

You're a #Twitter user coming to #Mastodon who share's links to #Birdsite.

And apparently you're using #Linux with a #monolithic #kernel you can't secure no matter how hard you try.

Yeah, might want to try #QubesOS and stop using Twitter 'Expert'.

@vendetta @galure #QubesOS exists for a specific reason and that reason is #Linux users are not #secure with ANY distro compared to it because they all rely on a #monolithic #kernel that has access to everything. You cannot secure ANY linux distro due to this compared to what #Qubes offers.

Linux users choose to have a less secure #OS in this way no matter how hard they try to secure it. It's two totally different threat models, no user friendly in between will exist for less savvy nix users.

@bojkotiMalbona
Yes, you will find the integrity attribute is used today but maybe not often enough, in all fairness.

Of course, a great way to be more secure though would be to not depend on a #monolithic privatiser of the web like Cf, and Amazon..

@pj@bitcoinhackers.org