Wednesday, 5 November 2014

Hadoop Benefits - Kapil Sharma

Hadoop Benefits:

Every day approx 3 exabytes (2.5×1018) of data were created globally.

Benefits: If analysed than they reveal patterns, trends, and associations, especially relating to human behaviour and interactions.

Low cost: Hadoop is open-source framework. So its free. 

Computing power: It has distributed computing model which quickly process very large data volumes. The more nodes(computing) you use the more processing power your hadoop setup going to have.

Scalability: Easily increase your hadoop system simply by adding more nodes. Less IT administration is required.

Storage flexibility: Hadoop includes unstructured data like text, images and videos in a single go. Users can store as much data as they want and decide how to use it later period.

Inherent data protection and self-healing capabilities: Data and application processing are protected against hardware failure. If a system(node) goes down, jobs are auto redirected to other systems to make sure the distributed computing does not leads failure. And it auto stores multiple data copies of input data.

What is Hadoop - Kapil Sharma

What is Hadoop?

Hadoop - is an open-source software framework for storing and processing big data in a distributed fashion on large clusters of commodity hardware. Essentially, it accomplishes two tasks: massive data storage and faster processing.

Currently three core components are included with your basic download from the Apache Software Foundation.


HDFS - the Java-based distributed file system that can store all kinds of data without prior organization.

MapReduce – a software programming model for processing large sets of data in parallel.

YARN – a resource management framework for scheduling and handling resource requests from distributed applications.

What is Big Data - Kapil Sharma

BigData: 

Extremely large data sets both structured and un-structured.

Four Vs of big data: volume, velocity, variety, variability and complexity.

Benefits

If analysed than they reveal patterns, trends, and associations, especially relating to human behaviour and interactions.

Every day approx 3 exabytes (2.5×1018) of data were created.

Try this cmd on google search: "?intitle:index.of?mp4 Oracle"

Thursday, 4 September 2014

Scrum Team - Kapil Sharma

Scrum Team


A breif overview of scrum team members: 

1.) Product Owner (PO)
2.) Developement Team (DT)
3.) Scrum Master (SM)

Thursday, 12 June 2014

Software Development Models: Scrum Vs Waterfall

As the software industry growing, it also leads many new technologies and software design architectures to evolving along with that.
As software designer you may came cross software development models. Mainly Waterfall model is the first choice of the software designers. But these days many software designers prefer Scrum based software development life cycle.
Waterfall Model:
The software development work goes in phase manner.
1.) Requirements
2.) Design
3.) Development
4.) Testing
5.) Maintenance
Suppose a client wants software to do stock trading and the time of building this software takes 12 months. The client shares his requirements in Jan. (first month) and by Dec. (last month) he/she able to see how the software works out.
There was no chance / choice of software requirements to change or any preview of the software product. So there was a complete blackout of more than 10 months for client side.
Whereas Scrum the new kid in the town believes that software development is a creative art where a big software product cut into small shippable product and client can change the requirements and view the shippable software in weeks based time frame rather than waiting to get a full finished software product.
Now, in scrum all this depends upon the PBI (Product Backlog Items) these are user stories or you can small chunks of bigger software requirements. These can be written by a scrum team consists of a ‘Product owner’ a ‘Scrum Master’ and ‘Development team’. All can write these user stories on client software requirements where as the P.O (product owner) he/she has the final authority to put these PBI in the sprints or iterations (these are time-bound week based software development cycle), in scrum a sprint can be 1-4 week maximum.
Scrum Sprint:
1.) Sprint 1, X items
2.) Sprint 2, X + Y items
3.) Sprint 3, X + Y + Z items
So, after ending of each sprint the scrum team show the client a workable software item. And this help client to check the software is building in the way he/she wants. If client thinks new or changes required, he suggest and these new C.R (change request) can be added in the next sprint.
So, in nutshell the scrum software design model basically cut short the margin of error of wrong software development and its leaps ahead of older development models.

Tuesday, 29 April 2014

What is Scrum?

Scrum is a methodology developed under Agile framework. The main people behind this methodology are 'Ken and Jeff'. They are the seasoned software developers.  

For example, think like 'Agile' is an umbrella and 'Scrum' is one edge of that framework.  

Generally scrum methodology used in software development through out the globe. 
The name scrum from a sport known as rugby : ) 

A scrum team having these following player or members:
1.) P.O: Product Owner
2.) SM: Scrum Master
3.) Team: Developers + QA