[Geoserver-devel] Splitting the atom... (or just the GeoServer WAR)

Hi all,

Due to the physical architecture in which I need to deploy GeoServer, I was wondering if anyone had experience of splitting GeoServer across servers.

As an example, I would deploy the Internet aware parts (say the WFS and WMF services) on one server, and the data aware services (i.e. connect to Oracle) on another.

If anyone has any info, I’d b grateful!

Thanks,

Dave Ankers
ESG Architecture
Information Systems
Land Registry
Seaton Court, Plymouth
x: 64635
t: 0300 0064635
e: dave.ankers@anonymised.comy.gsi.gov.uk

Land Registry’s House Price Index is now live. www.landregistry.gov.uk

If you have received this e-mail and it was not intended for you, please let us know, and then delete it. Please treat our communications in confidence, as you would expect us to treat yours. Land Registry checks all mail and attachments for known viruses, however, you are advised that you open any attachments at your own risk.

The original of this email was scanned for viruses by the Government Secure Intranet virus scanning service supplied by Cable&Wireless Worldwide in partnership with MessageLabs. (CCTM Certificate Number 2009/09/0052.) On leaving the GSi this email was certified virus free.
Communications via the GSi may be automatically logged, monitored and/or recorded for legal purposes.

Interesting question; usually people split geoserver into separate machines in order to load balance. A lot of time has spent getting GeoServer close physically to the data in order to be efficient; there is no distribution between the data reading library and the GeoServer code using it to handle web feature server request. Literally as each feature is read out of the database the xml is being generated.

If you had to (say for a security setup?) is set up cascading wms in order to have a front end geoserver talk to a backend geoserver that actually draws the pictures.


Jody Garnett

On Tuesday, 15 February 2011 at 10:00 PM, Ankers, David wrote:

Hi all,

Due to the physical architecture in which I need to deploy GeoServer, I was wondering if anyone had experience of splitting GeoServer across servers.

As an example, I would deploy the Internet aware parts (say the WFS and WMF services) on one server, and the data aware services (i.e. connect to Oracle) on another.

If anyone has any info, I’d b grateful!

Thanks,

Dave Ankers
ESG Architecture
Information Systems
Land Registry
Seaton Court, Plymouth
x: 64635
t: 0300 0064635
e: dave.ankers@anonymised.comy.gsi.gov.uk

Land Registry’s House Price Index is now live. www.landregistry.gov.uk

If you have received this e-mail and it was not intended for you, please let us know, and then delete it. Please treat our communications in confidence, as you would expect us to treat yours. Land Registry checks all mail and attachments for known viruses, however, you are advised that you open any attachments at your own risk.

The original of this email was scanned for viruses by the Government Secure Intranet virus scanning service supplied by Cable&Wireless Worldwide in partnership with MessageLabs. (CCTM Certificate Number 2009/09/0052.) On leaving the GSi this email was certified virus free.
Communications via the GSi may be automatically logged, monitored and/or recorded for legal purposes.


The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb


Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

On Tue, Feb 15, 2011 at 1:00 PM, Ankers, David
<Dave.Ankers@anonymised.com> wrote:

Hi all,

Due to the physical architecture in which I need to deploy GeoServer, I was
wondering if anyone had experience of splitting GeoServer across servers.

As an example, I would deploy the Internet aware parts (say the WFS and WMF
services) on one server, and the data aware services (i.e. connect to
Oracle) on another.

There are inefficient ways to do it (wfs-cascading for example) and there
could be more efficient ways to do it that still need to be created.
It would be interesting to know why you'd got for such an architecture
though, normally people create clusters in order to get higher performance
and availability, this kind of split instead may increase the points of
failure and certainly reduce efficiency

Cheers
Andrea

--
-------------------------------------------------------
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead

Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy

phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 333 8128928

http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf

-------------------------------------------------------

Hi Jody & Andrea,

Thanks to both of you for taking the time to reply. Much appreciated J

I fully understand the reasoning behind GeoServer’s application architecture – very sensible and obviously very efficient.

Our logical architecture is designed to split channel functionality (such as B2B and B2C interfaces) from business logic and data access. Due to our (some would argue overly) complex physical network architecture (with outer and inner DMZ), components cannot communicate with each other if they are not in the correct part of the network. My original idea (and the reason behind the question) was the hope that the services offered by GeoServer, such as WFS and WMS, could be offered on the outer layer (channel) and the data access and customisation could be offered on the inner layer (business logic and data).

Obviously this was more pie-in-the-sky than actual design, but it was worth a shot :wink:

We now have a way around this… but thanks again for taking the time to reply.

I’m sure I’ll have more questions in the future :wink:

Thanks,

Dave Ankers
ESG Architecture, Information Systems
Land Registry, Seaton Court, Plymouth, PL6 5WS, UK
x: 64635
t: 0300 0064635
e: dave.ankers@…2665…

From: Jody Garnett [mailto:jody.garnett@…403…]
Sent: 15 February 2011 12:35
To: Ankers, David
Cc: geoserver-devel@lists.sourceforge.net
Subject: Re: [Geoserver-devel] Splitting the atom… (or just the GeoServer WAR)

Interesting question; usually people split geoserver into separate machines in order to load balance. A lot of time has spent getting GeoServer close physically to the data in order to be efficient; there is no distribution between the data reading library and the GeoServer code using it to handle web feature server request. Literally as each feature is read out of the database the xml is being generated.

If you had to (say for a security setup?) is set up cascading wms in order to have a front end geoserver talk to a backend geoserver that actually draws the pictures.


Jody Garnett

There are inefficient ways to do it (wfs-cascading for example) and there could be more efficient ways to do it that still need to be created.

It would be interesting to know why you’d got for such an architecture though, normally people create clusters in order to get higher performance and availability, this kind of split instead may increase the points of failure and certainly reduce efficiency

Cheers

Andrea

Land Registry’s House Price Index is now live. www.landregistry.gov.uk

If you have received this e-mail and it was not intended for you, please let us know, and then delete it. Please treat our communications in confidence, as you would expect us to treat yours. Land Registry checks all mail and attachments for known viruses, however, you are advised that you open any attachments at your own risk.

The original of this email was scanned for viruses by the Government Secure Intranet virus scanning service supplied by Cable&Wireless Worldwide in partnership with MessageLabs. (CCTM Certificate Number 2009/09/0052.) On leaving the GSi this email was certified virus free.
Communications via the GSi may be automatically logged, monitored and/or recorded for legal purposes.