Data Analytics Ecosystem – AWS & Azure (Part 1)

Posted on April 11, 2017 by Sankeerth Reddy | Comments(2)

In the past decade, technologies around data analytics and business intelligence have seen a tremendous growth in number and reach. The emergence of Cloud has undoubtedly been a catalyst to this growth. Amazon Web Services and Microsoft Azure have both been working towards offering services for Collecting, Uploading, Storing and processing for Data. Below is an attempt to bring both the ecosystems forward into a comparative study of their services for various stages of Data Analytics. In a broad sense, the lifecycle of data to be analyzed goes through the below stages – Data Ingestion Preservation of Original Data Source LifeCycle Management and Cold Storage Metadata Capture Managing Governance, Security and Privacy Self-Service Discovery, Search and Access Managing Data Quality Preparing for Analytics Orchestration and Job Scheduling Capturing Data Change In this Part 1 of the blog, I would be exploring the first 5 stages of Data and how do both AWS and Azure serve the purpose. Data Ingestion Both AWS and Azure provide REST support so that users need to only perform HTTP(s) calls to be able to upload data onto their Cloud. Azure offers few connectors to migrate data to Databases, but currently doesn’t offer any specialized services to perform

Continue reading…

Zabbix- A Simpler way of Monitoring

Posted on March 8, 2017 by Sherin Shahanas | Comments(6)

Today, applications have evolved from standalone to the client-server model and ultimately to the cloud-based elastic application. Application performance can directly affect a business, hurting the revenue as customer struggle to complete the process. It’s always been difficult to see what’s going on inside the system. And doing so has become an essential part. Having a good monitoring tool will help us to understand the system status and determine when they are behaving normally and when they are behaving abnormally. When something goes wrong, the tool alerts quickly and then we can act on it and fix it without affecting customers. Zabbix is a well-known tool to do that for you. Why do we need Application Monitoring? Information gathering Large application produces a humongous number of data that should be monitored and analyzed for the performance and improvement of product and thereby better business. Around the clock monitoring Humans will never be able to monitor each server 24 X 7. But it is very crucial that any unexpected incident on the servers should be notified and act on it immediately. Pre-emptive Alerting Monitoring tool is an invisible team member who will alert you about unexpected things in the system. What

Continue reading…

Google’s strategy to counter AWS: Acquire mission critical AWS workloads. Will it work?

Posted on February 23, 2017 by Bhavesh Goswami | Comments(0)

Google has been on an aggressive buying spree on cloud. But they are acquiring only a specific kind of companies: the companies that support a mission critical AWS workload. Google has bought many companies in cloud, that were either only supporting AWS, or primarily supporting AWS workloads. Below are some examples of such acquisitions.

Continue reading…

AWS CodeBuild: A Fully Managed Build Tool

Posted on February 16, 2017 by Sherin Shahanas | Comments(1)

Integrate Code, Build Artifact, Manage release. If you know the pain of these processes you might need to look at AWS CodeBuild. Maintaining a project developed by many team members concurrently which is composed of different functions, environment, and languages, AWS CodeBuild is here to help you. AWS CodeBuild is a fully managed service that compiles your source code and gives you a software package which you can directly deploy into your servers. Instead of setting up and scaling your own build server fleet, you can use CodeBuild to streamline your development process. AWS CodeBuild is elastic, scalable, and easy to use. For each build, it launches a fresh, Isolated container-based environment and terminates it after the build process ends. You can also use CodeBuild as AWS CodePipeline Build Provider. Let’s look at the major Terminologies of AWS CodeBuild. • Source Repository – Location of your source code. • Build Environment – Your runtime environment. • IAM Role – Grants CodeBuild permission to access to specific AWS services and resources. • Build Spec – Build commands. • Compute Type – Amount of memory and compute power required. AWS CodeBuild uses Docker containers to build your code depending on your environment.

Continue reading…

Ramifications of Microsoft Azure’s Strategic Shift towards Cloud Solutions Provider (CSP) Partners

Posted on February 8, 2017 by Bhavesh Goswami | Comments(2)

Microsoft Azure is giving a tough fight to AWS in the public cloud market. Its no secret that AWS, with its 6 years of headstart in IaaS segment has more market share and more services. The latest announcement by Microsoft about Azure pay-as-you-go model not available in the MPSA licensing model gives us a hint on the strategic initiative by Microsoft Azure to capture more market share. Before we begin, let me share few licensing models with which microsoft sells Azure. Microsoft Online Subscription Program (MOSP) This licensing model is the subscription based model which is the default option when you go to the Azure portal and create an account using your credit card. You can also use this model to procure products like office 365, Dynamic CRM, etc. Most small and medium business, and individual developers procure Azure in this fashion. This is the classic Pay-as-you-go model with no prepaid commitments. Enterprise Agreement (EA) EA is a volume licensing package offered by Microsoft which primarily targets large organizations that have 500 or more personal computers. Although this is primarly used to buy software like Windows and SharePoint, Azure can be bought with this licensing model. There is usually some

Continue reading…

Lagging Behind Because of Logs? ELK Stack to the Rescue!

Posted on November 22, 2016 by Priya Panke | Comments(0)

One of the common mistakes done by most of the professionals is not using valuable data called ‘Logs’. Because of the quantity of logs generated, the chances of using them becomes very less. Logs are used only to debug in case of failure or issues, but it can be used for much more For Example: Monitor processes Finding the root cause of the issue being faced Analyze flow and performance of processes and many more The collections and analyzing of the log becomes extremely difficult because of the diversity generated. For example we have access logs, error logs, application logs etc. which are associated with an application or a server. In this blog, I will be demonstrating how to install and configure ELK Stack. ELK stands for: Elasticsearch, Logstash and Kibana. Before we begin, let’s have a quick overview of the overall architecture with their components, followed by the implementation procedure.   Architecture of ELK Stack:   ElasticSearch: It is an Indexing, Storage and Retrieval engine Powerful open-source full-text search library A Document is the unit of search and index Fast search against large volumes De-normalized document storage: Fast, direct access to the data Broadly distributed and highly scalable Logstash:

Continue reading…

Why do we opt for AWS Mumbai Region as an Indian cloud customer?

Posted on September 9, 2016 by Amrendra Kumar | Comments(0)

Are you an Indian AWS (Amazon Web Services) Cloud Customer? Do you want to adopt AWS Mumbai Region for your production? Then we have an analysis for you which will help you to decide whether to go for AWS Mumbai Region or not. In this blog, we’ll look at aspects like “cost comparison, services availability, S3 object download speed test, latency check, compliance” between near and famous regions. For those who are not familiar to AWS, a region in AWS is a term which describes a set of AWS resources within a geographic area. Each region contains multiple, isolated locations calledAvailability Zones (AZ). In June 2016, AWS announced Asia Pacific (Mumbai) Region as 13th AWS Region. Now, AWS provides 35 AZs across 13 regions globally. There are more than 75,000 India-based customers who are already using other AWS Regions to save costs, accelerate innovation, and widen their geographic reach in minutes. What does Mumbai region mean to all the hitherto existing customers or new customer? Mumbai Region allows global and India-based developers, start-ups, enterprises, government organisations and non-profits to leverage the AWS Cloud to run their applications from India and provide even lower latency to India-based end users. Two separate

Continue reading…