Alternatives to CloudApp logo

Alternatives to CloudApp

Dropbox, Fleeq, Loom, MySQL, and PostgreSQL are the most popular alternatives and competitors to CloudApp.
22
17
+ 1
0

What is CloudApp and what are its top alternatives?

Cloud-based visual communication technology. Used by developers, designers, and product managers to efficiently and effectively communicate complicated ideas across the globe with clarity and context.
CloudApp is a tool in the Cloud File Storage category of a tech stack.

Top Alternatives to CloudApp

  • Dropbox
    Dropbox

    Harness the power of Dropbox. Connect to an account, upload, download, search, and more. ...

  • Fleeq
    Fleeq

    It enables you to create bite-size training videos in minutes and then track, embed, optimize, localize and share them in seconds. ...

  • Loom
    Loom

    It is a work communication tool that helps you get your message across through instantly shareable video. ...

  • MySQL
    MySQL

    The MySQL software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software. ...

  • PostgreSQL
    PostgreSQL

    PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions. ...

  • MongoDB
    MongoDB

    MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding. ...

  • Redis
    Redis

    Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache, and message broker. Redis provides data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs, geospatial indexes, and streams. ...

  • Amazon S3
    Amazon S3

    Amazon Simple Storage Service provides a fully redundant data storage infrastructure for storing and retrieving any amount of data, at any time, from anywhere on the web ...

CloudApp alternatives & related posts

Dropbox logo

Dropbox

23.5K
1.7K
Build the power of Dropbox into your apps
23.5K
1.7K
PROS OF DROPBOX
  • 434
    Easy to work with
  • 256
    Free
  • 216
    Popular
  • 176
    Shared file hosting
  • 167
    'just works'
  • 100
    No brainer
  • 80
    Integration with external services
  • 77
    Simple
  • 49
    Good api
  • 38
    Least cost (free) for the basic needs case
  • 11
    It just works
  • 8
    Convenient
  • 7
    Accessible from all of my devices
  • 5
    Command Line client
  • 4
    Synchronizing laptop and desktop - work anywhere
  • 4
    Can even be used by your grandma
  • 3
    Cross platform app
  • 3
    Sync API
  • 3
    Reliable
  • 3
    Mac app
  • 2
    Backups, local and cloud
  • 2
    Everybody needs to share and synchronize files reliably
  • 2
    Delta synchronization
  • 2
    Ability to pay monthly without losing your files
  • 2
    Extended version history
  • 2
    Beautiful UI
  • 1
    YC Company
  • 1
    What a beautiful app
  • 1
    Easy/no setup
  • 1
    So easy
  • 1
    The more the merrier
  • 1
    Easy to work with
  • 1
    For when client needs file without opening firewall
  • 1
    Everybody needs to share and synchronize files reliabl
  • 1
    Easy to use
  • 1
    Official Linux app
  • 0
    The more the merrier
CONS OF DROPBOX
  • 3
    Personal vs company account is confusing
  • 1
    Replication kills CPU and battery

related Dropbox posts

Shared insights
on
Google DriveGoogle DriveDropboxDropbox

I created a simple upload/download functionality for a web application and connected it to Mongo, now I can upload, store and download files. I need advice on how to create a SPA similar to Dropbox or Google Drive in that it will be a hierarchy of folders with files within them, how would I go about creating this structure and adding this functionality to all the files within the application?

Intuitively creating a react component and adding it to a File object seems like the way to go, what are some issues to expect and how do I go about creating such an application to be as fast and UI-friendly as possible?

See more
Shared insights
on
BoxBoxDropboxDropboxKloudlessKloudless

Anyone recommend a good connector like Kloudless for connecting a SaaS app to Dropbox/Box etc? Cheers

See more
Fleeq logo

Fleeq

3
0
Create, share, localize & track customer facing videos & GIFs in minutes
3
0
PROS OF FLEEQ
    Be the first to leave a pro
    CONS OF FLEEQ
      Be the first to leave a con

      related Fleeq posts

      Loom logo

      Loom

      133
      0
      A work communication tool
      133
      0
      PROS OF LOOM
        Be the first to leave a pro
        CONS OF LOOM
          Be the first to leave a con

          related Loom posts

          MySQL logo

          MySQL

          127.2K
          3.8K
          The world's most popular open source database
          127.2K
          3.8K
          PROS OF MYSQL
          • 800
            Sql
          • 679
            Free
          • 562
            Easy
          • 528
            Widely used
          • 490
            Open source
          • 180
            High availability
          • 160
            Cross-platform support
          • 104
            Great community
          • 79
            Secure
          • 75
            Full-text indexing and searching
          • 26
            Fast, open, available
          • 16
            Reliable
          • 16
            SSL support
          • 15
            Robust
          • 9
            Enterprise Version
          • 7
            Easy to set up on all platforms
          • 3
            NoSQL access to JSON data type
          • 1
            Relational database
          • 1
            Easy, light, scalable
          • 1
            Sequel Pro (best SQL GUI)
          • 1
            Replica Support
          CONS OF MYSQL
          • 16
            Owned by a company with their own agenda
          • 3
            Can't roll back schema changes

          related MySQL posts

          Nick Rockwell
          SVP, Engineering at Fastly · | 46 upvotes · 4.4M 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

          Hello, I am building a website for a school that's used by students to find Zoom meeting links, view their marks, and check course materials. It is also used by the teachers to put the meeting links, students' marks, and course materials.

          I created a similar website using HTML, CSS, PHP, and MySQL. Now I want to implement this project using some frameworks: Next.js, ExpressJS and use PostgreSQL instead of MYSQL

          I want to have some advice on whether these are enough to implement my project.

          See more
          PostgreSQL logo

          PostgreSQL

          99.7K
          3.5K
          A powerful, open source object-relational database system
          99.7K
          3.5K
          PROS OF POSTGRESQL
          • 764
            Relational database
          • 510
            High availability
          • 439
            Enterprise class database
          • 383
            Sql
          • 304
            Sql + nosql
          • 173
            Great community
          • 147
            Easy to setup
          • 131
            Heroku
          • 130
            Secure by default
          • 113
            Postgis
          • 50
            Supports Key-Value
          • 48
            Great JSON support
          • 34
            Cross platform
          • 33
            Extensible
          • 28
            Replication
          • 26
            Triggers
          • 23
            Multiversion concurrency control
          • 23
            Rollback
          • 21
            Open source
          • 18
            Heroku Add-on
          • 17
            Stable, Simple and Good Performance
          • 15
            Powerful
          • 13
            Lets be serious, what other SQL DB would you go for?
          • 11
            Good documentation
          • 9
            Scalable
          • 8
            Free
          • 8
            Reliable
          • 8
            Intelligent optimizer
          • 7
            Transactional DDL
          • 7
            Modern
          • 6
            One stop solution for all things sql no matter the os
          • 5
            Relational database with MVCC
          • 5
            Faster Development
          • 4
            Full-Text Search
          • 4
            Developer friendly
          • 3
            Excellent source code
          • 3
            Free version
          • 3
            Great DB for Transactional system or Application
          • 3
            Relational datanbase
          • 3
            search
          • 3
            Open-source
          • 2
            Text
          • 2
            Full-text
          • 1
            Can handle up to petabytes worth of size
          • 1
            Composability
          • 1
            Multiple procedural languages supported
          • 0
            Native
          CONS OF POSTGRESQL
          • 10
            Table/index bloatings

          related PostgreSQL posts

          Simon Reymann
          Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 12.3M 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

          Hello, I am building a website for a school that's used by students to find Zoom meeting links, view their marks, and check course materials. It is also used by the teachers to put the meeting links, students' marks, and course materials.

          I created a similar website using HTML, CSS, PHP, and MySQL. Now I want to implement this project using some frameworks: Next.js, ExpressJS and use PostgreSQL instead of MYSQL

          I want to have some advice on whether these are enough to implement my project.

          See more
          MongoDB logo

          MongoDB

          94.6K
          4.1K
          The database for giant ideas
          94.6K
          4.1K
          PROS OF MONGODB
          • 829
            Document-oriented storage
          • 594
            No sql
          • 554
            Ease of use
          • 465
            Fast
          • 410
            High performance
          • 255
            Free
          • 219
            Open source
          • 180
            Flexible
          • 145
            Replication & high availability
          • 112
            Easy to maintain
          • 42
            Querying
          • 39
            Easy scalability
          • 38
            Auto-sharding
          • 37
            High availability
          • 31
            Map/reduce
          • 27
            Document database
          • 25
            Easy setup
          • 25
            Full index support
          • 16
            Reliable
          • 15
            Fast in-place updates
          • 14
            Agile programming, flexible, fast
          • 12
            No database migrations
          • 8
            Easy integration with Node.Js
          • 8
            Enterprise
          • 6
            Enterprise Support
          • 5
            Great NoSQL DB
          • 4
            Support for many languages through different drivers
          • 3
            Schemaless
          • 3
            Aggregation Framework
          • 3
            Drivers support is good
          • 2
            Fast
          • 2
            Managed service
          • 2
            Easy to Scale
          • 2
            Awesome
          • 2
            Consistent
          • 1
            Good GUI
          • 1
            Acid Compliant
          CONS OF MONGODB
          • 6
            Very slowly for connected models that require joins
          • 3
            Not acid compliant
          • 2
            Proprietary query language

          related MongoDB posts

          Jeyabalaji Subramanian

          Recently we were looking at a few robust and cost-effective ways of replicating the data that resides in our production MongoDB to a PostgreSQL database for data warehousing and business intelligence.

          We set ourselves the following criteria for the optimal tool that would do this job: - The data replication must be near real-time, yet it should NOT impact the production database - The data replication must be horizontally scalable (based on the load), asynchronous & crash-resilient

          Based on the above criteria, we selected the following tools to perform the end to end data replication:

          We chose MongoDB Stitch for picking up the changes in the source database. It is the serverless platform from MongoDB. One of the services offered by MongoDB Stitch is Stitch Triggers. Using stitch triggers, you can execute a serverless function (in Node.js) in real time in response to changes in the database. When there are a lot of database changes, Stitch automatically "feeds forward" these changes through an asynchronous queue.

          We chose Amazon SQS as the pipe / message backbone for communicating the changes from MongoDB to our own replication service. Interestingly enough, MongoDB stitch offers integration with AWS services.

          In the Node.js function, we wrote minimal functionality to communicate the database changes (insert / update / delete / replace) to Amazon SQS.

          Next we wrote a minimal micro-service in Python to listen to the message events on SQS, pickup the data payload & mirror the DB changes on to the target Data warehouse. We implemented source data to target data translation by modelling target table structures through SQLAlchemy . We deployed this micro-service as AWS Lambda with Zappa. With Zappa, deploying your services as event-driven & horizontally scalable Lambda service is dumb-easy.

          In the end, we got to implement a highly scalable near realtime Change Data Replication service that "works" and deployed to production in a matter of few days!

          See more
          Robert Zuber

          We use MongoDB as our primary #datastore. Mongo's approach to replica sets enables some fantastic patterns for operations like maintenance, backups, and #ETL.

          As we pull #microservices from our #monolith, we are taking the opportunity to build them with their own datastores using PostgreSQL. We also use Redis to cache data we’d never store permanently, and to rate-limit our requests to partners’ APIs (like GitHub).

          When we’re dealing with large blobs of immutable data (logs, artifacts, and test results), we store them in Amazon S3. We handle any side-effects of S3’s eventual consistency model within our own code. This ensures that we deal with user requests correctly while writes are in process.

          See more
          Redis logo

          Redis

          60.2K
          3.9K
          Open source (BSD licensed), in-memory data structure store
          60.2K
          3.9K
          PROS OF REDIS
          • 887
            Performance
          • 542
            Super fast
          • 514
            Ease of use
          • 444
            In-memory cache
          • 324
            Advanced key-value cache
          • 194
            Open source
          • 182
            Easy to deploy
          • 165
            Stable
          • 156
            Free
          • 121
            Fast
          • 42
            High-Performance
          • 40
            High Availability
          • 35
            Data Structures
          • 32
            Very Scalable
          • 24
            Replication
          • 23
            Pub/Sub
          • 22
            Great community
          • 19
            "NoSQL" key-value data store
          • 16
            Hashes
          • 13
            Sets
          • 11
            Sorted Sets
          • 10
            Lists
          • 10
            NoSQL
          • 9
            Async replication
          • 9
            BSD licensed
          • 8
            Integrates super easy with Sidekiq for Rails background
          • 8
            Bitmaps
          • 7
            Open Source
          • 7
            Keys with a limited time-to-live
          • 6
            Lua scripting
          • 6
            Strings
          • 5
            Awesomeness for Free
          • 5
            Hyperloglogs
          • 4
            Runs server side LUA
          • 4
            Transactions
          • 4
            Networked
          • 4
            Outstanding performance
          • 4
            Feature Rich
          • 4
            Written in ANSI C
          • 4
            LRU eviction of keys
          • 3
            Data structure server
          • 3
            Performance & ease of use
          • 2
            Temporarily kept on disk
          • 2
            Dont save data if no subscribers are found
          • 2
            Automatic failover
          • 2
            Easy to use
          • 2
            Scalable
          • 2
            Channels concept
          • 2
            Object [key/value] size each 500 MB
          • 2
            Existing Laravel Integration
          • 2
            Simple
          CONS OF REDIS
          • 15
            Cannot query objects directly
          • 3
            No secondary indexes for non-numeric data types
          • 1
            No WAL

          related Redis posts

          Russel Werner
          Lead Engineer at StackShare · | 32 upvotes · 2.9M views

          StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.

          Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!

          #StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit

          See more
          Simon Reymann
          Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 12.3M 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
          Amazon S3 logo

          Amazon S3

          53.8K
          2K
          Store and retrieve any amount of data, at any time, from anywhere on the web
          53.8K
          2K
          PROS OF AMAZON S3
          • 590
            Reliable
          • 492
            Scalable
          • 456
            Cheap
          • 329
            Simple & easy
          • 83
            Many sdks
          • 30
            Logical
          • 13
            Easy Setup
          • 11
            REST API
          • 11
            1000+ POPs
          • 6
            Secure
          • 4
            Easy
          • 4
            Plug and play
          • 3
            Web UI for uploading files
          • 2
            Faster on response
          • 2
            Flexible
          • 2
            GDPR ready
          • 1
            Easy to use
          • 1
            Plug-gable
          • 1
            Easy integration with CloudFront
          CONS OF AMAZON S3
          • 7
            Permissions take some time to get right
          • 6
            Requires a credit card
          • 6
            Takes time/work to organize buckets & folders properly
          • 3
            Complex to set up

          related Amazon S3 posts

          Ashish Singh
          Tech Lead, Big Data Platform at Pinterest · | 38 upvotes · 3.7M 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
          Russel Werner
          Lead Engineer at StackShare · | 32 upvotes · 2.9M views

          StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.

          Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!

          #StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit

          See more