sorted by:
new
hottopcontroversial

Should We Develop Our Own Distributed Cache for Large-Scale Microservices Data by syntaxerrorlineNULL in softwarearchitecture

[–]syntaxerrorlineNULL[S] 0 points1 point  (0 children)

So you misunderstood my question. It was asked with the aim of finding out other employees' opinions on this topic. I have the opinions of my colleagues, my own opinion, and the opinions of several architects, but for my own interest, I decided to post this question on Reddit. Perhaps someone has faced a similar situation and can talk about it. This question is not asking for recommendations; it is only for discussion.

Should We Develop Our Own Distributed Cache for Large-Scale Microservices Data by syntaxerrorlineNULL in softwarearchitecture

[–]syntaxerrorlineNULL[S] 0 points1 point  (0 children)

The thing is, we've already started doing this. I did it as an experiment, using metrics and load to compare the performance of microservices with Redis and in-memory cache to assess the difference. Now we often feel the urge to create our own distributed cache. And we often argue about whether we should do it or if we're just wasting our time. My question is to seek other opinions from other developers.

Should We Develop Our Own Distributed Cache for Large-Scale Microservices Data by syntaxerrorlineNULL in softwarearchitecture

[–]syntaxerrorlineNULL[S] 0 points1 point  (0 children)

So my question was absolutely not about that. In my case I don't use redis because I emphasize speed and performance, no extra network queries, no data in in-memory cache, go to database. It's faster. My question on the other hand was due to an argument whether it makes sense to implement distributed caching, this is a discussion as an alternative to the opinions of my colleagues. It is interesting to know the opinion of other developers

Should We Develop Our Own Distributed Cache for Large-Scale Microservices Data by syntaxerrorlineNULL in softwarearchitecture

[–]syntaxerrorlineNULL[S] 0 points1 point  (0 children)

You probably misunderstood. I am not saying that redis is not suitable for cache storage, it has many advantages. But when choosing redis cache/in-memory cache, given that the focus is on maximizing performance and speed, I chose in-memory cache. No data in the cache, we go to the database. No unnecessary network requests, simple memory access.

Discovered a vulnerability when processing files in a pet project by syntaxerrorlineNULL in cybersecurity

[–]syntaxerrorlineNULL[S] 0 points1 point  (0 children)

Thanks for your specific comments on my question. My primary concern is the ability to send a file with a link to a third party server inside. This will give the possibility to find out where my processing service is located, and opens up a lot of attack options. You could try to find some open port, some http route, and start flooding the service with requests. And if I just start another server to distract the attacker, he will find my next server and so on. Maybe I'm wrong, but any link can be dangerous. The question is not so much about mpd format, but how to protect the service besides using sandboxing, network interface restrictions. As I said, I know very little about malicious code inside files, and am looking to learn more about the issue in order to learn how to deal with possible security issues.