Anil N S

Observability just not ticks the monitoring, metric or alerting part but also an efficient way to take decisions on capacity planning, Performance optimisation and most importantly, keeping the user experience at its best. #linkedinlearning #devopsconcepts 

18

🔍 **Avoiding Static Method Calls for Better Testability in Java** Just wanted to share a quick thought on testing practices in Java, particularly when it comes to static method calls. While they might seem convenient, they can pose challenges when it comes to unit testing with JUnit. Using static methods tightly couples your code to specific implementations, making it difficult to substitute dependencies during testing. This can lead to brittle tests and hinder the ability to isolate and verify behaviors. Instead, consider dependency injection and object-oriented principles. By injecting dependencies or using interfaces, you can decouple your code, making it more modular and testable. Here's a quick example: ```java // Before: public class MyClass { public void myMethod() { StaticClass.staticMethod(); } } // After: public interface MyDependency { void doSomething(); } public class MyClass { private final MyDependency dependency; public MyClass(MyDependency dependency) { this.dependency = dependency; } public void myMethod() { dependency.doSomething(); } } ``` By following this approach, not only do you improve the testability of your code, but you also promote cleaner, more maintainable codebases. Let's strive for code that's not only functional but also easy to test and evolve. What are your thoughts on this? #Java #JUnit #TestingBestPractices #CleanCode

3

Two young IT professionals, Ashwini and Anish, tragically lost their lives in Pune due to the reckless actions of a 17-year-old driving an unregistered Porsche at 150 km/hr. This incident raises serious questions about accountability: an unregistered car, a minor driving without a license, and a club serving alcohol to minors. Despite these grave violations, the minor received VIP treatment and swift bail because of the local MLA and team of lawyers. This case underscores the stark contrast in how justice is served based on one's socio-economic status. The law must be enforced equally, without bias, to prevent such injustices. PS: We’re voting for criminals, we’re responsible!! #justice #roadsafety #equalityinlaw #publicsafety

68

💡 Use 𝐫𝐞𝐜𝐮𝐫𝐬𝐢𝐯𝐞 flag along with 𝐤𝐮𝐛𝐞𝐜𝐭𝐥 𝐞𝐱𝐩𝐥𝐚𝐢𝐧 command to get all the fields available for that Kubernetes resource. Following is the example command for deployment resource. >>> 𝘬𝘶𝘣𝘦𝘤𝘵𝘭 𝘦𝘹𝘱𝘭𝘢𝘪𝘯 𝘥𝘦𝘱𝘭𝘰𝘺𝘮𝘦𝘯𝘵 --𝘳𝘦𝘤𝘶𝘳𝘴𝘪𝘷𝘦 and then, If you want to deep dive into any of the field, use following command along with field name. In this scenario, I am looking for 𝘥𝘦𝘱𝘭𝘰𝘺𝘮𝘦𝘯𝘵.𝘴𝘱𝘦𝘤.𝘴𝘵𝘳𝘢𝘵𝘦𝘨𝘺 >>> 𝘬𝘶𝘣𝘦𝘤𝘵𝘭 𝘦𝘹𝘱𝘭𝘢𝘪𝘯 𝘥𝘦𝘱𝘭𝘰𝘺𝘮𝘦𝘯𝘵.𝘴𝘱𝘦𝘤.𝘴𝘵𝘳𝘢𝘵𝘦𝘨𝘺 #kubernetes #devops #docker #sre #hackwithharsha #python #java

3

1 Comment

Surya Narayanan R. — who is part of the #HR team at #FidelityInvestmentsIndia — talks about how he has benefited from the #learning hours program at the firm. Read more about learning at Fidelity here: https://lnkd.in/e27uQw4U #FidelityLearns #LearningatFidelity Fidelity Investments #FidelityAssociate

1

You will most probably fail your System Design interview if you don't know these 3 fundamental concepts !!! What Is Forward Proxy & Why It’s Important ? https://lnkd.in/db-qdHBQ What Is Reverse Proxy & Why Is It Important ? https://lnkd.in/dyQRQJFC What Is Load Balancing, How it works & Why should you know it ? https://lnkd.in/gGmc7NuU I write no BS stuff about Python, System design & AI/ML. You can stay up to date with my work on my free newsletter by subscribing to it https://t.co/8o04bSBt1I

14

1 Comment

Abysmal standards and policies for a designated 3/4-star hotel, Lemon Tree Hotels has stooped down to when I was trying to make a reservation of two nights for myself and family in the Hitech city, Hyderabad branch. Practically as per their 'policy', a customer should pay whatever they are charging but without any guarantees on the booking made. How? The room finally allocated with could be subject to availability on the day you checkin. You could get a below expectation or charged room and that would be under the excuse of written 'hotel policies' on your booking mail. No documented pricing guarantee for a customer, unless they will want you to pay upfront. the reservation executive will promise you a definite/negotiated rate but verbally. As per their 'policies', they will not provide it to you in writing or a simple mail committing you a service/hospitality (room type, discounts, charges, etc) guarantee as made verbally. You need this as more often than not, you could become a victim of service cheating made verbally by the service executive on the day of checkin. How do you rely over a person's verbal commitments when in the mail confirmation of booking, they mention all the standard rates and policies you are going to get which could be easily denied to the customer at the time of checkout or pay at the hotel before checkin or even with the credit card details provided at the time of booking. The reservation team tries to cheat you with false information trying to make you book a higher prices room by saying that the room which you have selected are already sold out and the availability on their official site is not completely updated, when they are themselves checking the availability in their own system. you could easily get cheated to checkin to a lower grade room behind the policy or availability. When you raise concern over this, you get out a templated mail, attached here. you can have the details here as after the 4 attempts of reserving the room in the Hyderabad hitech city, the only response i have is "they are looking into this matter and will get back as soon as possible." but no solution yet. Also they have a policy of early checkin charges and as per room availability. this is understandable but what came stood is that while these policies are different from branch to branch, the cental reservation team executive told me for early checkin would be chargeable by 699 +taxes on the day of checkin. Such policies can be made standard across all branches of in the country as i have seen in other multi-starred hotels, but keeping charges behind the grey excuse of hotel policy is cheating. To support such a deceiving policy, one of the executives said was arrogant enough to say that this hitech city branch, hence such policies. Now people could detest my opinion or agree. But in my personal opinion, these practices puts customers in a dark area towards his/her booking reservations as the customer are being cheated.

42

6 Comments

Saurabh Netravalkar is an Artificial Intelligence engineer. So you can understand how AI is impacting cricket 🙃. Meanwhile, Oracle employees are enjoying such memes: #SaurabhNetravalkar #USACricket #SoftwareEngineer #Inspiration #CricketJourney #DualCareer #SuccessStory #CricketAndTech #SportsAndAcademics #CricketLife #CricketFans #USA #IndiaToUSA

4

Thrilled to see my article on the Digital Transformation in Fintech published on TechGig! Grateful for the opportunity provided by Tietoevry to share my insights. Looking forward to continuing the conversation and contributing to the evolving landscape of digital banking. Tietoevry Banking #tietoevrybanking #fintech #financialservices #futureofmoney #DigitalTransformation #BankingInnovation

59

4 Comments

𝗜𝗻𝘁𝗲𝗿𝗲𝘀𝘁 𝗥𝗲𝗮𝗱 - 𝗞𝗮𝗿𝗽𝗲𝗻𝘁𝗲𝗿 𝗘𝗳𝗳𝗲𝗰𝘁𝘀   Came across this interesting blog https://lnkd.in/gvXvc4T7 about Karpenter effects.   Please read https://lnkd.in/g2XnwB7z previous post about Karpenter. 🔶 𝘾𝙡𝙪𝙨𝙩𝙚𝙧 𝙐𝙥𝙜𝙧𝙖𝙙𝙚𝙨 𝙖𝙧𝙚 𝙎𝙚𝙖𝙢𝙡𝙚𝙨𝙨   Without Karpenter, EKS-managed node groups have tight coupling between the control plane and node group upgrades. Any issue, like configuration errors or instance shortages, could cause failed stack upgrades and rollback loops.   With Karpenter, Control plane, and node pool upgrades are decoupled, the Control plane is upgraded at first, Karpenter asynchronously upgrades worker nodes by marking ‘Drifted’ tag if it does not match the target AMI Vesion. Drifted nodes are gradually replaced. 🔶 𝙁𝙞𝙣𝙚-𝙂𝙧𝙖𝙞𝙣𝙚𝙙 𝘾𝙤𝙣𝙩𝙧𝙤𝙡 𝙊𝙫𝙚𝙧 𝘿𝙞𝙨𝙧𝙪𝙥𝙩𝙞𝙤𝙣𝙨   Karpenter’s ability to respect Pod Disruption Budgets (PDBs) has been a significant improvement. The Cluster Autoscaler—even with the serialized option—would force-remove nodes after a short timeout, often leading to service disruptions. Karpenter works patiently within the disruption limits that are defined. 🔶 𝙁𝙡𝙚𝙭𝙞𝙗𝙞𝙡𝙞𝙩𝙮 𝙬𝙞𝙩𝙝 𝙄𝙣𝙨𝙩𝙖𝙣𝙘𝙚 𝙏𝙮𝙥𝙚𝙨   Karpenter abstracts away this complexity by defining instance requirements rather than instance types. It automatically selects the most appropriate and cheapest instances available. This flexibility mitigates the risk of instance exhaustion as well. It can dynamically migrate to cheaper/better nodes if they are available. 🔶 𝙀𝙣𝙝𝙖𝙣𝙘𝙚𝙙 𝙈𝙚𝙩𝙧𝙞𝙘𝙨 𝙖𝙣𝙙 𝙄𝙣𝙨𝙞𝙜𝙝𝙩𝙨   Karpenter provides a wealth of metrics. Drift detection, node disruption counts, and pod scheduling times are useful ones. 𝗖𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲𝘀 𝘄𝗶𝘁𝗵 𝗞𝗮𝗿𝗽𝗲𝗻𝘁𝗲𝗿 🔶 𝙍𝙞𝙜𝙝𝙩 𝙘𝙤𝙣𝙛𝙞𝙜𝙪𝙧𝙖𝙩𝙞𝙤𝙣 𝙤𝙛 𝙋𝙤𝙙 𝘿𝙞𝙨𝙧𝙪𝙥𝙩𝙞𝙤𝙣 𝘽𝙪𝙙𝙜𝙚𝙩 (𝙋𝘿𝘽)   Without PDBs, Apps could experience disruptions. At the same time, overly strict PDBs hinder maintenance. 🔶 𝙏𝙝𝙚 “𝘾𝙝𝙚𝙖𝙥𝙚𝙨𝙩 𝙁𝙞𝙧𝙨𝙩” 𝙋𝙞𝙩𝙛𝙖𝙡𝙡   While Karpenter’s cost-optimization is generally beneficial, it’s not always ideal. For example, the m5a instances were marginally cheaper($.01/hr) than m6a instances but m6a has significantly better performance. A possible workaround is to set a higher weight for 6th-generation instances neglecting the 5th-generation. 🔶 𝗦𝗰𝗵𝗲𝗱𝘂𝗹𝗶𝗻𝗴 𝗟𝗮𝘁𝗲𝗻𝗰𝘆   With Karpenter’s dense packing of nodes, there are fewer idle resources available at any given time. When a sudden demand spike occurs, there may not be an immediate capacity to schedule new pods, waiting for karpenter to provision nodes. One possible option is to use PriorityClass to schedule lower-priority placeholder pods that can be preempted when higher-priority pods need to be scheduled.

10

I agree with Govardhana Miriyala Kannaiah and would like to add my thoughts. In my experience, it's crucial to meticulously plan and execute the baseline, or build phase, by following best practices and taking into account your organization's unique requirements. While continuous improvement and optimization are essential, regardless of how robust your build phase is, a well-thought-out initial architecture can significantly reduce rework and costs in the future.

5

Executable (computational) graphs and diagrams in Java I've been using executable/computational graphs to manage complexity for quite a while, including graphs created from Drawio diagrams. This Medium story https://lnkd.in/dfs5e9A9 provides a high-level overview of the approach with links to detailed documentation and code. In my opinion, there are many applications for graphs in the enterprise. They can be used to "connect the dots" between different systems and build a holistic model of how an organization operates.

7

1 Comment

💡𝗧𝗶𝗽𝘀 : 𝗩𝗲𝗿𝘁𝗶𝗰𝗮𝗹 𝗦𝗹𝗶𝗰𝗲 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲 💡𝗜𝗻𝗱𝗲𝗽𝗲𝗻𝗱𝗲𝗻𝗰𝗲 𝗮𝘀 𝗮 𝗩𝗘𝗥𝗧𝗜𝗖𝗔𝗟 𝗦𝗟𝗜𝗖𝗘! In honor of India’s Independence Day, I’m excited to showcase how Vertical Slice Architecture (VSA) and Clean Architecture principles can be applied to create maintainable and modular applications. By applying VSA with Clean Architecture, we build scalable and modular solutions, reflecting both the spirit of innovation and our dedication to clean code. 𝙃𝙖𝙥𝙥𝙮 𝘾𝙤𝙙𝙞𝙣𝙜! 👍 #CSharp #CleanArchitecture #VerticalSlice #SOLID #IndependenceDay #CQRS #VSA #SOLIDPrinciples #SRP #DIP

11

1 Comment

Predicting the future isn't magic; its Artificial Intelligence Arindam Paul – VP – #AI and #ML at #FidelityInvestmentsIndia writes in CXOToday about the impact of #AI in our world today and what it means for industries, the job market, and the world at large. “We’re living in an exciting period,” he says. Check out these fascinating perspectives on #futuretrends from a leading practitioner in the space. Fidelity Investments #FidelityAssociate

3

Q: Which approach is best for a high-read, low-write database workload? A) Sharding B) Replication C) Caching

5

1 Comment

It was an interesting session on Platform Engineering.

2