Wednesday, 25 September 2024
Saturday, 21 September 2024
How to Uninstall JDK 17 on Windows 11 | Java JDK 17 Uninstallation on Windows
🚀 Level Up Your Java Skills!
Subscribe to Ram N Java for easy-to-follow coding tutorials!
SUBSCRIBE TO OUR CHANNELHow to Uninstall JDK 17 on Windows 11
Whether you need to upgrade to a newer version or simply want to clean up your development environment, uninstalling the Java Development Kit (JDK) 17 on Windows 11 is a straightforward process. Follow this simple, step-by-step guide to ensure it's removed correctly.
Step 1: Using the Control Panel
The most reliable way to remove software on Windows is through the standard uninstallation tool:
- Open the Start Menu and type "Control Panel."
- Go to Programs and then click Programs and Features.
- Scroll down the list until you find "Java(TM) SE Development Kit 17".
- Right-click it and select Uninstall. Follow the prompts to finish.
Step 2: Clean Up Environment Variables
After uninstalling the software, it's a good idea to remove any leftover paths to prevent system errors:
- Search for "Edit the system environment variables" in the Start Menu.
- Click the Environment Variables button.
- Under "System variables," look for JAVA_HOME. If it points to JDK 17, you can delete it.
- Also check the Path variable and remove any lines related to JDK 17.
Step 3: Verify the Removal
To make sure everything is gone, open your Command Prompt (cmd) and type:
If uninstalled correctly, Windows should tell you that 'java' is not recognized as an internal or external command.
💡 Need More Help?
If you're planning to install a different version of Java, check out my other tutorials on the Ram N Java YouTube channel for full installation and setup guides!
Friday, 20 September 2024
Thursday, 19 September 2024
Thursday, 12 September 2024
Monday, 9 September 2024
How Amazon SQS Works: Visual Guide with Sequence Diagrams | Amazon SQS Tutorial
🚀 Master the AWS Ecosystem!
Subscribe to Ram N Java for more visual guides and deep dives into cloud-native Java.
SUBSCRIBE ON YOUTUBEIntroduction
Amazon Simple Queue Service (SQS) is the backbone of many modern distributed systems. To truly master SQS, it is helpful to look beyond the code and understand the flow of messages between services. In this guide, we use sequence diagrams to illustrate how producers and consumers interact with SQS queues.
The Producer-Queue Interaction
The journey starts with the Producer. Whether it's a web application or a microservice, the Producer sends a message to the SQS queue using the SendMessage API call. Once the message is safely stored in SQS, the service returns a Message ID to the Producer, confirming receipt.
The Consumer Polling Mechanism
Unlike some messaging systems, SQS uses a polling model. Consumers must actively request messages using the ReceiveMessage API. During this visual journey, we see the Consumer asking SQS: "Do you have any messages for me?"
- Short Polling: SQS returns a response immediately, even if the queue is empty.
- Long Polling: SQS waits up to 20 seconds for a message to arrive before responding, reducing cost and empty responses.
Visibility Timeout and Deletion
When a Consumer receives a message, SQS doesn't delete it immediately. Instead, it starts a Visibility Timeout. During this time, the message is hidden from other consumers so it won't be processed twice.
Once the Consumer successfully processes the message, it must call the DeleteMessage API using the Receipt Handle. This final step removes the message from the queue forever.
Conclusion
Visualizing these steps through sequence diagrams makes the architecture of decoupled systems much clearer. By understanding the lifecycle of an SQS message—from production to visibility timeout and final deletion—you can build more resilient and scalable cloud applications. Happy architecting!
Tuesday, 3 September 2024
How to Set Up and Use Amazon AWS CLI on Windows/Mac/Linux | AWS CLI Installation and Basic Usage
Ready to Level Up Your Cloud Skills? ☁️
Don't miss out on more AWS and Java tutorials. Join our growing community today!
👉 SUBSCRIBE TO RAM N JAVAIntroduction
The AWS Command Line Interface (CLI) is a unified tool that allows you to manage your AWS services from the terminal. Instead of clicking through the AWS Management Console, you can run powerful commands to automate your workflows and manage resources like S3, EC2, and SQS efficiently.
Step 1: Installing AWS CLI
Depending on your operating system, follow the steps below:
Windows
- Download the AWS CLI MSI Installer from the official AWS website.
- Run the installer and follow the "Next" prompts until finished.
macOS
brew install awscli
Linux
curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip" unzip awscliv2.zip sudo ./aws/install
Step 2: Configuring Your Credentials
Once installed, you need to link the CLI to your AWS account. First, create an IAM User in the AWS Console to get your Access Key and Secret Key. Then, run:
aws configure
Provide the following when prompted:
- AWS Access Key ID
- AWS Secret Access Key
- Default region name (e.g.,
us-east-1) - Default output format (e.g.,
json)
Step 3: Essential AWS Commands
Amazon S3 (Storage)
List all your buckets:
aws s3 ls
Create a new bucket:
aws s3 mb s3://my-unique-bucket-name
Amazon EC2 (Servers)
List your running instances:
aws ec2 describe-instances
Amazon SQS (Queues)
Create a simple message queue:
aws sqs create-queue --queue-name MyQueue
Conclusion
Mastering the AWS CLI is a game-changer for cloud engineers. It allows for faster management, easy scripting, and powerful automation. Start practicing these commands today to streamline your cloud operations!