Posts

Showing posts with the label apache-storm-topology-example

Featured Post

How to Build CI/CD Pipeline: GitHub to AWS

Image
 Creating a CI/CD pipeline to deploy a project from GitHub to AWS can be done using various AWS services like AWS CodePipeline, AWS CodeBuild, and optionally AWS CodeDeploy or Amazon ECS for application deployment. Below is a high-level guide on how to set up a basic GitHub to AWS pipeline: Prerequisites AWS Account : Ensure access to the AWS account with the necessary permissions. GitHub Repository : Have your application code hosted on GitHub. IAM Roles : Create necessary IAM roles with permissions to interact with AWS services (e.g., CodePipeline, CodeBuild, S3, ECS, etc.). AWS CLI : Install and configure the AWS CLI for easier management of services. Step 1: Create an S3 Bucket for Artifacts AWS CodePipeline requires an S3 bucket to store artifacts (builds, deployments, etc.). Go to the S3 service in the AWS Management Console. Create a new bucket, ensuring it has a unique name. Note the bucket name for later use. Step 2: Set Up AWS CodeBuild CodeBuild will handle the build proces

Apache Storm Architecture Tutorial Flowchart

Image
There are two main reasons why Apache Storm is so popular. The number one is it can connect to many sources. The number two is scalable. The other advantage is fault-tolerant. That means, guaranteed data processing. The map-reduce jobs process data analytics in Hadoop. The topology in Storm is the real data processor. The co-ordination between Nimbus and Supervisor carried by Zookeeper Apache Storm The jobs in Hadoop are similar to the topology. The jobs run as per the schedule defined. In Storm, the topology runs forever. A topology consists of many worker processes spread across many machines.  A topology is a pre-defined design to get end product using your data. A topology comprises of 2 parts. These are Spout and bolts. The Spout is a funnel for topology Two nodes in Storm Master Node: similar to the Hadoop job tracker. It runs on a daemon called Nimbus. Worker Node: It runs on a daemon called Supervisor. The Supervisor listens to the work assigned to