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

Internet Of Things Basics (Part-1)

IBM investing $3 billion dollars on internet of things(IOT). What is IOT -It estimates that 90 per cent of all data generated by devices like smartphones, tablets, connected vehicles and appliances is never analysed or acted on.

IOT Protocols
IOT Protocols

IoT Basics to Read Now

In simple terms, it means machine-to-machine connecting. The emergence of the Internet of Things (IoT) destroys every precedent and preconceived notion of network architecture. To date, networks have been invented by engineers skilled in protocols and routing theory.

But the architecture of the Internet of Things will rely much more upon lessons derived from nature than traditional (and ossified, in my opinion) networking schemes.

It will consider the reasons why the architecture for the Internet of Things must incorporate a fundamentally different architecture from the traditional Internet, explore the technical and economic foundations of this new architecture, and finally begin to outline a solution to the problem.

Why internet of things require new solution


The architecture of the original Internet was created long before communicating with billions of very simple devices such as sensors and appliances was ever envisioned.

The coming explosion of these much simpler devices creates tremendous challenges for the current networking paradigm in terms of the number of devices, unprecedented demands for low-cost connectivity, and impossibility of managing far-flung and diverse equipment.

Although these challenges are becoming evident now, they will pose a greater, more severe problem as this revolution accelerates.

Related:  15 Hot IT Jobs

New generation devices

  1. But the vast majority of devices to be connected in the coming IoT are very different. They will be moisture sensors, valve controls, "smart dust," parking meters, home appliances, and so on. These types of end devices almost never contain the processors, memory, hard drives, and other features needed to run a protocol stack.
  2. These components are not necessary for the end devices' prime function, and the costs of provisioning them with these features would be prohibitive, or at least high enough to exclude wide use of many applications that could otherwise be well served. So these simpler devices are very much "on their own" at the frontier of the network.
  3. How things are connected: Billions of devices worldwide will form a network unprecedented in history. Devices as varied as soil moisture sensors, street lights, diesel generators, video surveillance systems—even the legendary Internet-enabled toasters—will all be connected in one fashion or another.

Comments

Popular posts from this blog

How to Fix datetime Import Error in Python Quickly

How to Check Kafka Available Brokers

SQL Query: 3 Methods for Calculating Cumulative SUM