Interested in discussing the product in detail for a large scale music distribution and data matching project

classic Classic list List threaded Threaded
3 messages Options
Scott Yaworski Scott Yaworski
Reply | Threaded
Open this post in threaded view
|

Interested in discussing the product in detail for a large scale music distribution and data matching project

Hello from Sydney Australia,

 

I’m working on an interesting project where based on what I have seen and read so far Ignite may be an option for us so I’m very interested to quickly understand if this is the case.

 

We have looked at a number of the standard options such as cloud, Hadoop, Spark, etc. Currently the company is using SQL Server and that really isn’t the best option for this type of solution.

 

There are a number of reasons why we are limited to not going Cloud at this point so we are looking at an On Premise solution.

 

Essentially we are ingesting all of the downloaded, streamed, and viewed music content globally from iTunes, YouTube, Spotify, etc.

 

We ingest the data that comes in many different formats and validate it then transform the data. Then we move into the data matching and aggregation process to understand the global number.

 

After that we must understand who owns the rights to the music and this is a many to one relationship so the data starts to explode. Then we have license fee calcs, and finally financial distribution.

 

That is a very simplified view of what we are doing but will help with the understanding. Very fun project and interesting problem to solve. While this is not truly a large amount of data compared to an oil and gas scenario which is what I’m normally dealing there is a lot of data movement currently and repetitive linear processes.

 

I need a way to break up the data and distribute it across nodes in order to match much faster. There is also a fuzzy logic/machine learning piece to the puzzle as well.

 

I just discovered your product yesterday and I’m hoping I can get some deeper information quickly from someone who could possibly have a conversation with me.

 

I would like a deeper understanding of the product and also some understand of what the hardware requirements/impact will be if we head down this path.

 

The company is a not for profit organisation so I’m hoping to minimize cost of them as much as possible while also giving them the ability to scale and more and more people around the world stream and download music.

 

Thanks in advance.

Scott

 

Scott Yaworski

Director – Digital IOT/Big Data Lead 
Avanade Australia Pty Ltd | Perth

Level 3, 5 Mill St Perth, WA
Email: [hidden email]

Mobile: +61 437 464 037 
www.avanade.com/au

 

Description: Description: Description: cid:image001.gif@01C9B8F6.A4BC28B0

 

 

vkulichenko vkulichenko
Reply | Threaded
Open this post in threaded view
|

Re: Interested in discussing the product in detail for a large scale music distribution and data matching project

Hi Scott,

I think you should definitely try Ignite for your use case. It will allow you to have scalable caches to store the data and different ways to read and process the data, like SQL queries and map-reduce. We also have transactional support, streaming capabilities and many other features that can also be useful.

Here is the list of documentation pages I would start with:

https://apacheignite.readme.io/docs/getting-started
https://apacheignite.readme.io/docs/data-grid
https://apacheignite.readme.io/docs/sql-queries
https://apacheignite.readme.io/docs/compute-grid
https://apacheignite.readme.io/docs/streaming--cep

Let us know if you have more questions.

-Val
dsetrakyan dsetrakyan
Reply | Threaded
Open this post in threaded view
|

Re: Interested in discussing the product in detail for a large scale music distribution and data matching project

Hi Scott, 

If you need to chat with someone in the community, then you can also try the Ignite chat room:

D.

On Wed, May 25, 2016 at 3:55 AM, vkulichenko <[hidden email]> wrote:
Hi Scott,

I think you should definitely try Ignite for your use case. It will allow
you to have scalable caches to store the data and different ways to read and
process the data, like SQL queries and map-reduce. We also have
transactional support, streaming capabilities and many other features that
can also be useful.

Here is the list of documentation pages I would start with:

https://apacheignite.readme.io/docs/getting-started
https://apacheignite.readme.io/docs/data-grid
https://apacheignite.readme.io/docs/sql-queries
https://apacheignite.readme.io/docs/compute-grid
https://apacheignite.readme.io/docs/streaming--cep

Let us know if you have more questions.

-Val



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Interested-in-discussing-the-product-in-detail-for-a-large-scale-music-distribution-and-data-matchint-tp5075p5175.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.