Skip to main content

BIG DATA

OBJECTIVES : 

-> What is big data?
-> How to handle big data?
->Solutions for big data


BIG DATA:
Big data is a broad term for data sets so large or complex that traditional data processing applications are inadequate. Challenges include analysis, capture, data curation, search, sharing, storage, transfer, visualization, and information privacy.

                  Big data is a massive volume of data that refers to both structured and unstructured and difficult to process.It has mainly three aspects.They are:
             
                            1)velocity
                            2)volume
                            3)variety
velocity: size of the data.Big data is so massive that it gets accumulated at large amounts in very less amount of time.

 volume: Size of the data is very large that it can't be processed using conventional methods.

 variety: Big data deals with both structured and unstructured data.



How to handle big data:

                                 there are many solutions provided to handle big data efficiently over many years.
 Companies like yahoo,facebook, google and many more people all around the world have worked to provide solutions to this problem.Some of the solutions avalable for big data are hadoop,pig,hive,spark.

Solutions for big data:

                    Hadoop is a open source project developed by Apache with the white paper algorith released by google. Google released a algorithm which explains how the search gaint handles large amounts of data.
Code is developed for same by the developers of yahoo and many people all over the world.

Hadoop uses map reduce function and HDFS for processing big data.  




 




Labels:

Comments

Post a Comment

Popular posts from this blog

SQL Server

                                                                     SQL Server  Its been a while that I have updated my blog. Though Databases and SQL was something that I used to stay away as much as possible because for some reasons, I got to work on these all the day for 8-9 hours and sometimes haunting in the nights and weekends as well. However, it has been a good journey so far and I found some interesting stuff in SQL Server. So, this triggered an idea a couple of weeks back to share some cool stuff that I am learning in SQL Server over numerous sources. Hope I can make this a good series. As there are not much visitors to my blog, le...
4 comments
Read more

An TLS 1.2 connection request was received from a remote client application, but none of the cipher suites supported by the client application are supported by the server. The TLS connection request has failed.

If the certificate being used on the server was generated using the Legacy Key option in the certificate request form, the private key for that certificate will be stored in Microsoft's legacy Cryptographic API framework. When the web server tries to process requests using its new, Cryptographic Next Generation (CNG) framework, it appears that something related to the RSA private key stored in the legacy framework is unavailable to the new framework. As a result, the use of the RSA cipher suites is severely limited. To avoid the issue, you can try to generate the certificate request using the CNG Key template in the custom certificate request wizard.
Post a Comment
Read more

Remote Login Failure on Server

I ran into an interesting situation when executing a Remote Stored Procedure on Linked   Server using four part query.    Vista-3139 which is a SQL Server 2005 instance is linked to the SERV2003\SQLDUMMY which is a SQL Server 2000 named instance. When I tried to execute a stored procedure: EXEC [SERV2003\SQLDUMMY].SQLAdmin.dbo.sp_ddlevents   Got the following error message. Could not connect to server SERV2003\SQLDUMMY ' because '' is not defined as a remote login at the server. Verify that you have specified the correct login name. I checked the Security settings of the linked server and it was set to “Be made using the login's current security context", which is valid considering that the user has all the permissions to login to the remote SQL server. Then I changed the security context to use a SQL authentication, but still it failed with the similar error message as described above. To troubleshoot this further, I ran...
Post a Comment
Read more