Anupam Malviya

In this article we create an AWS MSK Kafka resource using AWS IAM Roles and Policies to authenticate user access. We then create an Aerospike Database cluster and insert some sample messages which in turn get shipped to AWS Kafka via the Aerospike Kafka Source connector. The article is focused around using IAM to authenticate clients and will guide the reader step by step on how to achieve this. https://lnkd.in/ebwJQ5bN

2

CNI choice in Kubernetes always dragged me in serious debates and comparisions. To add a humour laden flavour , here is a bit of gig :) A humorous comparison of Calico and Cilium: Note: I am a big fan of both and cant choose one over the other.. Calico: - Like a calico cat - colorful, playful, and a bit quirky. - "Hey, I'll just randomly assign some IP addresses and hope for the best!" - "Networking? Meh, I'll just wing it!" Cilium: - Like a ninja - stealthy, precise, and deadly efficient. - "I'll sneak up on those packets and route them with ease!" - "Networking? Child's play. I'm a ninja, hear me roar!" Of course, this comparison is all in good fun, and both Calico and Cilium are powerful tools in their own right. Calico is known for its flexibility and ease of use, while Cilium is renowned for its performance and security features. Choose the one that fits your needs, but remember - with great power comes great responsibility :). Have a great weekend !!

18

4 Comments

Learnings from Monzo: AWS reInvent A Deep Dive into Building a Digital Bank #WorkSmartWithK8s #kubernetes #microservices #apachecassandra #monitoring #prometheus #thanos #deepdive https://lnkd.in/eGVCYGjU

1

Last week, I spent a day at the AWS Summit in London. My reaction was surprisingly reassuring. I realised that despite AWS's reputation for releasing countless  new services, not much has changed since I started with AWS 10 years ago. Certainly, since the GA of EKS in 2018, there is little new at the platform's core. Until 2018, I read weekly updates, but I have not missed much from dipping in periodically instead. Most of what has changed is the addition of convenience services and some renames. The core is stable. This is reassuring. It makes AWS a predictable platform for those building cloud-native applications. The principles, patterns, and practices applied ten years ago still hold today, and by 2018, the toolbox was already well established. Now, it is refined but fundamentally unchanged, with concerns about observability, cost, and security still present and vendors still plugging the gaps. Personally, I have also spent time with Cloud Foundry, Kubernetes, IBM Cloud, OpenShift, Azure, and Google Cloud over recent years. I have my preferences #googlecloud, but I am still confident that the fundamentals of architecting cloud-native applications are transferable, no matter the vendor or technology. #AWSSummitLondon #cloudnative

33

7 Comments

Yesterday marked my birthday. Once the celebrations were over, I found myself reminiscing about my past year. A year filled with growth, challenges, and remarkable moments. One of those moments was my Tech talk on Unlocking the Secrets to Zero Incidents at Konferense`23 🎤 The talk was about how to minimize risk of incidents using my own SIGMA rule. (More on this in the video) 🗣 It was the first time that I addressed a gathering of over 1700 competent people. 🌍 It was the first time I addressed diverse people from over 50 countries. ⏲ It was the first time that I was presenting slides which were auto timed at 15 seconds. 🎊 It was not the first time when my legs were shaking but it was the first time, I got mentored so well that shaking didn't linger for long. With this post I want to share a glimpse of my talk and thank Klarna and amazing people working for it who provided me an opportunity to learn and showcase another skillset which I am very passionate about. 🙏 I will always cherish the loud applause as I entered the stage and the louder one when the speech concluded 😍 Some of you may like/celebrate this post which would be really nice. But it would be even nicer if you can take out 5 minutes and watch the video. Bonus gratitude if you leave some feedback too. 🙌 #techtalk #zeroincidents #conference #klarna #birthday

78

3 Comments

Today I spoke about scalability, vector search/multi dimensional data, Multi tenancy in TiDB TiDB, powered by PingCAP

54

1 Comment

🌻 𝐒𝐮𝐧𝐟𝐥𝐨𝐰𝐞𝐫𝐬 𝐚𝐭 𝐘𝐨𝐮𝐫 𝐒𝐞𝐫𝐯𝐢𝐜𝐞: 𝐒𝐭𝐚𝐧𝐝𝐢𝐧𝐠 𝐓𝐚𝐥𝐥, 𝐃𝐞𝐥𝐢𝐯𝐞𝐫𝐢𝐧𝐠 𝐕𝐚𝐥𝐮𝐞 🌻 In today’s ever-evolving landscape 🌍, the sunflower stands as a beacon of strength 🌟, symbolizing a 𝐡𝐨𝐥𝐢𝐬𝐭𝐢𝐜 𝐚𝐩𝐩𝐫𝐨𝐚𝐜𝐡 to scalable service delivery. With its towering presence 🌿, it offers 𝐚 𝟑𝟔𝟎-𝐝𝐞𝐠𝐫𝐞𝐞 view of #operationalexcellence 💼, ensuring no detail goes unnoticed 👀. 🌻 As the tallest in the garden, it becomes the 𝒄𝒆𝒏𝒕𝒓𝒂𝒍 𝒕𝒐𝒖𝒄𝒉𝒑𝒐𝒊𝒏𝒕 for growth 🌱 and 𝒑𝒓𝒐𝒂𝒄𝒕𝒊𝒗𝒆 𝒍𝒆𝒂𝒅𝒆𝒓𝒔𝒉𝒊𝒑 🤝, providing insights and 𝐮𝐧𝐩𝐚𝐫𝐚𝐥𝐥𝐞𝐥𝐞𝐝 𝐬𝐮𝐩𝐩𝐨𝐫𝐭 to every stakeholder involved. From its elevated vantage point 🏔️, the sunflower embodies the true essence of 𝐬𝐞𝐫𝐯𝐚𝐧𝐭 𝐥𝐞𝐚𝐝𝐞𝐫𝐬𝐡𝐢𝐩, driving cross-functional collaboration 🤲, streamlining service pathways 🛤️, and fostering maximum impact 🌍. Ready to cultivate a 𝐟𝐞𝐫𝐭𝐢𝐥𝐞 𝐞𝐜𝐨𝐬𝐲𝐬𝐭𝐞𝐦 of success? 🌻 Every touchpoint is nurtured 🌸, 𝐞𝐯𝐞𝐫𝐲 𝐧𝐞𝐞𝐝 𝐦𝐞𝐭 𝐰𝐢𝐭𝐡 𝐩𝐫𝐞𝐜𝐢𝐬𝐢𝐨𝐧 🎯, delivering results that are not just immediate but also sustainable for the long term ⏳. Let’s grow together 🌱, 𝐰𝐢𝐭𝐡 𝐬𝐮𝐧𝐟𝐥𝐨𝐰𝐞𝐫𝐬 𝐚𝐭 𝐲𝐨𝐮𝐫 𝐬𝐞𝐫𝐯𝐢𝐜𝐞—standing tall, delivering value every step of the way. 🌻✨ #Leadership #Collaboration #ServiceDelivery

3

What is Observab-ility? Is it a part of 'ility' family (most Non Functional Requirements are ilities e.g. availability, reliability etc). Do you still need monitoring if you have implemented observability. The answer to these questions is a resounding yes. Monitoring is the practice of measuring signals that tell about the status of critical resources needed by a software system to continue to function e.g. CPU usage, memory usage. If a system is out of CPU or Memory, it will deviate from its expected behavior. Monitoring is proactive. It will help you take actions, such as scaling out. Sometimes, there is a memory leak. Scaling up or scaling out does not help with memory leaks. Someone has to find the code leaking memory and fix it. Fixing it requires logs, traces, dumps, and many internals stats. This is where observability comes in. When something goes wrong, an observable system provides the tools to find what is really happening. Observability is reactive. If you are unable to find the root cause of an issue, you probably don't have observability in your system. You will resort to restarting the system, adding more resources, and other similar hacks. Monitoring is relatively easy to implement. Observability is hard to implement because you need to understand internals of the tech stack. Remember most of us have a thermometer, but we go to an expert for the blood test. Blood testing is observability, while temperature measurement is monitoring. Monitoring captures the symptoms and Observability leads to diagnosis. A developer cures it. #observability #monitoring #alerting #logging #softwareengineering #software #systemdesign

56

4 Comments

An interesting read on Card Fronting and why it is not allowed in Visa. Card fronting is when two or more different Payment Credentials or cards are linked together to complete a single Transaction using Back-to-Back Funding. For example, “front” card is funded transaction-by-transaction from one of the linked payment cards, issued by unrelated issuers. This is strictly prohibited by Visa Rules. Card-fronting is not permitted. No digital wallet operators can support “back-to- back funding” capability when combined with general-purpose payment network products at the “front” of the wallet.No Back-to-Back Funding with Fronting. Reference: https://lnkd.in/ggw54FFa

4

Three months integration testing. Can we swear on linked in ? Fark That was hard. Tens of thousands of code lines, thousands of user stories, over 500 features . Hard mahi. Defects and bugs, missed requirements, reversed integrations, weird UTC date issues …. UAT in a week. woo hoo ! Is transformation hard ? Yep. Why do most transformations fail ? Refer above. Stay the course.

102

1 Comment

Great to see Daniel Thornton, a highly experienced recruiter, having a go at the incredibly low rates on offer to contractors. See the comments of the attached post. Clients ultimately lose offering these low rates - the top people are unlikely to work for them. And every formerly high earning contractor I knew in my contracting days has left the market* - they're either retired, perm or taken their skills to other countries. #ir35 *a market requires buyers and sellers, so I use the term loosely, as there are almost no buyers remaining, so no functioning market https://lnkd.in/epSMnCmi

2

1 Comment

Just completed a course on Java Application Performance Tuning and Memory Management! The course provided practical explanations for the impact of String Pool size on application performance and covered micro and macro benchmarking for the application. Additionally, it explained minor and major GC with the help of a visualization plugin for Visual VM. The course also discussed helpful JVM flags for tuning java application performance. It's a great resource for Operations teams managing production Java applications and gives developers better insights for code-level decisions (e.g. choosing the load factor and initial capacity of HashMap and its impact on performance). #Java #PerformanceTuning #MemoryManagement #JVMflags #ApplicationPerformance

14

1 Comment

Are #APIs the #PowerSource for #OpenBanking’s #Rise? #api #embeddedfinance ------ https://lnkd.in/g3TYqMEW ------ As open banking takes root in the United States, the role of application programming interfaces (APIs) will become more widely known and appreciated. That’s one of the predictions and insights stemming from a recent PYMNTS interview with Seth Perlman, global head of product at payment facilitator i2c. An API, he said, as part of the “What’s Next in Payments” series, “is really just the interface to whatever’s ‘underneath’ it in terms of financial services or processing or commerce. So ultimately, an API is a scalable and rapid way to integrate to an underlying service, but it doesn’t take the place of whatever processing infrastructure, or other capabilities, lie underneath it.” But for those APIs to be embraced fully, they also need to demonstrate the ways in which firms can harness them to change financial services — and they also need to be broadly available to the developer community itself. Against that backdrop, and in pursuit of scale, said Perlman, the key is to design those APIs with interoperability in mind — to have at least some level of abstraction or commonality tied to the information that’s put “into” the API. Card-level data, for example, should be formatted in standardized fashion so that APIs can connect and pass that data to a broad range of underlying services. #Security and #Scalability “There’s an art,” said Perlman, “to API design to ensure there’s interoperability for a single type of input on the front end, being able to be passed to a number of downstream backend product services companies, no matter where they’re plugged into.” That need for standardization has given tailwind to a number of providers, including i2c, offering expertise in streamlining how that information is captured and passed to processors, middleware providers and anyone else who could be sitting in the “middle” of financial interactions. Perlman added that i2c has been “API centric from day one,” and has helped client firms in the midst of developing payment or a banking application to pick and choose the components that are most relevant to them and only do the work that’s necessary to integrate for that purpose. “There have been cases where our clients have integrated to debit processing capabilities and are using our fraud engine, but potentially maybe using someone else’s mobile app. That mobile app,” he continued, “and that mobile app developer can call our APIs to get transaction information, transaction history and ‘trigger’ other products and services that they need.” The FinTech that strives to offer point-of-sale financing can embed those options in a merchant’s checkout page in streamlined fashion, he said.

3

**Microservices: What Could Have Been a JOIN is Now a Thousand Network Calls** Microservices can be a boon or a bane, depending on how we wield them. The real challenge lies in picking the right tool for the job. In most scenarios, microservices might not be the best fit, but let’s face it, we developers love to dive into complexity—especially when it boosts our resumes. The core problem is that microservices have turned into a golden hammer for many. Instead of addressing their design flaws, they opt for microservices as a quick fix. Trashing microservices is just as bad as worshipping them. The actual truth is: that monoliths are usually fine, services are useful, and you probably don't need microservices for everything Where do you draw a line, and when do you cross it?

7

I am excited to share my first engineering blog. It explores how we, at Cashfree Payments, built a no-code custom report generator that automates the entire process of financial reporting with different banking partners, ensuring accuracy and timeliness, even under tight deadlines. Read the blog for more details.🚀 #Fintech #Engineering #tech

34

2 Comments