How Netflix Really Uses Java

davidktw

Arch-Supremacy Member
Joined
Apr 15, 2010
Messages
13,547
Reaction score
1,300
Why I share this article. Because it coincide exactly to my understanding that if you are going microservices when you are designing an extremely large architecture, you will be paying dearly for all the tracing and logging, orchestration, which adds on much more operating cost than you reap any benefit from such a design.

How large is consider large? Based on what I have come across, anything less than 100 servers is probably still consider small.

The article is describing the corporate that contribute to the well-known Java framework in the industry today - namely Spring Cloud, which is based on Springboot within the Spring framework.

When architects speak of scalability issues in monolithic architecture, we are really referring to large organisations that need extremely large architecture to host all their applications need. If you need to artificially create teams to manage microservice designs, you are definitely doing it wrong. If you need to think hard on how to split your services, you are doing it wrong. If it is within a department that you implement microservices, it is most likely wrong too.

The article describe as each microservice larger than monolithic systems. Monolithic doesn’t mean One, it means homogeneous. Even homogeneous architecture can operate in parallel to scale across a very large user base.

It has nothing to do with which programming language or framework you choose. It has to do with the service and domain you are serving. Do yourself and your project a favour, don’t think microservices until you have exhausted all other options. It should be your last resort. Pay the price of splitting up things only when it make sense

:)
 

Trader11

Banned
Joined
Oct 14, 2018
Messages
15,698
Reaction score
5,233
Why I share this article. Because it coincide exactly to my understanding that if you are going microservices when you are designing an extremely large architecture, you will be paying dearly for all the tracing and logging, orchestration, which adds on much more operating cost than you reap any benefit from such a design.

How large is consider large? Based on what I have come across, anything less than 100 servers is probably still consider small.

The article is describing the corporate that contribute to the well-known Java framework in the industry today - namely Spring Cloud, which is based on Springboot within the Spring framework.

When architects speak of scalability issues in monolithic architecture, we are really referring to large organisations that need extremely large architecture to host all their applications need. If you need to artificially create teams to manage microservice designs, you are definitely doing it wrong. If you need to think hard on how to split your services, you are doing it wrong. If it is within a department that you implement microservices, it is most likely wrong too.

The article describe as each microservice larger than monolithic systems. Monolithic doesn’t mean One, it means homogeneous. Even homogeneous architecture can operate in parallel to scale across a very large user base.

It has nothing to do with which programming language or framework you choose. It has to do with the service and domain you are serving. Do yourself and your project a favour, don’t think microservices until you have exhausted all other options. It should be your last resort. Pay the price of splitting up things only when it make sense

:)
How does a lowly developer argue with the architect or lead developer who loves micro services?
 

davidktw

Arch-Supremacy Member
Joined
Apr 15, 2010
Messages
13,547
Reaction score
1,300
How does a lowly developer argue with the architect or lead developer who loves micro services?
You don’t. Because even if you do, the architect might be just another pawn where its boss is the one whom got bought into this architecture thinking it is really as good as it sounds without truly understand the complexity involved. It is up to one whom is truly competent to learn how to say NO.

If this recent article that describe one of the largest infrastructure in the world today doesn’t wake up the confused mind, nothing will.

However the junior developer can learn from this and hopefully one fine day when this developer becomes the architect, he/she can have the courage to learn how to say NO.

:)
 

Trader11

Banned
Joined
Oct 14, 2018
Messages
15,698
Reaction score
5,233
Would you like that ? How would that benefit you as a consumer ? :)
I think Netflix close their eyes intentionally. Those that complained are those copyrights companies. No harm for Netflix if user use VPN to access other region content
 

davidktw

Arch-Supremacy Member
Joined
Apr 15, 2010
Messages
13,547
Reaction score
1,300
I think Netflix close their eyes intentionally. Those that complained are those copyrights companies. No harm for Netflix if user use VPN to access other region content
Netflix can make it very difficult for end-users which makes it bad for business. Yes indeed it is the studios like Sony Pictures, Warner Bros that are concern. Hence I wonder why @peterchan75 seems rather concern when coming from a consumer standpoint.
:)
 
Important Forum Advisory Note
This forum is moderated by volunteer moderators who will react only to members' feedback on posts. Moderators are not employees or representatives of HWZ Forums. Forum members and moderators are responsible for their own posts. Please refer to our Community Guidelines and Standards and Terms and Conditions for more information.
Top