v2ray-core VS eShopOnContainers

Hey there! Lots of experience with this having lived in China for 2 years. I recommend you look into xray-core or v2ray.

https://github.com/v2fly/v2ray-core

https://github.com/XTLS/Xray-core

Here are my configs: https://github.com/acheong08/notes/tree/main/xray

cd ~ wget https://github.com/v2fly/v2ray-core/releases/download/v5.7.0/v2ray-linux-64.zip sudo apt install -y unzip unzip v2ray-linux-64.zip cp geoip/output/dat/* . ./v2ray uuid

If the changing por trick work you can try shadowsocks or v2ray.

Normal VPNs that you can see ads all over the place like N*rdVPN won't work, period. The correct way is to rent a few servers from different providers, make sure their ips are not blocked, and build your own V2Ray or Trojan service first. The Chinese gov will not be able to distinguish your Trojan traffic from ordinary https traffic, so the only thing that's sus to them would be the fact that all your traffic goes to one foreign ip, but I've been doing it for a few years without officials knocking on my door so yeah I think it will work for you as well. I don't take responsibility tho, do your research.

Given that every other client is mostly using https://github.com/v2fly/v2ray-core that can be compiled for every architecture/platform that Outline client supports, maybe it's worth investing time into allowing it as a backend. It can even be used for pure shadowsocks since it's for sure more updated than the old golang shadowsocks implementation.

v2Ray: https://v2fly.org

The eShopOnContainers is pretty popular, have you seen it yet? https://github.com/dotnet-architecture/eShopOnContainers

so I was exploring eShopOnContainers a little bit, more specifically the messages queues part and it made me wonder how is it possible to ensure data consistency across microservices when using them. If I'm not mistaken this isn't even shown in the eShopOnContainers examples.

For an example of an aggregate if you're unfamiliar - https://github.com/dotnet-architecture/eShopOnContainers/blob/3169a933447f1013c069e2cad2805c5de1ce9fbf/src/Services/Ordering/Ordering.Domain/AggregatesModel/OrderAggregate/Order.cs

You can check out eShopOnContainers as a reference architecture if you want, but (assuming this is meant to be somewhat of an ad hoc solution rather than a paragon of software engineering) I'd minimize the number of deployable assemblies (1 + tests if possible) and avoid Docker, again unless you have a specific reason to use it.

For K8s, it has a whole directory with deployment scripts. https://github.com/dotnet-architecture/eShopOnContainers/tree/dev/deploy/k8s

Checked the eshop on containers which uses EF for writes with DDD. Queries uses Dapper with raw sql. https://github.com/dotnet-architecture/eShopOnContainers/blob/dev/src/Services/Ordering/Ordering.API/Application/Queries/OrderQueries.cs

Maybe Microsoft’s eShopOnContainers reference system?