Alternatives to GeoServer logo

Alternatives to GeoServer

ArcGIS, PostGIS, NGINX, Apache HTTP Server, and Amazon EC2 are the most popular alternatives and competitors to GeoServer.
92
81
+ 1
0

What is GeoServer and what are its top alternatives?

GeoServer is an open source server software that allows users to share and edit geospatial data. It supports multiple data sources and formats, offers powerful styling capabilities, and provides a web interface for easy configuration. However, GeoServer can be complex to set up and maintain for beginners, and may require some level of technical expertise to optimize performance.

  1. MapServer: MapServer is an open source platform for publishing spatial data and interactive mapping applications. It supports a wide range of data formats and provides advanced styling options. Pros: Strong support for map rendering and extensive documentation. Cons: Steeper learning curve compared to some other alternatives.
  2. ArcGIS Server: ArcGIS Server is a commercial product that offers comprehensive GIS capabilities for managing and sharing geospatial data. It provides advanced spatial analysis tools and integrates seamlessly with other Esri products. Pros: Robust functionality and seamless integration with Esri ecosystem. Cons: Higher cost compared to open source alternatives.
  3. Mapnik: Mapnik is a powerful mapping toolkit for rendering geospatial data. It is widely used in various mapping applications and supports various data sources and formats. Pros: High-quality map rendering and flexibility in customization. Cons: Requires some programming knowledge to utilize fully.
  4. PostGIS: PostGIS is a spatial database extender for PostgreSQL that adds support for geographic objects. It enables spatial queries and analysis within a relational database environment. Pros: Seamless integration with PostgreSQL and strong support for spatial operations. Cons: Requires familiarity with SQL and database administration.
  5. QGIS Server: QGIS Server is an open source WMS implementation that allows users to publish QGIS projects as web maps. It provides a user-friendly interface for configuring map services and supports various data formats. Pros: Easy integration with QGIS desktop and user-friendly interface. Cons: Limited support for complex styling compared to other alternatives.
  6. UDIG: uDig is an open source desktop GIS application that also includes functionality for serving geospatial data via web services. It offers a user-friendly interface for data visualization and analysis. Pros: Intuitive interface and strong support for desktop GIS workflows. Cons: Limited scalability for large-scale deployments.
  7. Mapbox: Mapbox is a cloud-based platform for creating and managing custom maps. It offers powerful styling tools, customizable data visualizations, and APIs for integrating maps into web and mobile applications. Pros: High-quality mapping services and extensive customization options. Cons: Subscription-based pricing model may be costly for some users.
  8. Terracotta: Terracotta is a platform for managing and analyzing geospatial data at scale. It provides advanced caching and data processing capabilities, making it suitable for high-performance GIS applications. Pros: Scalable architecture and efficient data processing. Cons: Complexity in setting up and configuring the platform.
  9. Boundless Suite: Boundless Suite is a commercial geospatial solution that includes various components for managing and publishing geospatial data. It offers advanced data visualization tools, spatial analysis capabilities, and support for cloud deployment. Pros: Comprehensive geospatial functionality and professional support services. Cons: Higher cost compared to open source alternatives.
  10. GeoTools: GeoTools is an open source Java library for geospatial data processing and analysis. It provides a wide range of GIS functionalities and supports various data formats. Pros: Extensive library of geospatial tools and active developer community. Cons: Requires programming knowledge to utilize effectively.

Top Alternatives to GeoServer

  • ArcGIS
    ArcGIS

    It is a geographic information system for working with maps and geographic information. It is used for creating and using maps, compiling geographic data, analyzing mapped information, sharing and much more. ...

  • PostGIS
    PostGIS

    PostGIS is a spatial database extender for PostgreSQL object-relational database. It adds support for geographic objects allowing location queries to be run in SQL. ...

  • NGINX
    NGINX

    nginx [engine x] is an HTTP and reverse proxy server, as well as a mail proxy server, written by Igor Sysoev. According to Netcraft nginx served or proxied 30.46% of the top million busiest sites in Jan 2018. ...

  • Apache HTTP Server
    Apache HTTP Server

    The Apache HTTP Server is a powerful and flexible HTTP/1.1 compliant web server. Originally designed as a replacement for the NCSA HTTP Server, it has grown to be the most popular web server on the Internet. ...

  • Amazon EC2
    Amazon EC2

    It is a web service that provides resizable compute capacity in the cloud. It is designed to make web-scale computing easier for developers. ...

  • Firebase
    Firebase

    Firebase is a cloud service designed to power real-time, collaborative applications. Simply add the Firebase library to your application to gain access to a shared data structure; any changes you make to that data are automatically synchronized with the Firebase cloud and with other clients within milliseconds. ...

  • Amazon Web Services (AWS)
    Amazon Web Services (AWS)

    It is a comprehensive and broadly adopted cloud platform, offering over 200 fully featured services from data centers globally. ...

  • Google Cloud Platform
    Google Cloud Platform

    It helps you build what's next with secure infrastructure, developer tools, APIs, data analytics and machine learning. It is a suite of cloud computing services that runs on the same infrastructure that Google uses internally for its end-user products, such as Google Search and YouTube. ...

GeoServer alternatives & related posts

ArcGIS logo

ArcGIS

137
20
A geographic information system for working with maps
137
20
PROS OF ARCGIS
  • 7
    Reponsive
  • 4
    A lot of widgets
  • 4
    Data driven vizualisation
  • 2
    Easy tà learn
  • 2
    3D
  • 1
    Easy API
CONS OF ARCGIS
    Be the first to leave a con

    related ArcGIS posts

    Stephen Gheysens
    Lead Solutions Engineer at Inscribe · | 7 upvotes · 475.5K views

    Google Maps lets "property owners and their authorized representatives" upload indoor maps, but this appears to lack navigation ("wayfinding").

    MappedIn is a platform and has SDKs for building indoor mapping experiences (https://www.mappedin.com/) and ESRI ArcGIS also offers some indoor mapping tools (https://www.esri.com/en-us/arcgis/indoor-gis/overview). Finally, there used to be a company called LocusLabs that is now a part of Atrius and they were often integrated into airlines' apps to provide airport maps with wayfinding (https://atrius.com/solutions/personal-experiences/personal-wayfinder/).

    I previously worked at Mapbox and while I believe that it's a great platform for building map-based experiences, they don't have any simple solutions for indoor wayfinding. If I were doing this for fun as a side-project and prioritized saving money over saving time, here is what I would do:

    • Create a graph-based dataset representing the walking paths around your university, where nodes/vertexes represent the intersections of paths, and edges represent paths (literally paths outside, hallways, short path segments that represent entering rooms). You could store this in a hosted graph-based database like Neo4j, Amazon Neptune , or Azure Cosmos DB (with its Gremlin API) and use built-in "shortest path" queries, or deploy a PostgreSQL service with pgRouting.

    • Add two properties to each edge: one property for the distance between its nodes (libraries like @turf/helpers will have a distance function if you have the latitude & longitude of each node), and another property estimating the walking time (based on the distance). Once you have these values saved in a graph-based format, you should be able to easily query and find the data representation of paths between two points.

    • At this point, you'd have the routing problem solved and it would come down to building a UI. Mapbox arguably leads the industry in developer tools for custom map experiences. You could convert your nodes/edges to GeoJSON, then either upload to Mapbox and create a Tileset to visualize the paths, or add the GeoJSON to the map on the fly.

    *You might be able to use open source routing tools like OSRM (https://github.com/Project-OSRM/osrm-backend/issues/6257) or Graphhopper (instead of a custom graph database implementation), but it would likely be more involved to maintain these services.

    See more
    PostGIS logo

    PostGIS

    370
    30
    Open source spatial database
    370
    30
    PROS OF POSTGIS
    • 25
      De facto GIS in SQL
    • 5
      Good Documentation
    CONS OF POSTGIS
      Be the first to leave a con

      related PostGIS posts

      NGINX logo

      NGINX

      113.6K
      5.5K
      A high performance free open source web server powering busiest sites on the Internet.
      113.6K
      5.5K
      PROS OF NGINX
      • 1.4K
        High-performance http server
      • 894
        Performance
      • 730
        Easy to configure
      • 607
        Open source
      • 530
        Load balancer
      • 289
        Free
      • 288
        Scalability
      • 226
        Web server
      • 175
        Simplicity
      • 136
        Easy setup
      • 30
        Content caching
      • 21
        Web Accelerator
      • 15
        Capability
      • 14
        Fast
      • 12
        High-latency
      • 12
        Predictability
      • 8
        Reverse Proxy
      • 7
        Supports http/2
      • 7
        The best of them
      • 5
        Great Community
      • 5
        Lots of Modules
      • 5
        Enterprise version
      • 4
        High perfomance proxy server
      • 3
        Embedded Lua scripting
      • 3
        Streaming media delivery
      • 3
        Streaming media
      • 3
        Reversy Proxy
      • 2
        Blash
      • 2
        GRPC-Web
      • 2
        Lightweight
      • 2
        Fast and easy to set up
      • 2
        Slim
      • 2
        saltstack
      • 1
        Virtual hosting
      • 1
        Narrow focus. Easy to configure. Fast
      • 1
        Along with Redis Cache its the Most superior
      • 1
        Ingress controller
      CONS OF NGINX
      • 10
        Advanced features require subscription

      related NGINX posts

      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 11.7M views

      Our whole DevOps stack consists of the following tools:

      • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
      • Respectively Git as revision control system
      • SourceTree as Git GUI
      • Visual Studio Code as IDE
      • CircleCI for continuous integration (automatize development process)
      • Prettier / TSLint / ESLint as code linter
      • SonarQube as quality gate
      • Docker as container management (incl. Docker Compose for multi-container application management)
      • VirtualBox for operating system simulation tests
      • Kubernetes as cluster management for docker containers
      • Heroku for deploying in test environments
      • nginx as web server (preferably used as facade server in production environment)
      • SSLMate (using OpenSSL) for certificate management
      • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
      • PostgreSQL as preferred database system
      • Redis as preferred in-memory database/store (great for caching)

      The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

      • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
      • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
      • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
      • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
      • Scalability: All-in-one framework for distributed systems.
      • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
      See more
      John-Daniel Trask
      Co-founder & CEO at Raygun · | 19 upvotes · 489.5K views

      We chose AWS because, at the time, it was really the only cloud provider to choose from.

      We tend to use their basic building blocks (EC2, ELB, Amazon S3, Amazon RDS) rather than vendor specific components like databases and queuing. We deliberately decided to do this to ensure we could provide multi-cloud support or potentially move to another cloud provider if the offering was better for our customers.

      We’ve utilized c3.large nodes for both the Node.js deployment and then for the .NET Core deployment. Both sit as backends behind an nginx instance and are managed using scaling groups in Amazon EC2 sitting behind a standard AWS Elastic Load Balancing (ELB).

      While we’re satisfied with AWS, we do review our decision each year and have looked at Azure and Google Cloud offerings.

      #CloudHosting #WebServers #CloudStorage #LoadBalancerReverseProxy

      See more
      Apache HTTP Server logo

      Apache HTTP Server

      64.6K
      1.4K
      Open-source HTTP server for modern operating systems including UNIX and Windows
      64.6K
      1.4K
      PROS OF APACHE HTTP SERVER
      • 479
        Web server
      • 305
        Most widely-used web server
      • 217
        Virtual hosting
      • 148
        Fast
      • 138
        Ssl support
      • 44
        Since 1996
      • 28
        Asynchronous
      • 5
        Robust
      • 4
        Proven over many years
      • 2
        Mature
      • 2
        Perfomance
      • 1
        Perfect Support
      • 0
        Many available modules
      • 0
        Many available modules
      CONS OF APACHE HTTP SERVER
      • 4
        Hard to set up

      related Apache HTTP Server posts

      Nick Rockwell
      SVP, Engineering at Fastly · | 46 upvotes · 4.2M views

      When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

      So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

      React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

      Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

      See more
      Tim Abbott
      Shared insights
      on
      NGINXNGINXApache HTTP ServerApache HTTP Server
      at

      We've been happy with nginx as part of our stack. As an open source web application that folks install on-premise, the configuration system for the webserver is pretty important to us. I have a few complaints (e.g. the configuration syntax for conditionals is a pain), but overall we've found it pretty easy to build a configurable set of options (see link) for how to run Zulip on nginx, both directly and with a remote reverse proxy in front of it, with a minimum of code duplication.

      Certainly I've been a lot happier with it than I was working with Apache HTTP Server in past projects.

      See more
      Amazon EC2 logo

      Amazon EC2

      48.4K
      2.5K
      Scalable, pay-as-you-go compute capacity in the cloud
      48.4K
      2.5K
      PROS OF AMAZON EC2
      • 647
        Quick and reliable cloud servers
      • 515
        Scalability
      • 393
        Easy management
      • 277
        Low cost
      • 271
        Auto-scaling
      • 89
        Market leader
      • 80
        Backed by amazon
      • 79
        Reliable
      • 67
        Free tier
      • 58
        Easy management, scalability
      • 13
        Flexible
      • 10
        Easy to Start
      • 9
        Widely used
      • 9
        Web-scale
      • 9
        Elastic
      • 7
        Node.js API
      • 5
        Industry Standard
      • 4
        Lots of configuration options
      • 2
        GPU instances
      • 1
        Simpler to understand and learn
      • 1
        Extremely simple to use
      • 1
        Amazing for individuals
      • 1
        All the Open Source CLI tools you could want.
      CONS OF AMAZON EC2
      • 13
        Ui could use a lot of work
      • 6
        High learning curve when compared to PaaS
      • 3
        Extremely poor CPU performance

      related Amazon EC2 posts

      Ashish Singh
      Tech Lead, Big Data Platform at Pinterest · | 38 upvotes · 3.4M views

      To provide employees with the critical need of interactive querying, we’ve worked with Presto, an open-source distributed SQL query engine, over the years. Operating Presto at Pinterest’s scale has involved resolving quite a few challenges like, supporting deeply nested and huge thrift schemas, slow/ bad worker detection and remediation, auto-scaling cluster, graceful cluster shutdown and impersonation support for ldap authenticator.

      Our infrastructure is built on top of Amazon EC2 and we leverage Amazon S3 for storing our data. This separates compute and storage layers, and allows multiple compute clusters to share the S3 data.

      We have hundreds of petabytes of data and tens of thousands of Apache Hive tables. Our Presto clusters are comprised of a fleet of 450 r4.8xl EC2 instances. Presto clusters together have over 100 TBs of memory and 14K vcpu cores. Within Pinterest, we have close to more than 1,000 monthly active users (out of total 1,600+ Pinterest employees) using Presto, who run about 400K queries on these clusters per month.

      Each query submitted to Presto cluster is logged to a Kafka topic via Singer. Singer is a logging agent built at Pinterest and we talked about it in a previous post. Each query is logged when it is submitted and when it finishes. When a Presto cluster crashes, we will have query submitted events without corresponding query finished events. These events enable us to capture the effect of cluster crashes over time.

      Each Presto cluster at Pinterest has workers on a mix of dedicated AWS EC2 instances and Kubernetes pods. Kubernetes platform provides us with the capability to add and remove workers from a Presto cluster very quickly. The best-case latency on bringing up a new worker on Kubernetes is less than a minute. However, when the Kubernetes cluster itself is out of resources and needs to scale up, it can take up to ten minutes. Some other advantages of deploying on Kubernetes platform is that our Presto deployment becomes agnostic of cloud vendor, instance types, OS, etc.

      #BigData #AWS #DataScience #DataEngineering

      See more
      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 11.7M views

      Our whole DevOps stack consists of the following tools:

      • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
      • Respectively Git as revision control system
      • SourceTree as Git GUI
      • Visual Studio Code as IDE
      • CircleCI for continuous integration (automatize development process)
      • Prettier / TSLint / ESLint as code linter
      • SonarQube as quality gate
      • Docker as container management (incl. Docker Compose for multi-container application management)
      • VirtualBox for operating system simulation tests
      • Kubernetes as cluster management for docker containers
      • Heroku for deploying in test environments
      • nginx as web server (preferably used as facade server in production environment)
      • SSLMate (using OpenSSL) for certificate management
      • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
      • PostgreSQL as preferred database system
      • Redis as preferred in-memory database/store (great for caching)

      The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

      • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
      • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
      • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
      • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
      • Scalability: All-in-one framework for distributed systems.
      • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
      See more
      Firebase logo

      Firebase

      41.2K
      2K
      The Realtime App Platform
      41.2K
      2K
      PROS OF FIREBASE
      • 371
        Realtime backend made easy
      • 270
        Fast and responsive
      • 242
        Easy setup
      • 215
        Real-time
      • 191
        JSON
      • 134
        Free
      • 128
        Backed by google
      • 83
        Angular adaptor
      • 68
        Reliable
      • 36
        Great customer support
      • 32
        Great documentation
      • 25
        Real-time synchronization
      • 21
        Mobile friendly
      • 19
        Rapid prototyping
      • 14
        Great security
      • 12
        Automatic scaling
      • 11
        Freakingly awesome
      • 8
        Super fast development
      • 8
        Angularfire is an amazing addition!
      • 8
        Chat
      • 6
        Firebase hosting
      • 6
        Built in user auth/oauth
      • 6
        Awesome next-gen backend
      • 6
        Ios adaptor
      • 4
        Speed of light
      • 4
        Very easy to use
      • 3
        Great
      • 3
        It's made development super fast
      • 3
        Brilliant for startups
      • 2
        Free hosting
      • 2
        Cloud functions
      • 2
        JS Offline and Sync suport
      • 2
        Low battery consumption
      • 2
        .net
      • 2
        The concurrent updates create a great experience
      • 2
        Push notification
      • 2
        I can quickly create static web apps with no backend
      • 2
        Great all-round functionality
      • 2
        Free authentication solution
      • 1
        Easy Reactjs integration
      • 1
        Google's support
      • 1
        Free SSL
      • 1
        CDN & cache out of the box
      • 1
        Easy to use
      • 1
        Large
      • 1
        Faster workflow
      • 1
        Serverless
      • 1
        Good Free Limits
      • 1
        Simple and easy
      CONS OF FIREBASE
      • 31
        Can become expensive
      • 16
        No open source, you depend on external company
      • 15
        Scalability is not infinite
      • 9
        Not Flexible Enough
      • 7
        Cant filter queries
      • 3
        Very unstable server
      • 3
        No Relational Data
      • 2
        Too many errors
      • 2
        No offline sync

      related Firebase posts

      Stephen Gheysens
      Lead Solutions Engineer at Inscribe · | 14 upvotes · 1.8M views

      Hi Otensia! I'd definitely recommend using the skills you've already got and building with JavaScript is a smart way to go these days. Most platform services have JavaScript/Node SDKs or NPM packages, many serverless platforms support Node in case you need to write any backend logic, and JavaScript is incredibly popular - meaning it will be easy to hire for, should you ever need to.

      My advice would be "don't reinvent the wheel". If you already have a skill set that will work well to solve the problem at hand, and you don't need it for any other projects, don't spend the time jumping into a new language. If you're looking for an excuse to learn something new, it would be better to invest that time in learning a new platform/tool that compliments your knowledge of JavaScript. For this project, I might recommend using Netlify, Vercel, or Google Firebase to quickly and easily deploy your web app. If you need to add user authentication, there are great examples out there for Firebase Authentication, Auth0, or even Magic (a newcomer on the Auth scene, but very user friendly). All of these services work very well with a JavaScript-based application.

      See more
      Eugene Cheah

      For inboxkitten.com, an opensource disposable email service;

      We migrated our serverless workload from Cloud Functions for Firebase to CloudFlare workers, taking advantage of the lower cost and faster-performing edge computing of Cloudflare network. Made possible due to our extremely low CPU and RAM overhead of our serverless functions.

      If I were to summarize the limitation of Cloudflare (as oppose to firebase/gcp functions), it would be ...

      1. <5ms CPU time limit
      2. Incompatible with express.js
      3. one script limitation per domain

      Limitations our workload is able to conform with (YMMV)

      For hosting of static files, we migrated from Firebase to CommonsHost

      More details on the trade-off in between both serverless providers is in the article

      See more
      Amazon Web Services (AWS) logo

      Amazon Web Services (AWS)

      30.1K
      0
      A comprehensive and broadly adopted cloud platform
      30.1K
      0
      PROS OF AMAZON WEB SERVICES (AWS)
        Be the first to leave a pro
        CONS OF AMAZON WEB SERVICES (AWS)
          Be the first to leave a con

          related Amazon Web Services (AWS) posts

          waheed khan
          Associate Java Developer at txtsol · | 11 upvotes · 72.9K views

          I want to make application like Zomato, #Foodpanda.

          Which stack is best for this? As I have expertise in Java and Angular. What is the best stack you will recommend?

          Web Micro-service / Mono? Angular / React? Amazon Web Services (AWS) / Google Cloud Platform? DB : SQL or No SQL

          Mob Cross-platform: React Native / Flutter

          Note: We are a team of 5. what languages do you recommend if I go with microservices?

          Thanks

          See more
          Santiago Velasco
          Java Software Developer at ViewNext · | 8 upvotes · 28.6K views

          Hello everyone, I would like to start using a cloud service to host my projects, which are web applications. If anyone has enough experience with Microsoft Azure, Amazon Web Services (AWS) or Google Cloud Platform, I would like to know which of these is most recommended to use, depending on the features they have or how used they are. Thank you so much.

          See more
          Google Cloud Platform logo

          Google Cloud Platform

          25.6K
          18
          A suite of cloud computing services
          25.6K
          18
          PROS OF GOOGLE CLOUD PLATFORM
          • 5
            Good app Marketplace for Beginner and Advanced User
          • 4
            1 year free trial credit USD300
          • 3
            Premium tier IP address
          • 3
            Live chat support
          • 3
            Cheap
          CONS OF GOOGLE CLOUD PLATFORM
            Be the first to leave a con

            related Google Cloud Platform posts

            waheed khan
            Associate Java Developer at txtsol · | 11 upvotes · 72.9K views

            I want to make application like Zomato, #Foodpanda.

            Which stack is best for this? As I have expertise in Java and Angular. What is the best stack you will recommend?

            Web Micro-service / Mono? Angular / React? Amazon Web Services (AWS) / Google Cloud Platform? DB : SQL or No SQL

            Mob Cross-platform: React Native / Flutter

            Note: We are a team of 5. what languages do you recommend if I go with microservices?

            Thanks

            See more

            My days of using Firebase are over! I want to move to something scalable and possibly less cheap. In the past seven days I have done my research on what type of DB best fits my needs, and have chosen to go with the nonrelational DB; MongoDB. Although I understand it, I need help understanding how to set up the architecture. I have the client app (Flutter/ Dart) that would make HTTP requests to the web server (node/express), and from there the webserver would query data from MongoDB.

            How should I go about hosting the web server and MongoDb; do they have to be hosted together (this is where a lot of my confusion is)? Based on the research I've done, it seems like the standard practice would be to host on a VM provided by services such as Amazon Web Services, Google Cloud Platform, Microsoft Azure, etc. If there are better ways, such as possibly self-hosting (more responsibility), should I? Anyways, I just want to confirm with a community (you guys) to make sure I do this right, all input is highly appreciated.

            See more