Hi Leo Simons wrote: > Hey folks, > > On Mon, Mar 12, 2012 at 11:07 AM, Alexander Dutton > <[email protected]> wrote: >>> JENA-201, even if flagged as minor, I think it's quite important if >>> we want to successfully allow Fuseki to be deployed and used in >>> 'enterprisy' environments. >> Another thing that might be useful for 'enterprisy' environments would >> be Debian and/or RPM packaging, though these probably want to wait until >> after the release. (I've had a look at the Debian side, but I'm no >> expert, and dealing with non-tarball upstreams (as things are at the >> moment) is messy). > > For the record, as someone with some experience with the 'enterpricy' > stuff, I personally wouldn't try to provide .deb/.rpm/.msi for java > webapps, at least not for the enterprise.
Thanks Leo for sharing your expertise and advice. I always follow informed advices which imply no work needed. ;-) > The issue is "where do we actually install stuff". I.e. a big java > shop will have a standard web container setup and will want to > integrate a fuseki deployment into that, and you won't be able to know > the details of that setup. It tends to not be the standard tomcat that > comes with the OS. > > I think you need three things: > * a standard .war that drag-and-drop installs in any servlet container Yep. > * an svn tag corresponding to a versioned release that is readily > buildable using standard tools > * a description of actual real life deployment environments > (hardware+software+config+service dependencies), associated data sets > and achieved performance/uptime, easily findable on your website That would be really be useful, alongside best practices for: - high availability - security - load balancing - monitoring - request throttling - ... Even if you get away with these saying: "it's just a standard web app". Just checking, by "your website" do you mean Apache Jena website? What other Apache projects do that? (sorry for my ignorance). We use TDB, but not Fuseki (when we started Fuseki wasn't there). Some of us, use Fuseki internally. Having said that, things such as performances and/or uptime do not depend only on a specific software, it's a mix of different software, architecture, processes and people. Isn't it? > * links to available commercial support Yep. > The first will be used to evaluate how much work needs to be done to > beat the app into submission, following the standard rules. > > The second will get used to create a vendor branch and then customize > the build to produce a custom-enterprise-style rpm containing a > custom-enterprise-style war to go into a custom-enterprise-style > tomcat. > > The third will be used for capacity planning and to inform load > testing as to whether the achieved performance is reasonable. Since > the people doing those things may be different from the people that > are wanting to use fuseki, and so they won't be familiar with jena or > fuseki, it's pretty important to make it easy enough to find. > > The commercial support may not get used, but it tends to at least be > considered a lower risk to use something if you know you can go and > pay for someone to come in and fix messed up systems a year later. > > All the above *doesn't* mean providing a .deb/.rpm/.msi/.whatever is > useless. But it'll mostly be because its useful for 'normal' end > users, not for the enterpricy folks. > > Heh. I didn't mean to write *all* that :-). Hope it helps, anyway. Thanks. Paolo > > > cheers! > > > Leo
