Remember microservices should be, well micro, compared to your current services.
this post was submitted on 30 May 2024
24 points (96.2% liked)
memes
22 readers
49 users here now
share memes.
Meme:
- text over image, preferably a known meme template
Not memes:
- Text in image format
- rage comic
- webcomic
- text on clothing / hat / shoe / etc
- text post
- funny picture
- a picture of some text that is funny
- screencap of twitter post
- gif or sequential screencaps of tv/movie/cartoon with the actual script lines on them
- screencap of sms convo
- a tiktok
- a video
- a picture of questionably arranged text aka "don't dead open inside"
- anything with pornography
founded 5 months ago
MODERATORS
NPM install
Your 50 file project now has 7000 files.
People don’t understand that microservices ultimately end up creating more code, but that code is likely easier to maintain in a (very) large project because you can dedicate engineers to specific portions of it.
The vast majority of organizations don’t have the complexity required to make microservices practical.
One of the main drawbacks is cross-team collaboration. For example let's imagine an organization is siloed and teams are not incentivized to collaborate. When you find a service you depend on needs updating to give you access to data you can't currently get, you're possibly blocked for a long time. It turns into a political game to get the upstream service to implement the functionality you require.
Yeah understandable. When your organization crosses a certain size, it inevitably becomes politics.
Micro services have caused me far more problems than they've ever solved for me.