Manifold® Internet Map Server Top 10 Advantages
See the Manifold Internet Map Server (IMS) page for an introduction to Manifold IMS. This page discusses the top ten advantages experienced users have reported for using Manifold IMS over old-fashioned IMS.
There are many good reasons to use Manifold IMS instead of a legacy system such as ArcIMS. Manifold IMS provides much more power and functionality while being easier to use, easier to deploy and easier to maintain, all while being over 40 times less expensive. Users report that these Manifold advantages hold against both ArcIMS and newer ESRI products such as ArcGIS Server. This page describes key advantages of Manifold IMS over older systems. We use ESRI products as a typical example of legacy systems.
Discussion: In addition to the better performance and more sophisticated capabilities made possible by the more modern software technology used within Manifold IMS, the fundamental difference in approach also delivers a lot of benefits. The old-fashioned way to do GIS uses separate packages for various core functions. In the ESRI product line, someone might use ArcInfo to edit their data and prepare it for functioning, ArcObjects to write programs interacting with that data, ArcSDE to connect to spatial databases and finally ArcIMS to GIS-enable a web site. [This page uses ESRI names most users know. ESRI has recently given new names to more or less the same old products.]
The ESRI approach requires spending money on multiple different programs and, worse yet, becoming expert in different packages that, typically, were written at different times by different teams and implemented using different interfaces. No wonder ArcIMS sites are legendarily difficult to get running, and that implementors will often end up feeling so bruised by the process that they are afraid of changing anything for fear the web site will stop functioning.
In contrast, Manifold takes the more modern approach of using a single, integrated package. Once you go to the effort of writing and re-writing the millions of lines of code required for a modern, enterprise-class GIS engine it's not much more effort to equip that same engine with web-server interfaces as well as desktop console and keyboard interfaces. Manifold made that extra effort so that identically the same engine can function whether it is accessed in a web server scenario or through an interactive user console. That has a lot of benefits:
- First, only one package need be purchased, installed, learned, configured and maintained. This has obvious savings in initial and recurrent cost, as well as great savings in training and labor.
- Second, because the same package is used throughout the process, from whipping data into shape to formatting and other configuration and then finally for publishing, you get the benefit of WYSIWYG ("What You See Is What You Get") workflow: what is published in IMS looks exactly like what was created on the desktop because it is identically the same engine rendering the data. This carries through all phases of the process: because the object model is the same, any programmatic parts of the site will work identically the same way. Because all features, such as spatial SQL are the same, these also will work identically the same way. This has enormous savings in time and labor.
- Third, because the same package publishes the data as is used to prepare it, the package can provide automated means to eliminate programming. The simplest way to create an IMS web site in Manifold is to launch Manifold as an ordinary desktop application, cobble up a project as you see fit until it looks the way you like and then choose File - Export - Web Page. Check off the options desired and Manifold will write your web page for you with zero programming required. Although experts will, of course, often desire to make their own customizations it is great for confidence building and debugging to know that you can always have Manifold create a web site for you in a matter of minutes as a fall-back or as an illustrated example to study while learning the system.
Top 10 Manifold Advantages
The following reasons are the top ten reasons Manifold users have reported for preferring Manifold IMS to ArcIMS or ArcGIS Server.
1. More power running 64-bit Windows
Only Manifold System runs as 64-bit code in 64-bit Windows. All Manifold products have run fully 64-bit for years. According to ESRI's web site, ArcIMS not only does not run in 64-bits, it is not even fully certified as a mere 32-bit application when run in 64-bit Windows. All Manifold IMS editions, even the least expensive Professional Runtime at $100, can run either in native 64-bit mode in Windows x64 operating systems or in 32-bit mode when 32-bit Windows operating systems are used. This makes it effortless and zero-cost for Manifold users to scale up to 64-bits.
Discussion: 64-bit Windows has become the standard for web servers because 64-bit Windows systems can provide much better performance at about the same cost as 32-bit systems. 64-bit Intel and AMD processors have been around for years and 64-bit Windows editions like Windows 8 x64, Windows 7 x64, Windows Server 2008 x64 and similar have become the de facto standards for professional webmasters who work in Microsoft environments. Microsoft's outstanding new Windows Server x64 editions (already supported by Manifold with native 64-bit code) have taken the web server world by storm, with each new edition almost instantly becoming every webmaster's choice for the best Windows ever created.
The least expensive way to get more throughput from a web server is to install 64-bit Windows running 64-bit applications with ample amounts of very inexpensive RAM. No other performance measure comes close, not even installing multiple servers, to the "bang for the buck" obtained by moving to 64-bit computing using lots of modern, inexpensive RAM.
Running 32-bit ESRI products in either 32-bit or 64-bit Windows wastes the performance potential of the operating system. It is like taking an eight cylinder automobile engine and cutting the spark plug wires so that only two cylinders operate. Running 64-bit Manifold in 64-bit Windows enables full-power functioning for maximum performance. The end result is being able to serve more visitors to the same web site with less cost in hardware or to serve more complex web sites without adding hardware cost.
Don't be fooled by legacy vendors who say "Our software is fully supported in 64-bit Windows" but who don't tell you that what they are selling is still 32-bit code. Yes, 64-bit Windows editions can execute 32-bit programs, but they do so by emulating 32-bit Windows. For example, you can launch a 32-bit ESRI product in a 64-bit Windows environment like Server x64, but the moment you do so you have lobotomized your 64-bit Windows environment down into 32-bit mode with all the 32-bit limitations on memory usage and all the notorious instability of 32-bit environments compared to the extraordinary reliability of 64-bit Windows. The "Windows on Windows" emulator is also slower than straight Windows, so running a 32-bit ESRI application in 64-bit Windows can actually end up being slower than running it in 32-bit Windows, not a good idea given the well-known performance limitations of 32-bit ESRI products.
Also, don't be fooled by vendors who upgrade a small part of their product line to 64-bits while leaving all the rest in 32-bits: a chain is only as strong as its weakest link, so if the GIS "stack" you are operating has any 32-bit portions you've just gone back to 32-bit operation. Even if ESRI's forecasts for improvements in future years are to be believed, most of their product line will remain 32-bit into the future - it is amazing that anyone can stay in business that long ignoring 64-bit Windows, which has been available since 2005! Only Manifold provides a complete 64-bit GIS environment today and into the foreseeable future.
2. More power running multi-core processors
Only Manifold System runs multiple threads for key processes through multicore processors or multiple processors on a mother board. All ESRI web site references to multi-core processors state that ArcGIS and all other products mentioned on such pages do not utilize either multiple processor cores nor multiple processors on a motherboard. Although ArcIMS is not explicitly mentioned in such ESRI web pages, users report it is unable to take advantage of multi-core processors or multiple processors on a motherboard.
Discussion: In modern times even very inexpensive home systems and notebook computers will feature multi-core processors like Intel Core i7 and similar. More advanced systems now use quad-core processors such as the Intel quad and even six core processors. Prices have dropped so much on quad-core processors that a quad-core system now costs about the same as a dual core system. Both Intel and AMD have announced a focus on yet more cores for future processors.
It would be incomprehensible for a web professional not to use a multi-core processor in a web server. In fact, many web professionals will routinely install web servers that feature not just multi-core processors but also have two or more processor sockets so that two or more multi-core processors can be used. A motherboard with two sockets with a quad core processor in each will provide eight processing cores, which can appear to Windows as sixteen cores via hyperthreading. It's already easy to configure such systems to provide 16 cores or more at very low cost!
ESRI software cannot take advantage of multiple cores, not even of the the two cores in a typical dual core notebook computer let alone the multiple cores in a typical web server. Manifold IMS will take advantage of multiple cores for many key processes to deliver significantly better performance for your computing dollar. The end result is being able to serve more visitors to the same web site with less cost in hardware or to serve more complex web sites without adding hardware cost.
3. Ability to run one server instead of requiring multiple servers
For both 64-bit computing and multi-core computing a critical financial advantage from running Manifold is the ability to avoid running multiple web server machines to serve a given web site. It is a big financial advantage to run a single, more powerful machine instead of running several weaker machines. This is an additional benefit of Manifold's greater power that is often explicitly cited by users as a reason for choosing Manifold over ESRI.
Discussion: One machine normally involves less software cost since only one license need be acquired. It involves less maintenance and less power draw since there are fewer discrete components (fans, power supplies, etc.) to fail. It requires less space. Most important, it is far easier in most cases to create and maintain a web site using a single server than to create clustering or round-robin dispatch software that will automatically integrate web servers, DBMS and GIS on multiple machines.
A single, modern, 64-bit, multi-core machine loaded with ample, inexpensive RAM that runs 64-bit Manifold can handle many hundreds of thousands, or even millions, of hits per day in many web site applications. If 64-bit Manifold can help your web application fit into a single, 64-bit, multi-core web server, that is a huge financial and managerial gain that is worth striving for.
Even if you don't think your web application will ever get millions of hits, it still makes sense to plan for upside by starting with 64-bit Windows and 64-bit Manifold. Few things are as costly or as much regretted as wasting the opportunity to get scalability and growth potential virtually for free as a result of going 64-bits right at the outset. Choosing ESRI means your web application, for all the phenomenally high costs of developing an ESRI web application, will be condemned to running only in 32-bits and will not be as scalable as even the least expensive Manifold application is automatically.
4. Better, silo-free integration with enterprise DBMS
Unlike ArcIMS, Manifold applications (including Manifold IMS) can connect directly to spatial DBMS without requiring middleware. Unlike ArcIMS, Manifold uses the spatial DBMS vendor's own architecture or uses "open" standards. The direct connection between Manifold and the DBMS is faster, more reliable, easier to set up, easier to debug and easier to maintain. ArcIMS requires the use of ArcSDE middleware, which is a separate, very expensive package. Worse still, ArcSDE interposes ESRI's own proprietary interfaces instead of using the DBMS vendor's architecture directly.
Discussion: Almost all web sites above the hobbyist level will utilize an enterprise class DBMS to host geospatial data. The choice of a DBMS is critical to organizations, because many different programs and business processes will work with that DBMS to achieve data centralization. If GIS-related data is stored in that DBMS using proprietary middleware, the key benefits of interoperability between different applications and business processes will be lost.
Manifold interacts with enterprise DBMS in a GIS setting using the DBMS vendor's own data types and access methods, so that data that is read/written/edited via Manifold can also be accessed by any other application using that DBMS's standards. A good example is Oracle.
The leading enterprise DBMS with "spatial" capabilities in the DBMS is Oracle. Manifold can connect directly to Oracle using Oracle's own Oracle Call Interface (OCI) and directly use Oracle Locator and Oracle Spatial capabilities using Oracle's own SDO_GEOMETRY and GeoRaster data types to read/write/edit vector or raster data. Any of hundreds of other applications that interact with Oracle can simultaneously work with that same data within the centralized geospatial data warehouse. Manifold works exactly the same way using the native spatial standards of other enterprise DBMS packages such as SQL Server 2008, IBM DB2 with IBM Spatial Extender and PostgreSQL/PostGIS.
Manifold's direct connection to Oracle and other spatial DBMS packages (a part of all Manifold editions from the $395 Enterprise Edition and up) is available however Manifold is used: as a desktop application, as an objects library or as Manifold IMS. This makes it easy to set up projects and verify them before deploying to web servers.
In contrast, ESRI requires use of ArcSDE to connect to Oracle Spatial and to other enterprise spatial DBMS packages, which transforms those enterprise-class DBMS interfaces from industry standard, well-understood, widely-used interfaces into peculiarly ESRI interfaces. In addition to the inevitable performance loss of using middleware instead of a direct connection, this system would appear to have no reason for existing except to provide a way for ESRI to assure that once customers use ArcSDE they will be forced into buying ESRI software for any program that wishes to connect to the spatial data stored in Oracle or other DBMS. That traps all such data into an ESRI "silo" and defeats the purpose of using an industry standard DBMS package to facilitate interoperability between business processes.
Manifold provides the widest array of silo-free, direct connections to spatial DBMS of any GIS vendor: Manifold can connect directly to Oracle Spatial, IBM DB2 with IBM Spatial Extender, PostgreSQL/PostGIS and even direct connections to Microsoft's SQL Server 2008 spatial product.
In the case of DBMS packages that do not have built-in spatial types (such as SQL Server), Manifold offers choice of a variety of spatial types, including "open" GIS types such as OGC WKB which are well-documented and used by hundreds of different software packages. ESRI, in contrast, forces use of ESRI's own middleware stack.
One last consideration is that ArcSDE is phenomenally expensive. To match the functioning of a direct connection to DBMS as well as IMS that one gets in a $395 Manifold Enterprise Edition package, it is possible in many parts of the world to spend $50,000 just for a single license of ArcSDE plus ArcIMS. Even in the US users will spend tens of thousands of dollars for ArcSDE + ArcIMS.
Manifold is so "into" DBMS as a core part of enterprise and IMS that the Manifold user manual includes detailed instructions on installing and using "Express" editions of all three of the major DBMS packages: Oracle, Microsoft SQL Server and IBM DB2, which are provided free by their vendors and which have the capacity to handle many user needs or to do development. This makes it easy for users to achieve modern, spatial DBMS at near zero cost.
5. More functionality
Because Manifold IMS is the same as Manifold itself, a Manifold IMS installation automatically benefits from the vast array of features described in the over 5000 pages of the Manifold user manual. For example, the Manifold Universal x64 Runtime license used by most IMS installations delivers all Manifold Enterprise Edition features plus all three Manifold extensions. That gives IMS applications access to capabilities like profiles and elevations in surfaces, watershed/hydrology analysis and so forth. In contrast, because ESRI ArcIMS is a separate package, you don't get all of the features in ArcIMS you might read about in other ESRI packages.
Discussion: Modern GIS practise requires access to thousands of capabilities that have evolved through the collective wisdom of GIS practitioners. ArcIMS provides very few tools and capabilities compared to Manifold. Although if you spend enough money with ESRI to buy various different "Arc" products you can cobble up a toolkit with very many features, it's easy to forget that once you jump into ArcIMS you are subject to the limitations of ArcIMS.
Because Manifold IMS is the same program as Manifold itself, you automatically gain access to numerous functional and development facilities within Manifold. A great example is spatial SQL, which is easy to use to provide phenomenal spatial analytic power to web sites. Other examples include geocoding functionality, vast capabilities with projections, sophisticated DBMS capabilities, integrated raster capabilities and integrated 3D terrain visualization. Manifold can even take advantage in dozens of functions of massively-parallel GPGPU architectures to achieve supercomputer peformance using inexpensive NVIDIA® CUDA™ cards to run up to 512 stream processors per server. ArcIMS cannot handle such things any more than a cow can understand a nuclear reactor.
Finally, Manifold IMS is not just an ordinary HTML map server. Manifold IMS also provides Manifold image server capability like that seen in Virtual Earth and Google Earth, OGC WMS "open" image servers and even OGC WFS-T (feature server with edit-back transactions) server capability, which allows OGC WFS-T clients to edit through the web portal data that could be resident on some remote spatial DBMS. Some legacy IMS packages charge thousands of dollars extra for things like WFS-T capability.
6. One object model instead of multiple object models
Because Manifold IMS is the same program as Manifold itself, there is only one, consistent object model programmers need learn. In dramatic contrast, ESRI ArcIMS uses a different object model than other ESRI products, which is a cruel trap for programmers.
Discussion: An "object model" specifies the programmatic interface exposed by a product so that programmers can write programs that work with that product. If two different products that are designed to work with the same data use different object models, then a program written for one of the products will not work with the other. It will require modification, which can be very costly both for the initial modification as well as for subsequent maintenance. Few things are as costly as trying to maintain two, slightly different versions of the same program over time.
Non-trivial web applications using an IMS will often utilize programming to customize the functionality and appearance of the application. Such web sites will require several phases of development, including acquiring and organizing the data to be used in the site, writing and verifying the program logic and algorithms used against that data and then finally creating, deploying and debugging the actual web application itself.
In the case of ESRI products, different packages are used for those different phases, each of which often will require programming. Because those different packages utilize different object models the programmers involved in the development of the web site will need expert familiarity with those differences so that they can make changes in their work when different ESRI packages are involved. Any experienced development manager will immediately see that such a situation is a formula for disaster.
Setting aside the potential for error, many experienced ESRI developers remark that they often end up coding each application two or three times during different phases of development and usage to deal with the vagaries of different ESRI object models.
In contrast, because Manifold IMS is Manifold itself, the exact same object model applies throughout. Programmers use a single, identical interface throughout all phases of the project. What is written and debugged once stays written and debugged throughout.
7. Easier to learn, easier to deploy and easier to maintain
Because Manifold IMS is Manifold itself, learning Manifold interactively also teaches capabilities in Manifold IMS. It is a lot easier to learn a package interactively with the full support of interactive menus and commands, using the keyboard and mouse, than it is to attempt to get your head around some programmatic "black box" like ArcIMS.
Discussion: With Manifold, one can use the interactive application to learn, test-bed and debug key aspects of the proposed web site. In contrast, until you know enough to get a full web site launched in ArcIMS nothing happens. Although it is of course possible, even required, to use other ESRI tools like ArcView or other ArcGIS tools to help cobble up a web site using ArcIMS, at the end of the process because those tools are different packages there is still a leap of faith and a minimum reservoir of expert skill required to make a final translation into ArcIMS. It is a "make it or break it" process.
With Manifold one can simplify the process into smaller steps, each of which can be accomplished easily with low risk. Projects can be developed within Manifold interactively with no programming risk at all. Once developed, they can be published in trial form automatically using Manifold's Export Web Page dialog to create a web site without programming. The sites thus written by Manifold can then be customized while learning the system, secure in the knowledge that at any point one can fall back to the automatically-written web site to help resolve any difficulty.
More advanced web applications can be prototyped within interactive Manifold sessions using the programming development environment built into Manifold. ESRI requires scripting outside of ESRI products, but within Manifold one can actually pop open a script window and write code within Manifold itself, using any ActiveX or .NET programming language. This allows very rapid development and prototyping using standard Microsoft languages within Manifold itself.
Most web sites are not static. They change over time as data changes and business processes and requirements change. The hardware and host operating system will change over time. The GIS tools used will change over time. At all stages of the game, you must be able to confidently and reliably evolve your web site at low cost. Manifold makes this easy. ESRI makes it very difficult and very expensive.
Almost all organizational web sites will require major GIS functionality in several key areas: data intake, preparation, editing, and update; interaction with DBMS; programming and finally, actual IMS publication in conjunction with a web server. Manifold provides all functions in a single integrated package. Everything works together automatically as Manifold evolves because Manifold releases are published as single, integrated updates. Routine updates are free and include automatic support for new versions of Windows. When a new version of Windows emerges all parts of Manifold support it on the same day, because Manifold is a single, integrated package.
In contrast, ESRI provides required functions using separate packages, for example, the ArcGIS suite of products, ArcSDE and ArcIMS. Those separate packages have separate product life cycles as ESRI releases different versions at different times. The web developer using ESRI therefore has to constantly worry about resolving multiple gotcha's and repeat re-integration as ESRI desktop, SDE and IMS applications are independently revised. That's especially difficult and costly if at the same time the web developer must re-integrate such complex packages when the DBMS vendor issues updates or when the hardware vendor upgrades hardware, or the development system is revised or Microsoft issues Windows updates.
To consider a real-life example, when ESRI decides to support the many versions of Vista, which of the many pieces of ESRI's product puzzle will support Vista, and does anyone think that all of the pieces involved in a sophisticated IMS application will be upgraded on the same day to support all of the different versions of Vista in the same way?
It is difficult enough just to keep the different ESRI pieces of the puzzle working together and harder still to figure out how each of those different ESRI puzzle pieces are affected by updates in DBMS, Visual Studio and Windows. No wonder administrators of ArcIMS applications are famously fearful of any changes!
8. Focus on Microsoft: Windows 7, Vista and Windows Server 2008 support today
Manifold has a total commitment to Microsoft technologies. No other GIS vendor even comes close to the depth and timeliness of Manifold focus on Microsoft. ESRI has historically lagged in supporting Microsoft technologies, often deploying support for key Microsoft technologies several years after Manifold.
Discussion: The Microsoft ecosystem rewards those who embrace it expertly and whole-heartedly. By embracing Microsoft standards one can achieve astonishing price/performance and interoperability with hundreds of thousands of applications. The Microsoft ecosystem includes a wealth of free and low cost resources for those who fully support Microsoft standards.
Manifold begins work with emerging Microsoft technologies years ahead of their release to the general public. That's why Manifold was the first to run 64-bits in 64-bit Windows and why Manifold supports Windows 8, Windows 7 and Windows Server editions today, including native 64-bit code for Windows 8 x64, Windows 7 x64, Vista x64 and x64 Windows Server editions. It's also why Manifold was the first GIS to support built-in programming using Microsoft ActiveX scripting languages and then later the first GIS to support built-in programming using Microsoft .NET languages like C# and VB.NET. Manifold was the first GIS (and the first IMS) to include use of Microsoft's .NET Framework and Manifold is the only GIS and IMS that has been tracking the .NET Framework in near real-time as it evolves into new versions.
Manifold was the only GIS vendor to ship built-in native spatial support for Microsoft's spatial DBMS product, Microsoft SQL Server spatial (code named "Katmai") even before it came out of beta for public use.
In contrast, ESRI has lagged behind Manifold in supporting Microsoft technologies and at times has even chosen alien technologies in opposition to Microsoft standards. The lag effect can be seen today with failure to support Vista on launch while opposition to Microsoft standards can be seen in ArcIMS's choice of Java instead of a Microsoft language. The use of Java may endear ESRI to anti-Microsoft partisans, but it interposes yet another obstacle to seamless integration with the Microsoft ecosystem.
It also injects yet more room for error by making any ArcIMS web application held hostage to whatever changes may occur in the Java SDK that used by ArcIMS and is published by SUN, a notorious enemy of Microsoft. No business manager in his or her right mind would knowingly expose a costly web application to the political risks of SUN's competition with Microsoft.
In contrast, Manifold IMS uses only 100% Microsoft technologies. Besides eliminating the risk that some third party might not support Microsoft as well as you would like, using exclusively Microsoft technologies guarantees that a Manifold IMS application will automatically take advantage of the billions of dollars Microsoft spends to assure that major Microsoft updates will continue to support those Microsoft standards upon which your application depends.
9. Faster upgrades and more improvements
Manifold delivers by far the fastest rate of improvements of any GIS vendor. Updates now average approximately 1000 improvements per year, including a range of new features as well as bug fixes and other improvements. The large number of improvements together with frequent updates assure that not only is Manifold more responsive to the wishes of the Manifold user community but that any bugs which do arise are rapidly identified and eliminated. Because Manifold IMS is Manifold itself, any improvements to any part of Manifold will also improve Manifold IMS in those parts as well. In contrast, ESRI has an extraordinarily slow rate of improvements to ArcIMS, whether it is in ArcIMS itself or other product configurations such as ArcGIS Server.
Discussion: Computer technology changes very rapidly and complex systems such as any IMS product necessarily involve tens of thousands of details, many of which need to be continuously improved to keep up with changes in the web server environment, to respond to user requests, to take advantage of advances in related software such as .NET or DBMS and to rapidly identify and fix any bugs that emerge. The larger the user base, the more sophisticated the applications, the greater the importance of continuous, reliable improvements in your IMS package.
Manifold IMS is famously bulletproof exactly because manifold.net maintains the product with fanatic diligence. It's not just a matter of eliminating bugs before users encounter them, it is also a matter of assuring that product technology is continuously improved so that any rough edges are removed before they can cause user errors or other difficulties. More IMS web sites run on Manifold IMS than any other IMS, so by listening to the desires of many Manifold users and rapidly responding to their suggestions manifold.net can leverage the collective intelligence and experience of the entire Manifold user community to help make Manifold IMS a better product for you.
Although not as many organizations host IMS web sites as use GIS interactively, with Manifold even the relatively smaller IMS user community will benefit from optimizations and other improvements prompted by the very much larger community of interactive Manifold users. For example, recent dramatic increases in performance of topology algorithms will help the performance of IMS sites even though they were originally suggested by non-IMS users. ESRI's ArcIMS does not benefit from such synergies because it is a separate product from ESRI's mainstream desktop GIS products.
Finally, by thoroughly embedding Microsoft technologies within the common Manifold engine that runs IMS as well as all other Manifold uses, manifold.net assures that any advances in Microsoft technologies, such as improved internal performance or new .NET features, will automatically create a better product for Manifold IMS users as well.
10. Dramatically lower initial cost and recurring costs
Typical Manifold IMS costs are on the order of 40 times less than typical ESRI ArcIMS costs, even though the ArcIMS solution will usually do less and offer lower performance on a modern web server. Recurring costs with ArcIMS tend to be much higher than Manifold IMS as well.
Discussion: A Manifold IMS license need not cost any more than a single Professional x64 Runtime license per web server, only $100 per web server. Because of the very low cost of Manifold runtime licenses, most organizations will deploy Manifold IMS applications using a Manifold Universal x64 Runtime license, which is only $225 per web server. The same low price per web server applies no matter how many applications are hosted on that web server, no matter how many users access it, no matter how many pages are served and no matter how many processors or processor cores are running inside that web server. It is one low price per web server.
Runtime licenses are so low in cost that Manifold provides x64 versions which can run in either 32-bit or 64-bit mode for the same low price. No maintenance fees or recurring fees are required, as routine updates may be downloaded for free. However, most IMS users will budget approximately $50 per year as they plan to take advantage of upgrade offers when major new versions are released.
Note that a Universal runtime license includes full Enterprise capability, including direct connection to Oracle Spatial, SQL Server 2008 spatial and other spatial DBMS use as well as full enterprise IMS capability, including the full range of HTML server, image server, WMS server and WFS-T server capability. An attempt to duplicate that same range of capabilities with ESRI products would require at least ArcSDE in addition to ArcIMS for even greater cost, requiring tens of thousands of dollars more per installation. Further, ESRI requires massively expensive maintenance fees and upgrade fees for much greater recurring costs than Manifold IMS.
Manifold.net is often asked how it is possible that anyone would buy ESRI ArcIMS when superior alternatives like Manifold IMS are available. Not surprisingly, the answer is that usually people who have a choice in the matter don't buy ArcIMS if they know about Manifold IMS. It is no accident that Manifold IMS has overwhelmingly more installations than ArcIMS.
Visit the following pages for additional, detailed information on Manifold IMS:
- Internet Map Server - Manifold IMS home page.
- IMS Requirements - Hardware and software requirements for running Manifold IMS.
- Live IMS Examples - Live examples of IMS running on manifold.net servers, with links to complete source code for examples.
- IMS FAQ - Frequently asked questions and answers.
Please contact us at firstname.lastname@example.org. We would like you to be happy with your licensing of Manifold products, so please do not hesitate to ask any questions before placing an order.
Suggestions to improve Manifold are always welcome. Please see the Suggestions page for tips on making effective suggestions.