VISHNU S R

Exciting change in JDK 15, change in its field layout strategy, both superclass and hierarchy gaps are closed. To run through example, the left most snapshot shows 3 classes in hierarchy, if we analyse field layout and memory bytes needed in JDK 8 in middle snapshot vs JDK 15 right most one. there are 8 bytes saving. With child classes fields adjusting in padding gaps in parent classes, there seems to be good memory saving in Java 15 and beyond. Chapter 11 of this article explains it with more granular details with compressedOops and other configurations. https://lnkd.in/grvc3Y8m #jdk15 #fieldlayout #java #heap #memory

15

🚀 **Exciting News!** 🚀 MuleSoft just dropped the **new SFTP Connector (v2.4)** on **November 13, 2024**! 🌟 Say goodbye to KEYBOARD_INTERACTIVE auth and hello to **PUBLIC_KEY, PASSWORD, or GSSAPI_WITH_MIC** methods. Get ready to streamline your file transfers like never before! 📈✨ #MuleSoft #SFTP #TechUpdate

6

Jio's Bold Cloud Storage Move: Is This the Start of a New Era? Jio is shaking things up with its offer of up to 100 GB of free cloud storage, directly challenging the dominance of giants like Google and Apple. This move isn't just about undercutting prices—it's part of a bigger strategy to fuel their "Jio Brain" AI initiative. By tapping into the data of millions of users, Jio aims to create AI solutions specifically tailored to India. But this bold step raises important questions about data privacy and the complexities of switching providers. Key learnings and takeaways- • Disruptive Strategy-Jio’s free cloud storage offer is a smart move to quickly capture attention and market share. • Ecosystem Building-By linking cloud storage with their AI projects, Jio is creating a system that keeps customers coming back. • Data-Driven Marketing-With all the user data they’re collecting, Jio can refine their marketing and make it more personalized. Could this be the game-changer for cloud storage in India? #Jio #CloudStorage #AI #content #marketing #learnings #branding

45

19 Comments

Is'nt every backend exists to serve front end? otherwise why it would called so? So you are suggesting 2 types of back ends? 1. "new" back end to front end 2. traditional back end? Question to all ? Where is bulk of business logic ... Now ? Tracing the history from 2000's 1. VB/Oracle Desktop App : Front end 50%, Backend (DB) 50%. Stored procedures and PL/SQL code encoded business logic 2. Early Web Apps - Front end (ASP/JSP) - 20%, Middle Tier (App server) 50% and database (30%) 3. Modern Rich Internet apps, Front end (10% or less), Microservices (85%) and 5% in databases. What do you think?

2

Next on my series about Spring REST API with Java: "Spring REST API: PathVariable, RequestParam, RequestBody and Input Validation: How to remain safe while serving client request" #spring #rest #api #input #validation #security https://lnkd.in/gbqqDktC

4

Good karma is real 🙏 Let's see some examples in software industry 🙂 Software Engineer 🧑‍💻 Good job - Helps colleague during debugging Good karma - Gets back to back fullstack development stories DevOps Engineer 👨🏻‍💻 Good job - Proactively fix issues Good karma - License cost for new tools gets approved Software Architect 🧑‍💻 Good job - Guides team from requirements understanding to application deployment Good karma - Implementation is very close to architecture goals, which brings you recognition Project Manager 👨🏻‍💻 Good job - Keep team focused on project objectives Good karma - Your project gets an extra budget to deliver new innovations Verification Lead 🧑‍💻 Good job - Able to find and fix good issues before release Good karma - Customers share feedback that application quality meets expectations Engineering Director 👨🏻‍💻 Good job - Keep compensation parity in the team Good karma - Able to find internal candidates as part of hiring for important positions #goodkarma #software #goodness #begood #dogood #realtalk

26

Pointers in Go (Golang) are essential for several reasons, primarily related to performance and control over memory management. Here are some key reasons why pointers are needed in Go: Efficiency: Passing large structs by value can be inefficient because it involves copying the entire struct. Using pointers allows you to pass the reference to the struct, avoiding the overhead of copying and improving performance. Mutability: When you pass a value to a function, Go creates a copy of that value. If you want a function to modify the original value, you need to pass a pointer to that value. This allows the function to directly access and modify the original variable. Nil Values: Pointers can be nil, representing the absence of a value. This can be useful for optional parameters or indicating an uninitialized or missing value. Interfacing with C Code: When using Go's cgo package to interface with C code, pointers are often required to pass data between Go and C. Data Structures: Pointers are fundamental for implementing data structures such as linked lists, trees, and graphs, where elements need to reference other elements dynamically. #Golang #GolangDeveloper https://lnkd.in/g8VHP2ye

7

My Story of How I improved single server pod efficiency to handle 150 concurrent users operating at 100% cpu usage to 900 concurrent users operating at 85% cpu usage It has been a long day and a long time since I had posted so here's some of my recent venture into servers, server-side latency and infra costs. So the story starts with a load test request for one of our apis on a Friday morning looking forward to push a new feature to prod by evening. My mind goes well that's a double edged sword when it comes to critical requests on a Friday :) Anyways It's a simple request with a small twist to it since I wanted to publish the results for both cached and non-cached behavior of the same api. I build my jmeter scripts and run it on Azure Load Runner and bam first surprise.... As the number of virtual users increased, our poor little single pod taking up the huge loads suffered and the latency gradually went up until certain breaking point where it couldn't handle the said number of concurrent users. Surprisingly the same pod could handle same rps with way less number of users! This pod had a spec of 2 cpu and 4G memory. The server could handle merely 29 users at 191ms which is < 200ms (standards) and this seemed too low.  Moreover at ~150 users the latency shot upto 48s and at ~200 users it had reached 3mins! This led me into a rabbithole trying to debug what might be issue which led me into profiling the memory and cpu usage during such loads and long story short the cpu usage was pretty high i.e., 100% but low memory. After a live profiling of such pods via VisualVm I was able to conclude the following: 1. Number of threads must be improved. 2. Threads must be efficiently used i.e., less waiting time on threads. 3. Reduce the cpu usage. The solution for the above problem was: 1. Tomcat thread and queue management for best use of available resources. 2. Server change from BIO to NIO mode (Non-Blocking IO) 3. Connection pooling 4. Increase Heap memory and set min and max to handle throttling. Now the trick is to not over-do the number of threads and tasks handled by a thread since it can increase the memory usage again trggering gc events which is bad. After fine ballet of all above mentioned fixes lo and behold a single pod could handle  900 concurrent users 1k RPS at 950ms with cpu as low as 85% and low gc activity!! #springboot #jmeter #backend #infra #costcutting

12

Replace the ToDo app projects on your resume with these 10 real time multi micro service architectured applications available for Free(No ifs and buts, no registration required). 1. My personal favourite demo app written by the developers/contributors of Open Telemetry. This project has front end, back end with multiple services, database, caching service, message queue and also a fake load generator. 2. Demo app by Backstage. Another CNCF project and another excellent demo app which hosts a near realtime website. If you are interested in building and deploying web applications definitely you should give it a try. 3. Sprint Petclinic is a mid level complexity Java sprint boot demo project. This app is used a lot in demos of open source projects because of its stability. If you are interested in java demo apps give it a try. 4. Sample voting application by Docker. A multi micro service project that I would highly recommend. Personally I used it for a Azure DevOps migration and implemention project on the channel. 5. Demo Chatbot by Redis. If you are interested in building and deploying chatbots, this project is an amazing option. 6. Demo Bookshop application by Keycloak. If you are interested in building and deploying advanced java frameworks apps written in quarkus, give this project a try. 7. Demo Playground application by Sysdig. This is a very simple app for beginners. If you are interested in exploring a simple application yet stable, give this a try. 8. A Bookinfo (review and rating site for books) application by Istio. Yet another very popular multi micro service architectured application. 9. GitOps demo app by Flux CD. If you are interested in learning GitOps and advanced continuous delivery using Flux, helm and kustomize give this project a try. 10. Demo javascript and Node.js project by Circle CI. You can find more details about the projects in my youtube video. All the above project links are shared in the pinned comment of the video. https://lnkd.in/gjxnGcmq Please don’t forget to share this useful information with every Developer and DevOps job aspirants that you know.

2,081

45 Comments

[Advise to younger software engineers]: If you are a younger software engineer, who would like to build a highly successful career in IT industry, my advise, as an industry veteran, is, "don't follow the mainstream path" and not be with the crowd. The mainstream path is becoming a "poster child" of frameworks, buzzwords, jargons, hypes, intellectual thoughts and labels, and adopt everything for the sake of it without understanding the basics of it and what it does and doesn't do. For example, if someone else heard about the buzzword "Microservices" (you don't need this distributed systems architecture for 99.9% of use cases), the mainstream path is without understanding it, just tied-up it with some tools and frameworks and claim that I am using this architecture by using those tools and frameworks. When there is a buzzword around AI, then the mainstream path is dive into it instead of focusing on your core product idea. Instead of this mainstream path, do learn core programming fundamentals and good engineering principles, and make "curiosity" to everything and ask a lot of questions to all of the narratives. When you heard about something learn it with a fresh mindset without any baggage of the past experiences but ask a lot of questions with curiosity in mind. Just understand what it does and doesn't do as there is no silver bullet in software engineering and architecture. When you look into evolutionary tools, for example ORMs, you must try to understand the history of such evolution and its basics, and in the example case of ORM, you must learn writing SQL. When your organisation uses Kubernetes or using a framework like Spring Boot and claim that using these are Microservices, then ask a question, how can be a distributed systems architecture by simply using some tools and frameworks. When your organisation write unit tests just for the sake of getting some test coverage number by doing some gimmicks after writing the production code, then ask a question at least to yourself (your questions to seniors may lose your job) what are the benefits of doing those things if we don't follow the core philosophy of writing unit tests and test-first approach. You should always focus on core fundamentals and principles, and different programming paradigms even with different languages, with a lot of curiosity. Curiosity with a great reading habits will differentiate you from the crowd and the mainstream. If your foundation is rock solid, you can become huge success in IT industry. LLMs won't be able to replace software engineers.

125

10 Comments

#TechByte: Virtual Threads vs. Goroutines 🚀 In the world of concurrency, **Java Virtual Threads** and **Go Goroutines** are powerful tools, but they come with different philosophies and strengths. Let's dive into a quick comparison! 🌐 **1. Java Virtual Threads**: Introduced with Project Loom, virtual threads in Java aim to simplify concurrent programming by providing lightweight, user-mode threads. These threads are managed by the JVM and are perfect for I/O-bound tasks. With virtual threads, you can scale your applications with minimal overhead, as they require fewer system resources compared to traditional OS threads. **2. Go Goroutines**: Goroutines are Go's way of handling concurrency, and they're designed to be lightweight and efficient. Unlike OS threads, goroutines are multiplexed onto fewer OS threads by the Go runtime, allowing thousands (or even millions) of goroutines to run concurrently. Goroutines are ideal for tasks that need to perform a lot of blocking operations, like network requests. **Key Differences**: - **Execution Model**: Virtual threads use the JVM's scheduler, while goroutines use the Go runtime's scheduler. - **Resource Efficiency**: Both are designed to be resource-efficient, but goroutines have been optimized for this for a longer period. - **Blocking Operations**: Goroutines handle blocking operations natively with less impact, while virtual threads in Java aim to reduce blocking via cooperative scheduling. **When to Use Which?** - Use **virtual threads** if you're heavily invested in the Java ecosystem and need seamless integration with existing Java libraries and frameworks. - Opt for **goroutines** if you're building from scratch in Go and need an ultra-lightweight solution for massive concurrency. #TechByte #Java #Go #Concurrency #VirtualThreads #Goroutines #Programming

20

1 Comment

An example OpenRewrite recipe to Create Aggregator class which executes methods from different classes which are passed as input https://lnkd.in/ggJaBpdq

8

1 Comment

Watch this enticing conversation with Saiyam Pathak ONLY if you're interested in: ✅ Becoming a top grade DevOps Professional ✅ Talking at Conferences internationally ✅ Want to create a successful tech startup - he's already created two! Above all, watch this if you want to: ✅ Understand the mindset and choices that led to these "dream" outcomes

15

If I have a system design round tomorrow, I will revise my DB concepts from these 8 posts I wrote in last 6 months. [1] How youtube scaled MySQL DB to millions of TPS https://lnkd.in/gWnu3yb4 [2] How Discord moved from MongoDB to Cassandra https://lnkd.in/gBqre_Sp [3] How to answer "why NoSQL" in an interview. https://lnkd.in/gFaNXzpw [4] Why did Facebook build Cassandra https://lnkd.in/gN8eaBuk [5] How to create schema in NoSQL DB https://lnkd.in/g5yS2cxu [6] How did Discord fixed database key during migration https://lnkd.in/gX3vRuGb [7] Complete guide for scaling a database https://lnkd.in/gh5HbjmZ [8] How does high write throughput database works https://lnkd.in/gG_yEpgA BONUS # 1: 30 sec interview conversation on databases https://lnkd.in/gcKxAmTh BONUS # 2: 4 database papers you must read https://lnkd.in/gUhxZ83b P.S. Save this post for future reference.

340

22 Comments

If the cost of software development goes down by factor by 2. Quantity of software built will go up by factor of 4. Number of software engineer required go up by 2. AI will increase software engineering job, not decrease. Nature of job will change.

8

Nail Your Platform Engineering Interview Preparing for a platform engineering interview? Here's some advice to help you stand out. First, ensure you understand the fundamentals. Brush up on your knowledge of cloud services, containerisation, and orchestration tools like Kubernetes. Familiarise yourself with the latest trends and technologies in the field. According to a recent survey by Tech Nation, 70% of UK companies are adopting cloud-native solutions. Knowing this can give you an edge. Next, practical skills are crucial. Hands-on experience with platforms like AWS, Azure, or Google Cloud can set you apart. Create a small project or contribute to open-source platforms to showcase your skills. Employers value candidates who can demonstrate their abilities with real-world examples. Finally, soft skills matter. Effective communication and problem-solving abilities are essential. Be ready to discuss how you've handled challenges in previous roles. Share stories that highlight your teamwork and adaptability. These qualities are often just as important as technical expertise. Comment below with your thoughts or connect with me if you're looking to hire or find a new role. Visit charles-simon.co.uk for more insights. #PlatformEngineering #JobSearch #CareerAdvice

1

This provides an excellent explanation of a fascinating GitHub bug and the steps taken to resolve it. Loved it! The intricacies of distributed systems are particularly challenging to grasp, requiring a deep focus on even the smallest details to fully understand their complexities. #redis #ratelimit #cache

3