LISAsoft Geoserver Module 1 Training Melbourne Tuesday August 18th 2015

LISAsoft is pleased to announce that we’ve organised our Geospatial training calendar through to September 2015.

The first course out of the starting gate, to which we’d like to extend you a personal invitation, is Geoserver Module 1 being held in Melbourne for the dates Tuesday August 18th through to Wednesday August 19th.

Course Synopsis:

Course Name: Geoserver Module 1
Course Location: Melbourne, VIC
Course Duration: 2 Days
Course Date: Tuesday 18 – Wednesday 19th August, 2015
Course Value (exc. GST): $2,450
Course Code: GSPRO01

For a full description of the Geoserver Module 1 Program click through here: Geoserver Module 1

To view the complete LISAsoft Training Schedule through to September 2015 click through here: LISAsoft Training Schedule

All your LISAsoft Training FAQ’s should be answered if you click through here: LISAsoft Training FAQ’s

We hope you can make it along to the course.

Call Jack or Cameron at LISAsoft on 02 9009 5000 if there is anything further about the training you’d like to discuss.

Hadoop To Postgres – Bridging The Gap

Story Source and Credit: Ahsan Hadi & Ibrar Ahmed, Feb 20, 2015

Advances in Postgres in recent releases have opened up opportunities for expanding features that support data integration. The most compelling of these new features are called Foreign Data Wrappers (FDWs). FDWs essentially act as a pipeline for data to move to and from Postgres and other kinds of databases as if the different solutions were a single database. EnterpriseDB has developed new FDWs for MongoDB and MySQL. Now, we have released one for Hadoop.

The FDW for Hadoop can be found on EDB’s GitHub page.

Foreign Data Wrappers enable Postgres to act as the central hub, a federated database, in the enterprise. And the features have emerged at a good time as integration becomes more of a challenge. Database administrators (DBAs) have begun using more and more specialized NoSQL-only solutions to address specific problems. Now DBAs need to address getting the data in all of these different solutions to tell one single story, or lend value to one another.

Since EDB released the new FDWs with both read and write capability to the open source PostgreSQL community, usage has grown tremendously. More and more developers are contributing features and fixes.

Now that we’ve established some context for the FDWs, let’s explore the Hadoop FDW in more detail. There are few popular terms worth exploring first:

Hadoop Distributed File System (HDFS): HDFS is a distributed file system for large data storage and processing. It’s java-based and provides scalable and reliable storage that is designed to span large clusters of commodity servers. The data is stored in flat files and format-free. As a result, it’s used for very large data sets and a typical HDFS file is a GB to TB in size. Applications that run HDFS require streaming access to their data sets.

MapReduce: MapReduce is a programming model and associated implementation for processing and generating large data sets. The model was inspired by the map and reduce functions commonly used in functional programming. MapReduce jobs are written in java and are used for performing statistical analysis, aggregates or other complex processing on large data sets stored in HDFS.

Hive Server: The Apache Hive is data warehouse software that facilitates querying and managing large datasets residing in distributed storage i.e. an HDFS. Hive defines a simple query-like language called QL which is used for querying and manipulating large data sets stored in an HDFS. The QL language is similar to SQL and provides similar constructs for retrieving data. Hive server is an optional service that allows remote clients to send requests to HIVE using various programming languages and retrieve results.

Foreign Data Wrapper (FDW): While we have introduced FDWs already, it’s good to know they are based on Postgres implementation of the SQL/MED (SQL management of external data) specification of the SQL standard. It is a standard way of accessing external data stores ranging from SQL and NoSQL-only databases to flat files. FDWs provide a SQL interface for accessing remote objects and large data objects stored in remote data stores. The FDWs supported by EnterpriseDB are postgres_fdw, oracle_fdw, mongo_fdw, mysql_fdw and now we’re adding HDFS_fdw to the list.

Full Story, Installation Instructions and Code Examples Here…….

EnterpriseDB Features Enterprise Postgres Migrations at Gartner Summit

Story Credit and Source: EnterpriseDB April 1st 2015

EnterpriseDB (EDB), a leading worldwide provider of enterprise-class Postgres products and database compatibility solutions, is showcasing the enterprise-class performance of Postgres during the Gartner Enterprise Information & Master Data Management Summit today and tomorrow in Las Vegas.

EDB and its customer Clear Capital will present a case study during the event that illustrates the ease and benefits of migrating from a costly, traditional database to EDB’s Postgres Plus Advanced Server.

Brands globally have discovered Postgres provides the performance and security required to support mission-critical workloads at a fraction of the cost of traditional databases. With an open source based model that reduces costs, Postgres Plus solutions from EDB enable IT to redirect budget to support new data-driven initiatives. Clear Capital is a data-driven enterprise, providing residential and commercial real estate valuations, data and analytics, quality assurance services and technology solutions.

“EDB has become an industry leader by providing a database, tools and compatibility with Oracle that support most of the applications global enterprises typically run,” said Marc Linster, Senior Vice President of Products and Services at EnterpriseDB.

“We believe our recent positioning in the Leaders Quadrant of the Gartner Magic Quadrant for Operational Database Management Systems* is a reflection of that. The fact we cut database costs has made us popular with innovative departments looking to redirect budget to more strategic, forward-thinking projects.”

Open Source: The New Data Center Standard

Story Source and Credit: The Gartner Files

Open-source Relational Database Management Systems have matured significantly and can be used to replace commercial RDBMSs at a considerable Total Cost of Ownership saving. Information leaders, Database Administrators and application development management can now consider them as a standard choice for deploying applications.

Strategic Planning Assumption
By 2018, more than 70% of new in-house applications will be developed on an OSDBMS, and 50% of existing commercial RDBMS instances will have been converted or will be in process.

Impacts

  • Open-source relational DBMSs (RDBMSs) have matured and today can be considered by information leaders, DBAs and application development management as a standard infrastructure choice for a large majority of new enterprise applications.
  • An increasing proportion of third-party and in-house applications can be used on open-source RDBMSs, meaning DBAs and application development management can now use them to replace existing internal commercial RDBMSs.
  • Information leaders who opt for an open-source DBMS (OSDBMS) licensing model can benefit from much lower costs than using a commercial model, even with today’s hosted cloud and database platform as a service (dbPaaS) offerings.

Recommendations

  • Add an open-source RDBMS to your organization’s RDBMS standards for new uses, and to replace a commercial RDBMS where it and specific functionality are not required.
  • Evaluate the use of an open-source RDBMS, when offered by a third-party application vendor, as the implementation platform of choice for existing deployments.
  • Look for subscription-based pricing models, even if not open source — most offer the same cost model and lower total cost of ownership (TCO).

Get The Report Here …….

Open Source Threatens To Eat The Database Market

Story Source And Credit: Matt Assay, Infoworld Tech Watch

The database market has largely been impervious to open source pricing pressure. That may be about to change.

Marten Mickos may no longer run MySQL, but his ghost still haunts the database market.

Years ago, Mickos declared, “The relational database market is a $9 billion a year market. I want to shrink it to $3 billion and take a third of the market.” MySQL never got to that point, generating roughly $100 million in sales before being acquired by Sun for $1 billion, but that commoditization urge has hit the database market hard.

How hard? Today’s open source databases comprise a fraction of the paid database market, yet now constitute as much as a quarter of all database usage. The database market, in short, is ripe for open source cannibalization.

A Big Market And Target

The database market is a huge and growing market. According to IDC, the overall database market tops $40 billion today and should reach $50 billion by 2017. Most of that market is composed of proprietary databases like Oracle and Microsoft’s SQL Server.

Yet despite what appears to be reasonable growth, all is not well in database land — at least, not if you’re a legacy vendor.

Growing Slower All The Time

As Gartner highlights in a recent research report, open source databases now consume 25 percent of relational database usage.

Why should we care? Because, according to Gartner, “The potential impact of [open source databases] capturing workloads that would otherwise go to commercial products will manifest in declining growth rates for the latter.”

In fact, it’s already happening. Though the proprietary RDBMS market grew at a sluggish 5.4 percent in 2014, the open source database market grew 31 percent to hit $562 million.

Think about that: $562 million in revenue but 25 percent overall database usage in a market worth more than $40 billion. What will happen to that $40 billion when open source databases claim 50 percent market share in terms of database use?

Physician, Eat Thyself

The database vendors need an answer — soon. A quick look at DB-Engines, which ranks database popularity, suggests that this trend toward open source will only continue.

With very few exceptions, open source databases — both relational and NoSQL — are chewing into proprietary database popularity.

This isn’t a development a vendor can combat through ever-tightening account control, not given the rising importance of developers. As Gartner highlights, “Developer choice, an increasingly important determinant of product usage, often occurs without reference to corporate standard preferences, as usage increasingly falls outside of IT organizations.”

While it used to be the case that picking open source databases was a trade-off of robustness and performance for developer convenience, that’s no longer the case according to Gartner for open source RDBMSes: “Open source … RDBMSes have matured and today can be considered by information leaders, DBAs and application development management as a standard infrastructure choice for a large majority of new enterprise applications.”

Assuming the same happens in the NoSQL market — a very good assumption– the hitherto indomitable proprietary database market looks ripe for open source cannibalization. Mickos had the vision, but today’s open source database leaders will really get to live it.

Full Infoworld Story Here Along With Charts and Reference Links……

GeoNetwork OpenSource v3.0.0 Released

Source and Credit: Francois Prunayre, Project Steering Committee Member

We’re proud to announce the release of GeoNetwork opensource v3.0.0 http://geonetwork-opensource.org/.

This is a major release for the project that provides a brand new user interface with great functionality, helping all those that need to publish their data, services and maps with standardized metadata.

You can find the software here.

You can find a list of new functionality here.

If you have any improvements you want to contribute back, the best is to use git to get a local copy of the source code, apply the fix and put out a Pull request so your improvements can be integrated quickly.

Otherwise you can also create new Tickets in the issue tracker here.

Thanks and congratulations to the all community members and developers that have been putting a huge amount of effort and energy in this release.

Using Postgres To Integrate MongoDB, Hadoop and Others With Foreign Data Wrappers


Event: EnterpriseDB Webinar

Date: Wednesday, April 29, 8:00am EDT

Presented By: Bruce Momjian, Co-Founder of the PostgreSQL Global Development Group and Sr. Database Architect at EnterpriseDB.

Register Here

Attend this special webinar to learn about Foreign Data Wrappers (FDWs) and watch a live demo with Bruce Momjian.

A powerful feature in Postgres called Foreign Data Wrappers lets end users integrate data from MongoDB, Hadoop and other solutions with their Postgres database and leverage it as single, seamless database using SQL.

Use of these features has skyrocketed since EDB released to the open source community new FDWs for MongoDB, Hadoop and MySQL that support both read and write capabilities. Now greatly enhanced, FDWs enable integrating data across disparate deployments to support new workloads, expanded development goals and harvesting greater value from data.

Learn more about Foreign Data Wrappers (FDWs) and watch a live demo with Bruce Momjian, Co-Founder of the PostgreSQL Global Development Group and Sr. Database Architect at EDB.

Target Audience: This presentation is intended for IT Professionals seeking to do more with Postgres in his every day projects and build new applications.

Webcast Author: Bruce Momjian, Cofounder of PostgreSQL Global Development and Sr. Database Architect, EDB

Link to live webcast: http://info.enterprisedb.com/using-postgres-fdw.html

Duration: 1 Hour