Re: Spark and N-tier architecture

Our difference is mostly over whether n-tier means what it meant long ago, or whether it is a malleable concept that can be stretched without breaking to cover newer architectures. As I said before, if n-tier helps you think about Spark, then use it; if it doesn't, don't force it. On Tue, Mar

Re: Spark and N-tier architecture

ng. I am currently > evaluating it right now. > > > On Mar 29, 2016, at 16:17, Michael Segel <msegel_had...@hotmail.com> > wrote: > > > > Begin forwarded message: > > *From: *Michael Segel <mse...@segel.com> > *Subject: **Re: Spark and N-tier architecture* >

Re: Spark and N-tier architecture

n-tiers or layers is mainly for separate a big problem into pieces smaller problem. So it is always valid. Just for different application, it means different things. Speaking of offline analytics, or big data eco-world, there are numerous way of slicing the problem into different tier/layer.

Re: Spark and N-tier architecture

Spark-jobserver was originally created by Ooyala Now it's Open Source Apache Licensed project ​

Re: Spark and N-tier architecture

It is a separate project based on my understanding. I am currently evaluating it right now. > On Mar 29, 2016, at 16:17, Michael Segel <msegel_had...@hotmail.com> wrote: > > > >> Begin forwarded message: >> >> From: Michael Segel <mse...@sege

Re: Spark and N-tier architecture

Hi Mark, I beg I agree to differ on the interpretation of N-tier architecture. Agreed that 3-tier and by extrapolation N-tier have been around since days of client-server architecture. However, they are as valid today as 20 years ago. I believe the main recent expansion of n-tier has been on

Re: Spark and N-tier architecture

Yes and no. The idea of n-tier architecture is about 20 years older than Spark and doesn't really apply to Spark as n-tier was original conceived. If the n-tier model helps you make sense of some things related to Spark, then use it; but don't get hung up on trying to force a Spark architecture

Fwd: Spark and N-tier architecture

> Begin forwarded message: > > From: Michael Segel <mse...@segel.com> > Subject: Re: Spark and N-tier architecture > Date: March 29, 2016 at 4:16:44 PM MST > To: Alexander Pivovarov <apivova...@gmail.com> > Cc: Mich Talebzadeh <mich.talebza...@gmail.com>

Re: Spark and N-tier architecture

Thank you both. So am I correct that Spark fits in within the application tier in N-tier architecture? On Tuesday, 29 March 2016, 23:50, Alexander Pivovarov wrote: Spark is a distributed data processing engine plus distributed in-memory / disk data cache 

Re: Spark and N-tier architecture

Spark is a distributed data processing engine plus distributed in-memory / disk data cache spark-jobserver provides REST API to your spark applications. It allows you to submit jobs to spark and get results in sync or async mode It also can create long running Spark context to cache RDDs in

Re: Spark and N-tier architecture

Interesting question. The most widely used application of N-tier is the traditional three-tier architecture that has been the backbone of Client-server architecture by having presentation layer, application layer and data layer. This is primarily for performance, scalability and maintenance. The

Spark and N-tier architecture

Experts, One of terms used and I hear is N-tier architecture within Big Data used for availability, performance etc. I also hear that Spark by means of its query engine and in-memory caching fits into middle tier (application layer) with HDFS and Hive may be providing the data tier.  Can