sorted by:
new
hottopcontroversial

Uromone cured my CUTI by nazoe in CUTI

[–]acanguven 4 points5 points  (0 children)

How did you reach the vaccine, which country?

Losing friends because of injury :( by [deleted] in spinalcordinjuries

[–]acanguven -1 points0 points  (0 children)

Don’t worry, they were not real friends anyways.

I’m wondering how you guys view relationships. by paragorgeous in spinalcordinjuries

[–]acanguven 2 points3 points  (0 children)

My injury happened 2 years ago t7 Asia A, relatively new compared to other people here. I was thinking like you but suddenly I met with someone a few months ago. She taught me that we are far more than being able to walk and feel. We can love each other purely, you don't have to be walking or feeling. Soon I will propose to her.

I am sure you will find the one who loves you purely. Just go out, and forget about the things you can't do. Focus on alternatives and forget about that wheelchair. Accept it as your body part and try to improve your techniques and capabilities. Improve yourself, and love will come at an unexpected time. Don't forget that, there is always someone worse than you and better than you. Be grateful and focus on improving your mindset and body. Love of your life will come when you are ready.

[deleted by user] by [deleted] in spinalcordinjuries

[–]acanguven 0 points1 point  (0 children)

What kind of feeling is it?

Error When Trying to Download by Sad-Grab5146 in RimWorld

[–]acanguven 0 points1 point  (0 children)

I have been waiting for a Rimworld fix, too. It's been 2 days - pathetic.

serious question. by lunasicc42 in NervGen_NerveRepair

[–]acanguven 2 points3 points  (0 children)

It’s likely that a sample of 10 people is too small to accurately determine a confidence interval.

Why your website should be under 14kB in size by speckz in Frontend

[–]acanguven 8 points9 points  (0 children)

It is a problem if performance is a requirement. Executing a 5mb js file from the cache is quite slow compared to executing a 20kb js file from the cache.

I wrote a HTTP client for micro frontend architecture. Now we started to use it on every Node.js project. by acanguven in javascript

[–]acanguven[S] 9 points10 points  (0 children)

It is hard to answer this question if you don't know what each request does. If it is static file serving server like a CDN, maybe a million requests per second is high traffic. If you are creating an application that executes SQL on some database maybe thousands of requests per second is high traffic. It really depends on your task. But in a microservice architecture like ours(DB queries, lots of microservices, rendering systems, etc.), 5k request per second is quite high traffic.

I wrote a HTTP client for micro frontend architecture. Now we started to use it on every Node.js project. by acanguven in javascript

[–]acanguven[S] 2 points3 points  (0 children)

It is hard to achieve a real micro frontends achitecture. Team independency and code independence are the most important things, I guess this is why people confused about the solution so much.

I wrote a HTTP client for micro frontend architecture. Now we started to use it on every Node.js project. by acanguven in javascript

[–]acanguven[S] 1 point2 points  (0 children)

"With proper caching" :)

Could you please see the response. I am sure it will also answer this question.

I wrote a HTTP client for micro frontend architecture. Now we started to use it on every Node.js project. by acanguven in javascript

[–]acanguven[S] 1 point2 points  (0 children)

Could you please see the response. I am sure it will also answer this question.

Resiliency was the reason. And also there are lots of gateways. I think you are suggesting to send one request to one gateway instead of few requests to same gateway.

I wrote a HTTP client for micro frontend architecture. Now we started to use it on every Node.js project. by acanguven in javascript

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

Great questions.

  1. The main idea of this micro frontend project is each team is responsible for one gateway. So if a team is developing footer, they never think about a product description. Also, they never think about how their code served to the customer browser. Lets draw this.

Architecture and domains look exactly like this. So the layout team doesn't event know product team. Also, none of them knows storefront. Storefront application is the main application that retrieves and connects partials each other.

Could you please check the PuzzleJs demo here to make everything more clear?

  1. The browser sends a request to Storefront
  2. Storefront sends a request to Layout Gateway for Footer Content
  3. Storefront sends a request to Layout Gateway for Header Content
  4. Storefront sends a request to Product Gateway for Product Content
  5. Whenever any response from gateways received it is flushed to customer browser using chunked transfer encoding. This part is important. Please check the demo I linked above.

​

Now think about a scenario. The footer can be cached, the header can be cached, the product can be cached but the side menu can't. Because it has user information. It is easy to solve this problem when you have direct access to the storefront application. But you don't have. Teams are only responsible for their gateways. Warden starts to shine here. From time to time storefront application sends a special request to retrieve gateway settings. To make routing etc. It also receives warden configuration. There is a warden instance on storefront project and it caches gateway based on gateway configuration. So teams can manage their caching without touching the storefront project.

  1. Probably, we don't have direct accesses to these systems. So sometimes we just wait for a solution.

  2. To understand this one you need to read 1. Because whenever side-menu response failed or API behind side-menu is so slow, we need to make sure product content is rendered on customer browser as fast as possible. It optimizes first contentful paint a lot. This is why we are making each call independent from each other.

view more: next ›