# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 3
# self = https://watcher.sour.is/conv/sbrsnua
prologic
twtxt.net
View Thread
What I find amazing about micro service l architectures in the way engineering teams and software companies overuse them is how many problems they seem to run into and solutions to those problems that seem to arise.

when did you ever hear problems with good old fashion monolith designs and implementation and random tools created to solve problems with monolith development?
prologic
twtxt.net
View Thread
What I find amazing about micro service l architectures in the way engineering teams and software companies overuse them is how many problems they seem to run into and solutions to those problems that seem to arise.

when did you ever hear problems with good old fashion monolith designs and implementation and random tools created to solve problems with monolith development?
lyse
lyse.isobeef.org
View Thread
(Disclaimer: didn't read the original post.) I was thinking about that each day since you brought this up, @prologic. Very interesting. I fail to answer your question. But I have the feeling that it's just a matter of some kind of a filter bubble (for the lack of a better term).

While some people go totally overboard with their microservices (so did I once in the past, it was a valuable lesson, though), I can't believe that there isn't the same (or quite close) level of problems and new tooling for monolithitic systems out there. The problems and thus solutions are different, but I'm sure, they exist in a comparable manner. On the other hand, microservices are hyped as the very best latest shit and savior for a very long time now. So I would imagine that there are waaay more microservice architectures out there than monolithic ones these days. Hence, just by the difference in magnitudes, one has to come across microservice solutions much more than monolith helpers. I don't have any numbers to back this up, it's just a gut feeling. My theory could be complete rubbish.

In a way, microservices are just one of the key concepts from the Unix philosophy in my opinion. Just called differently. Once I realized that, µservices suddenly made much more sense to me. Once again, most things are just reinventions of old concepts and now called differently. "Raider heißt jetzt Twix, sonst ändert sich nix."

And as with everything, overcoloring is always bad, no matter in which direction you go. Just gotta have to hit the sweet spot, or somewhere close enough in that area.