Clever Geek Handbook

What are the disadvantages of riblet architecture in uber?

I am researching the current architecture of the Uber Rider app, and I learned that the current RIDER app has evolved from MVC to a custom RIBLE architecture that Uber developed by Uber themselves. As I understand it, riblets are independently testable pieces, each with one goal. I know the new architecture is capable of handling performance and scalability. I am interested to know the cons of riblet architecture.

image

+4


source to share


1 answer


Okay. I've found a few downsides to riblet architecture . I'll post them here to discuss with anyone interested. The main cons are as follows:



  • Since there are more independent riblets exchanging through their interfaces, there is the potential for a particular interface to fail compared to a system with fewer components.
  • Yes, testing a single riblet is very easy, but it makes integrating and processing queries across rifts more difficult.
  • It's too hard to change technology stack in the long run
+1


source






More articles:


All Articles