Tick-Bank Web Traffic Analytics Implementation Guidelines

Web Traffic Analytics Implementation Guidelines

Question

Tick-Bank is a privately held Internet retailer of both physical and digital products founded in 2008

The company has more than six-million clients worldwide.

Tick-Bank aims to serve as a connection between digital content makers and affiliate dealers, who then promote them to clients.

Tick-Bank's technology aids in payments, tax calculations and a variety of customer service tasks.

Tick-Bank assists in building perceptibility and revenue making opportunities for entrepreneurs. Tick-Bank runs multiple java based web applications running on windows based EC2 machines in AWS managed by internal IT Java team, to serve various business functions.

Tick-Bank is looking to enable web-site traffic analytics there by understanding user navigational behavior, preferences and other click related info.

The amount of data captured per click is in tens of bytes.

Tick-Bank has the following objectives in mind for the solution. Tick-Bank uses KPL to process the data and KCL library to consume the records.

Thousands of events are being generated every second.

To optimize the costs Tick-Bank proposes to group all the user records generated during a specific period and process the data as a stream and want to optimize the costs and processing capability.

Please detail the implementation guidelines.

select 2 options.

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

Tick-Bank is looking to enable website traffic analytics by understanding user navigational behavior, preferences, and other click-related information. They are using KPL to process the data and KCL library to consume the records, generating thousands of events every second.

To optimize costs and processing capability, Tick-Bank proposes to group all the user records generated during a specific period and process the data as a stream. The amount of data captured per click is in tens of bytes.

Given this context, the two implementation guidelines for Tick-Bank are:

  1. Batching is implemented as the target implementation.

Batching is the process of grouping multiple records into a single payload before sending them to the Kinesis Data Stream. This approach is more cost-effective and efficient as it reduces the number of API calls to the Kinesis service, which helps reduce overall costs.

In this case, Tick-Bank can group user records generated during a specific time period, such as a few seconds or minutes, and then send them to the Kinesis Data Stream in a single HTTP request. By doing so, Tick-Bank can reduce the number of HTTP requests made to the Kinesis service, thereby optimizing costs and processing capabilities.

  1. Each HTTP request carries multiple Kinesis Stream records, which are sent to Kinesis Data Streams.

In this implementation guideline, Tick-Bank sends multiple Kinesis Stream records in a single HTTP request to the Kinesis Data Stream. This approach is more efficient than sending each record in a separate Kinesis Data Streams record, as it reduces the number of HTTP requests made to the Kinesis service.

To implement this guideline, Tick-Bank can group multiple user records generated during a specific time period, such as a few seconds or minutes, and then send them to the Kinesis Data Stream in a single HTTP request.

In summary, the implementation guidelines for Tick-Bank are to implement batching and send multiple Kinesis Stream records in a single HTTP request to optimize costs and processing capabilities.