Rhythm is everywhere. Even in IT Industry?

Rhythm is everywhere, no longer in music. Walking, running, speech, blue waves, and many things we do and experience have rhythm. In fact, thy first journey used to be the rhythms on your mother’s heartbeat.

I was watching below Video from TED “Rhythm is Everywhere”. I thought I should find out what is meant of Rhythm in IT industries.

I believe Rhythm is everywhere in IT industry as well. Let’s Talk about Programming and try to find out output.

score_theory = 60

score_practical = 20

if(score_theory > 50):

                                    print(“Please check the input score for ‘Theory’.”) # Step 2.1

elif(score_practical > 50):

print(“Please check the input score for ‘Practical’.”)  # Step 2.2

else:                            print(“Score validated. Your total is: “,score_theory + score_practical) # Step 3

Are you able to find anything? You are right, very difficult to read this program. Rhythm is missing in this program. What is Rhythm here? Alignment. Right?

score_theory = 60

score_practical = 20

if(score_theory > 50):

    print(“Please check the input score for ‘Theory’.”)

elif(score_practical > 50):

    print(“Please check the input score for ‘Practical’.”) 

else:

    print(“Score validated. Your total is: “,score_theory + score_practical)

You can see above Rhythmic programming. Proper aligned and this enhance the readability of the program.

Let’s take more example. The heartbeat of CPU and Memory. Whenever you face any challenge in Computer/Server, you quickly check CPU and Memory Utilization.

If the graph is Rhythmic, you check something else. But if it is fluctuating, then? We quickly reboot the server (We should not do this until we find the root cause). As soon as we reboot, the server comes into Rhythm.

Below you can find various Rhythmic and Non-rhythmic Graph.

Let’s Talk About Architecture.

Architecture should also be Rhythmic.

Non-Rhythmic Architecture.

 If anyhow below architecture comes into reality,  but I am sure you cannot maintain this. Some Architect calls it a very complicated architecture. Do you agree? Suppose you design your house just like below architecture. What will happen? I am sure you will not be able to sleep in same room every day. You will have to find your room here you slept last night.

Rhythmic Architecture.

You can see below we have tried to redesign above Architecture and clearly it is Rhythmic. Right?

An example of a future state view – instead of systems being siloed between each department they are now connected and it is much more organized.

Security in IT

This is again an excellent example of Rhythm. If Security people find any non Rhythmic thing anywhere, they quickly report and check what happened. They are quick to remove the nonrhythmic thing from network otherwise you know what will happen.

Microservice Architecture

nowadays people are talking about microservice but please be aware this may become nonrhythmic if you are not designing it properly. It will put an extra load on the system and it will not be possible to control.

Here’s a list of some potential pain areas and other cons associated with microservices designs:

•        Communication between service is unpredictable: Since everything is currently a free help, be extremely cautious while taking care of solicitations going between your modules. In one such situation, designers might be compelled to compose additional code to keep away from interruption. After some time, inconveniences will emerge when far off calls experience idleness.

•        More services equivalent to more assets: Multiple databases and exchange the board can be agonizing.

•        Global testing is troublesome: Testing a microservices-based application can be awkward. In a solid methodology, we would simply need to dispatch our WAR on an application worker and guarantee its availability with the basic database. With microservices, every reliant assistance should be affirmed before testing can happen.

•        Debugging issues can be more earnestly: Each assistance has its own arrangement of logs to experience. Log, logs, and more logs.

•        Deployment challengers: The item may require coordination among various administrations, which may not be as clear as sending a WAR in a holder.

•        Large versus little item organizations: Microservices are incredible for enormous organizations, however can be more slow to actualize and excessively convoluted for little organizations who need to make and repeat rapidly, and don’t have any desire to get hindered in complex arrangement.

Furthermore, so as to figure out which sort of design is most appropriate to the necessities of a particular venture, we have to address the accompanying inquiries:

•        How huge is the group? A bigger group can be more fit to microservices.

•        Are we as of now reliant on a solid assistance?

•        Is there somebody in the group with the aptitude to encourage microservice engineering?

•        Are we working for a solitary crowd? Microservices are most helpful when you’re working for a more different purchaser base.

With an enormous and developing framework (think Google, Netflix, Amazon, Uber… and so on.), microservices are unmistakably the better decision. Be that as it may, all things considered, does your undertaking contrast with an association as tremendous as Google?

So as to decide if microservice design is directly for you, you should initially evaluate your association’s needs, assets and culture.

Choose Monolithic if:

• You have a small team,
• Your application is simple,
• You don’t have microservice expertise,
• You want to launch your application as soon as possible.

Choose Microservices if:

• You have a complex application which you want to be scalable,
• You have microservice expertise.

You can see Rhythm is everywhere and if you lose any Rhythm, now you know what will happen. Rhythm should well support even team formation for any project. It is a responsibility of Team Leader to take everyone in Rhythm like music director.