Separate binaries for thin clients and drivers

[dmagda]

Igniters,

Presently, all our thin clients and SQL drivers are stored in the main
Ignite repository. That's totally fine, I wouldn't change anything in here.

But, what I would encourage us to contemplate on is how a user gets and
downloads those binaries. Basically, the user has to download the whole
Ignite distribution even if he needs just a JDBC driver or Node.JS thin
driver.

The proposal is pretty simple. In addition to the main distribution, let's
prepare separate ZIP archives with binaries for:

   - JDBC
   - ODBC
   - Thin clients (Java, C#, Node.JS, Python, etc.)

The binaries would be available for downloads on the main page:
https://ignite.apache.org/download.cgi

Thoughts? Supporters and opposers, please speak out.

--
Denis

[dsetrakyan]

+1

On Fri, Jun 15, 2018 at 12:29 PM, Denis Magda <[hidden email]> wrote:

> Igniters,
>
> Presently, all our thin clients and SQL drivers are stored in the main
> Ignite repository. That's totally fine, I wouldn't change anything in here.
>
> But, what I would encourage us to contemplate on is how a user gets and
> downloads those binaries. Basically, the user has to download the whole
> Ignite distribution even if he needs just a JDBC driver or Node.JS thin
> driver.
>
> The proposal is pretty simple. In addition to the main distribution, let's
> prepare separate ZIP archives with binaries for:
>
>    - JDBC
>    - ODBC
>    - Thin clients (Java, C#, Node.JS, Python, etc.)
>
> The binaries would be available for downloads on the main page:
> https://ignite.apache.org/download.cgi
>
> Thoughts? Supporters and opposers, please speak out.
>
> --
> Denis
>

[Pavel Petroshenko]

Hi Denis,

There are no "binaries" for Node.js and Python that you can download. These
Thin Clients are distributed and installed by a package management system
(npm, pip): which resolves all the dependencies and deploys necessary
components to the appropriate system locations. So instead of downloading a
Node or Python package binary, the package management systems should be
used to properly install it:

Node.js: $ npm install <...>
or
Python: $ pip install <...>

So the proposal is not really applicable to these clients.

Pavel



On Sat, Jun 16, 2018 at 12:45 AM, Dmitriy Setrakyan <[hidden email]>
wrote:

> +1
>
> On Fri, Jun 15, 2018 at 12:29 PM, Denis Magda <[hidden email]> wrote:
>
> > Igniters,
> >
> > Presently, all our thin clients and SQL drivers are stored in the main
> > Ignite repository. That's totally fine, I wouldn't change anything in
> here.
> >
> > But, what I would encourage us to contemplate on is how a user gets and
> > downloads those binaries. Basically, the user has to download the whole
> > Ignite distribution even if he needs just a JDBC driver or Node.JS thin
> > driver.
> >
> > The proposal is pretty simple. In addition to the main distribution,
> let's
> > prepare separate ZIP archives with binaries for:
> >
> >    - JDBC
> >    - ODBC
> >    - Thin clients (Java, C#, Node.JS, Python, etc.)
> >
> > The binaries would be available for downloads on the main page:
> > https://ignite.apache.org/download.cgi
> >
> > Thoughts? Supporters and opposers, please speak out.
> >
> > --
> > Denis
> >
>

[dsetrakyan]

Pavel, this makes sense. In a way, these clients already have a separate
binary installation.

D.

On Sat, Jun 16, 2018, 11:10 Pavel Petroshenko <[hidden email]> wrote:

> Hi Denis,
>
> There are no "binaries" for Node.js and Python that you can download. These
> Thin Clients are distributed and installed by a package management system
> (npm, pip): which resolves all the dependencies and deploys necessary
> components to the appropriate system locations. So instead of downloading a
> Node or Python package binary, the package management systems should be
> used to properly install it:
>
> Node.js: $ npm install <...>
> or
> Python: $ pip install <...>
>
> So the proposal is not really applicable to these clients.
>
> Pavel
>
>
>
> On Sat, Jun 16, 2018 at 12:45 AM, Dmitriy Setrakyan <[hidden email]
> >
> wrote:
>
> > +1
> >
> > On Fri, Jun 15, 2018 at 12:29 PM, Denis Magda <[hidden email]> wrote:
> >
> > > Igniters,
> > >
> > > Presently, all our thin clients and SQL drivers are stored in the main
> > > Ignite repository. That's totally fine, I wouldn't change anything in
> > here.
> > >
> > > But, what I would encourage us to contemplate on is how a user gets and
> > > downloads those binaries. Basically, the user has to download the whole
> > > Ignite distribution even if he needs just a JDBC driver or Node.JS thin
> > > driver.
> > >
> > > The proposal is pretty simple. In addition to the main distribution,
> > let's
> > > prepare separate ZIP archives with binaries for:
> > >
> > >    - JDBC
> > >    - ODBC
> > >    - Thin clients (Java, C#, Node.JS, Python, etc.)
> > >
> > > The binaries would be available for downloads on the main page:
> > > https://ignite.apache.org/download.cgi
> > >
> > > Thoughts? Supporters and opposers, please speak out.
> > >
> > > --
> > > Denis
> > >
> >
>

[Aleksandr Sokolovskii]

Hi All,

The same situation is for Go lang also.
There are no binaries.
Libraries are installed from source code repo, etc.:

go get -u github.com/amsokol/ignite-go-client

So the proposal is not really applicable to Go lang client.

Thanks,
Aleksandr

From: Pavel Petroshenko
Sent: 16 июня 2018 г. 21:10
To: Denis Magda
Cc: dev
Subject: Re: Separate binaries for thin clients and drivers

Hi Denis,

There are no "binaries" for Node.js and Python that you can download. These
Thin Clients are distributed and installed by a package management system
(npm, pip): which resolves all the dependencies and deploys necessary
components to the appropriate system locations. So instead of downloading a
Node or Python package binary, the package management systems should be
used to properly install it:

Node.js: $ npm install <...>
or
Python: $ pip install <...>

So the proposal is not really applicable to these clients.

Pavel



On Sat, Jun 16, 2018 at 12:45 AM, Dmitriy Setrakyan <[hidden email]>
wrote:

> +1
>
> On Fri, Jun 15, 2018 at 12:29 PM, Denis Magda <[hidden email]> wrote:
>
> > Igniters,
> >
> > Presently, all our thin clients and SQL drivers are stored in the main
> > Ignite repository. That's totally fine, I wouldn't change anything in
> here.
> >
> > But, what I would encourage us to contemplate on is how a user gets and
> > downloads those binaries. Basically, the user has to download the whole
> > Ignite distribution even if he needs just a JDBC driver or Node.JS thin
> > driver.
> >
> > The proposal is pretty simple. In addition to the main distribution,
> let's
> > prepare separate ZIP archives with binaries for:
> >
> >    - JDBC
> >    - ODBC
> >    - Thin clients (Java, C#, Node.JS, Python, etc.)
> >
> > The binaries would be available for downloads on the main page:
> > https://ignite.apache.org/download.cgi
> >
> > Thoughts? Supporters and opposers, please speak out.
> >
> > --
> > Denis
> >
>

[Pavel Tupitsyn]

Same thing with package manager for .NET (NuGet).
And same with Java, actually (Maven).

In my understanding, most people use package managers and don't download
ZIP archives.
Package managers are more convenient and easy to use. It is a modern way.


On Sun, Jun 17, 2018 at 11:28 AM, Aleksandr Sokolovskii <[hidden email]>
wrote:

> Hi All,
>
> The same situation is for Go lang also.
> There are no binaries.
> Libraries are installed from source code repo, etc.:
>
> go get -u github.com/amsokol/ignite-go-client
>
> So the proposal is not really applicable to Go lang client.
>
> Thanks,
> Aleksandr
>
> From: Pavel Petroshenko
> Sent: 16 июня 2018 г. 21:10
> To: Denis Magda
> Cc: dev
> Subject: Re: Separate binaries for thin clients and drivers
>
> Hi Denis,
>
> There are no "binaries" for Node.js and Python that you can download. These
> Thin Clients are distributed and installed by a package management system
> (npm, pip): which resolves all the dependencies and deploys necessary
> components to the appropriate system locations. So instead of downloading a
> Node or Python package binary, the package management systems should be
> used to properly install it:
>
> Node.js: $ npm install <...>
> or
> Python: $ pip install <...>
>
> So the proposal is not really applicable to these clients.
>
> Pavel
>
>
>
> On Sat, Jun 16, 2018 at 12:45 AM, Dmitriy Setrakyan <[hidden email]
> >
> wrote:
>
> > +1
> >
> > On Fri, Jun 15, 2018 at 12:29 PM, Denis Magda <[hidden email]> wrote:
> >
> > > Igniters,
> > >
> > > Presently, all our thin clients and SQL drivers are stored in the main
> > > Ignite repository. That's totally fine, I wouldn't change anything in
> > here.
> > >
> > > But, what I would encourage us to contemplate on is how a user gets and
> > > downloads those binaries. Basically, the user has to download the whole
> > > Ignite distribution even if he needs just a JDBC driver or Node.JS thin
> > > driver.
> > >
> > > The proposal is pretty simple. In addition to the main distribution,
> > let's
> > > prepare separate ZIP archives with binaries for:
> > >
> > >    - JDBC
> > >    - ODBC
> > >    - Thin clients (Java, C#, Node.JS, Python, etc.)
> > >
> > > The binaries would be available for downloads on the main page:
> > > https://ignite.apache.org/download.cgi
> > >
> > > Thoughts? Supporters and opposers, please speak out.
> > >
> > > --
> > > Denis
> > >
> >
>
>

[Igor Sapego-2]

So, it seems, like it only has sense for ODBC Windows binaries.
For Linux there are also packages that should also be used.
Best Regards,
Igor


On Mon, Jun 18, 2018 at 10:04 AM Pavel Tupitsyn <[hidden email]>
wrote:

> Same thing with package manager for .NET (NuGet).
> And same with Java, actually (Maven).
>
> In my understanding, most people use package managers and don't download
> ZIP archives.
> Package managers are more convenient and easy to use. It is a modern way.
>
>
> On Sun, Jun 17, 2018 at 11:28 AM, Aleksandr Sokolovskii <[hidden email]
> >
> wrote:
>
> > Hi All,
> >
> > The same situation is for Go lang also.
> > There are no binaries.
> > Libraries are installed from source code repo, etc.:
> >
> > go get -u github.com/amsokol/ignite-go-client
> >
> > So the proposal is not really applicable to Go lang client.
> >
> > Thanks,
> > Aleksandr
> >
> > From: Pavel Petroshenko
> > Sent: 16 июня 2018 г. 21:10
> > To: Denis Magda
> > Cc: dev
> > Subject: Re: Separate binaries for thin clients and drivers
> >
> > Hi Denis,
> >
> > There are no "binaries" for Node.js and Python that you can download.
> These
> > Thin Clients are distributed and installed by a package management system
> > (npm, pip): which resolves all the dependencies and deploys necessary
> > components to the appropriate system locations. So instead of
> downloading a
> > Node or Python package binary, the package management systems should be
> > used to properly install it:
> >
> > Node.js: $ npm install <...>
> > or
> > Python: $ pip install <...>
> >
> > So the proposal is not really applicable to these clients.
> >
> > Pavel
> >
> >
> >
> > On Sat, Jun 16, 2018 at 12:45 AM, Dmitriy Setrakyan <
> [hidden email]
> > >
> > wrote:
> >
> > > +1
> > >
> > > On Fri, Jun 15, 2018 at 12:29 PM, Denis Magda <[hidden email]>
> wrote:
> > >
> > > > Igniters,
> > > >
> > > > Presently, all our thin clients and SQL drivers are stored in the
> main
> > > > Ignite repository. That's totally fine, I wouldn't change anything in
> > > here.
> > > >
> > > > But, what I would encourage us to contemplate on is how a user gets
> and
> > > > downloads those binaries. Basically, the user has to download the
> whole
> > > > Ignite distribution even if he needs just a JDBC driver or Node.JS
> thin
> > > > driver.
> > > >
> > > > The proposal is pretty simple. In addition to the main distribution,
> > > let's
> > > > prepare separate ZIP archives with binaries for:
> > > >
> > > >    - JDBC
> > > >    - ODBC
> > > >    - Thin clients (Java, C#, Node.JS, Python, etc.)
> > > >
> > > > The binaries would be available for downloads on the main page:
> > > > https://ignite.apache.org/download.cgi
> > > >
> > > > Thoughts? Supporters and opposers, please speak out.
> > > >
> > > > --
> > > > Denis
> > > >
> > >
> >
> >
>

[dmagda]

Guys,

Have a look at Hazelcast. They provide both approaches - installation with
a package management system + binary (or zip archives downloads):
https://hazelcast.org/clients-languages/

It will be great to provide Ignite community with the same usability.

--
Denis

On Mon, Jun 18, 2018 at 12:20 AM Igor Sapego <[hidden email]> wrote:

> So, it seems, like it only has sense for ODBC Windows binaries.
> For Linux there are also packages that should also be used.
> Best Regards,
> Igor
>
>
> On Mon, Jun 18, 2018 at 10:04 AM Pavel Tupitsyn <[hidden email]>
> wrote:
>
> > Same thing with package manager for .NET (NuGet).
> > And same with Java, actually (Maven).
> >
> > In my understanding, most people use package managers and don't download
> > ZIP archives.
> > Package managers are more convenient and easy to use. It is a modern way.
> >
> >
> > On Sun, Jun 17, 2018 at 11:28 AM, Aleksandr Sokolovskii <
> [hidden email]
> > >
> > wrote:
> >
> > > Hi All,
> > >
> > > The same situation is for Go lang also.
> > > There are no binaries.
> > > Libraries are installed from source code repo, etc.:
> > >
> > > go get -u github.com/amsokol/ignite-go-client
> > >
> > > So the proposal is not really applicable to Go lang client.
> > >
> > > Thanks,
> > > Aleksandr
> > >
> > > From: Pavel Petroshenko
> > > Sent: 16 июня 2018 г. 21:10
> > > To: Denis Magda
> > > Cc: dev
> > > Subject: Re: Separate binaries for thin clients and drivers
> > >
> > > Hi Denis,
> > >
> > > There are no "binaries" for Node.js and Python that you can download.
> > These
> > > Thin Clients are distributed and installed by a package management
> system
> > > (npm, pip): which resolves all the dependencies and deploys necessary
> > > components to the appropriate system locations. So instead of
> > downloading a
> > > Node or Python package binary, the package management systems should be
> > > used to properly install it:
> > >
> > > Node.js: $ npm install <...>
> > > or
> > > Python: $ pip install <...>
> > >
> > > So the proposal is not really applicable to these clients.
> > >
> > > Pavel
> > >
> > >
> > >
> > > On Sat, Jun 16, 2018 at 12:45 AM, Dmitriy Setrakyan <
> > [hidden email]
> > > >
> > > wrote:
> > >
> > > > +1
> > > >
> > > > On Fri, Jun 15, 2018 at 12:29 PM, Denis Magda <[hidden email]>
> > wrote:
> > > >
> > > > > Igniters,
> > > > >
> > > > > Presently, all our thin clients and SQL drivers are stored in the
> > main
> > > > > Ignite repository. That's totally fine, I wouldn't change anything
> in
> > > > here.
> > > > >
> > > > > But, what I would encourage us to contemplate on is how a user gets
> > and
> > > > > downloads those binaries. Basically, the user has to download the
> > whole
> > > > > Ignite distribution even if he needs just a JDBC driver or Node.JS
> > thin
> > > > > driver.
> > > > >
> > > > > The proposal is pretty simple. In addition to the main
> distribution,
> > > > let's
> > > > > prepare separate ZIP archives with binaries for:
> > > > >
> > > > >    - JDBC
> > > > >    - ODBC
> > > > >    - Thin clients (Java, C#, Node.JS, Python, etc.)
> > > > >
> > > > > The binaries would be available for downloads on the main page:
> > > > > https://ignite.apache.org/download.cgi
> > > > >
> > > > > Thoughts? Supporters and opposers, please speak out.
> > > > >
> > > > > --
> > > > > Denis
> > > > >
> > > >
> > >
> > >
> >
>

[dsetrakyan]

On Mon, Jun 18, 2018 at 9:45 AM, Denis Magda <[hidden email]> wrote:

> Guys,
>
> Have a look at Hazelcast. They provide both approaches - installation with
> a package management system + binary (or zip archives downloads):
> https://hazelcast.org/clients-languages/
>
> It will be great to provide Ignite community with the same usability.
>

Agree with Denis. For example, Maven for Java is not an installation, is a
project-dependency import. We need a separate ZIP file for Java client
which will include the license information, examples, documentation, and
any additional dependencies if needed. I am sure the same approach will
have to be put in place for many other clients.