justcallmelarry

joined 1 year ago
[–] [email protected] 7 points 1 day ago

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

[–] [email protected] 12 points 1 month ago

Nah thanks, up arrow hasnt failed me yet

[–] [email protected] 3 points 1 month ago
866
A step too far? (lemmy.dbzer0.com)
 
[–] [email protected] 1 points 2 months ago* (last edited 2 months ago) (2 children)

Yeah, or Shelfplayer

I'm holding off on trying Plappa until they add session support, since I like the stats, heh.

Tho I do have a Testflight spot for the ABS app, as well.

I do want to try Plappa, though! I really like the paperless-ngx app (Paperparrot) from the same developer

[–] [email protected] 3 points 2 months ago (6 children)

The ABS app is also still in beta on iOS, so unless you are tech savvy enough to either sideload or try to get in on one of the windows when users are booted from the testflight beta, you are going to have to use one of the 3d party apps.

Prologue just seems to do many things nicely, and user experience seems very important to the developer, so there is a huge crowd that swears by the app.

[–] [email protected] 12 points 2 months ago (2 children)

I WANNA KNOW WHAT LOAF IS!

[–] [email protected] 16 points 2 months ago (1 children)

That sure looks like a blocker, though

[–] [email protected] 3 points 2 months ago

Looks like an elf to me!

[–] [email protected] 5 points 3 months ago

You can just close your eyes and not open them again, no blinking!

[–] [email protected] 8 points 3 months ago
[–] [email protected] 3 points 3 months ago (1 children)

I know you wrote /s, but this has basically nothing to do with the tech of microservices, and more to do with internal politics.

Switch the ”user microservice” to ”birth date is not indexed in the database and i have to reach out to the database handling team” and you are in the same situation

[–] [email protected] 12 points 3 months ago (4 children)

Tbh mostly microservices solves two issues for me:

  1. You can scale resource-heavy operations without an impact of scaling everything else.
  2. You kind of ”force” people to keep things contained, instead of making everything interdependant. Which helps containing issues with updates to certain functionality to only have an impact on that functionality.

You could do #2 in a ”monolithic” setup as well (by doing modules or libraries or something), it just never works out that way in practice

376
submitted 3 months ago* (last edited 3 months ago) by [email protected] to c/[email protected]
view more: next ›