Alternatives to Seafile logo

Alternatives to Seafile

Nextcloud, ownCloud, Dropbox, Syncthing, and OneDrive are the most popular alternatives and competitors to Seafile.
29
45
+ 1
2

What is Seafile and what are its top alternatives?

A file syncing and collaboration platform for enterprise. It provides Dropbox like file syncing. It also comes with rich collaboration features, includes file preview, discussion, wiki. The goal is to help customers to build an unified and easy-to-use file management platform behind their firewalls.
Seafile is a tool in the File Storage category of a tech stack.
Seafile is an open source tool with 11.9K GitHub stars and 1.5K GitHub forks. Here’s a link to Seafile's open source repository on GitHub

Top Alternatives to Seafile

  • Nextcloud
    Nextcloud

    A suite of client-server software for creating and using file hosting services The most deployed self-hosted file share and collaboration platform on the web. Access & collaborate across your devices. ...

  • ownCloud
    ownCloud

    It is an open source, self-hosted file sync and share app platform. Access & sync your files, contacts, calendars & bookmarks across your devices. You decide what happens with your data, where it is and who can access it. ...

  • Dropbox
    Dropbox

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

  • Syncthing
    Syncthing

    It is a continuous file synchronization program. It synchronizes files between two or more computers and replaces proprietary sync and cloud services with something open, trustworthy and decentralized. Your data is your data alone and you deserve to choose where it is stored, if it is shared with some third party and how it's transmitted over the internet. ...

  • OneDrive
    OneDrive

    Outlook.com is a free, personal email service from Microsoft. Keep your inbox clutter-free with powerful organizational tools, and collaborate easily with OneDrive and Office Online integration. ...

  • JavaScript
    JavaScript

    JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles. ...

  • Git
    Git

    Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. ...

  • GitHub
    GitHub

    GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together. ...

Seafile alternatives & related posts

Nextcloud logo

Nextcloud

264
188
12
A self-hosted productivity platform that keeps you in control
264
188
+ 1
12
PROS OF NEXTCLOUD
  • 5
    Free
  • 4
    Synchronous with all devices
  • 3
    Simplistic
CONS OF NEXTCLOUD
    Be the first to leave a con

    related Nextcloud posts

    Joshua Dean Küpper
    CEO at Scrayos UG (haftungsbeschränkt) · | 3 upvotes · 173.1K views

    We use Nextcloud for company-file-management, personal work-documents and for collaborative work (through collabora), organize our #TODOs, that are not covered by the Bugtracker. Existing solutions either were very expensive ( Google Drive ), missed a lot of features ( Trello ) or were pretty much overloaded with features ( Wekan within Sandstorm ).

    That made Nextcloud ud our natural fit for our company management and we're convinced of its integrations and flexibility.

    See more
    ownCloud logo

    ownCloud

    51
    53
    3
    Open source self-hosted web apps with sync clients and sharing
    51
    53
    + 1
    3
    PROS OF OWNCLOUD
    • 1
      Open source
    • 1
      GDPR compliant
    • 1
      Self hosted
    CONS OF OWNCLOUD
      Be the first to leave a con

      related ownCloud posts

      Dropbox logo

      Dropbox

      23.2K
      18.1K
      1.7K
      Build the power of Dropbox into your apps
      23.2K
      18.1K
      + 1
      1.7K
      PROS OF DROPBOX
      • 434
        Easy to work with
      • 256
        Free
      • 216
        Popular
      • 176
        Shared file hosting
      • 167
        'just works'
      • 100
        No brainer
      • 79
        Integration with external services
      • 76
        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
        Reliable
      • 3
        Sync API
      • 3
        Mac app
      • 3
        Cross platform app
      • 2
        Ability to pay monthly without losing your files
      • 2
        Delta synchronization
      • 2
        Everybody needs to share and synchronize files reliably
      • 2
        Backups, local and cloud
      • 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
      Jason Barry
      Cofounder at FeaturePeek · | 4 upvotes · 2.4M views

      We've tried a couple REST clients over the years, and Insomnia REST Client has won us over the most. Here's what we like about it compared to other contenders in this category:

      • Uncluttered UI. Things are only in your face when you need them, and the app is visually organized in an intuitive manner.
      • Native Mac app. We wanted the look and feel to be on par with other apps in our OS rather than a web app / Electron app (cough Postman).
      • Easy team sync. Other apps have this too, but Insomnia's model best sets the "set and forget" mentality. Syncs are near instant and I'm always assured that I'm working on the latest version of API endpoints. Apps like Paw use a git-based approach to revision history, but I think this actually over-complicates the sync feature. For ensuring I'm always working on the latest version of something, I'd rather have the sync model be closer to Dropbox's than git's, and Insomnia is closer to Dropbox in that regard.

      Some features like automatic public-facing documentation aren't supported, but we currently don't have any public APIs, so this didn't matter to us.

      See more
      Syncthing logo

      Syncthing

      45
      74
      2
      Open Source Continuous File Synchronization
      45
      74
      + 1
      2
      PROS OF SYNCTHING
      • 1
        Convenient to use
      • 1
        Offline
      CONS OF SYNCTHING
      • 1
        Not intuitive how to set up on a headless machine

      related Syncthing posts

      OneDrive logo

      OneDrive

      285
      191
      6
      Save your files and photos to OneDrive and get them from any device, anywhere
      285
      191
      + 1
      6
      PROS OF ONEDRIVE
      • 2
        FREE
      • 2
        Simple
      • 1
        Back up
      • 1
        Stable service
      CONS OF ONEDRIVE
        Be the first to leave a con

        related OneDrive posts

        JavaScript logo

        JavaScript

        354.5K
        269.5K
        8.1K
        Lightweight, interpreted, object-oriented language with first-class functions
        354.5K
        269.5K
        + 1
        8.1K
        PROS OF JAVASCRIPT
        • 1.7K
          Can be used on frontend/backend
        • 1.5K
          It's everywhere
        • 1.2K
          Lots of great frameworks
        • 897
          Fast
        • 745
          Light weight
        • 425
          Flexible
        • 392
          You can't get a device today that doesn't run js
        • 286
          Non-blocking i/o
        • 237
          Ubiquitousness
        • 191
          Expressive
        • 55
          Extended functionality to web pages
        • 49
          Relatively easy language
        • 46
          Executed on the client side
        • 30
          Relatively fast to the end user
        • 25
          Pure Javascript
        • 21
          Functional programming
        • 15
          Async
        • 13
          Full-stack
        • 12
          Setup is easy
        • 12
          Future Language of The Web
        • 12
          Its everywhere
        • 11
          Because I love functions
        • 11
          JavaScript is the New PHP
        • 10
          Like it or not, JS is part of the web standard
        • 9
          Expansive community
        • 9
          Everyone use it
        • 9
          Can be used in backend, frontend and DB
        • 9
          Easy
        • 8
          Most Popular Language in the World
        • 8
          Powerful
        • 8
          Can be used both as frontend and backend as well
        • 8
          For the good parts
        • 8
          No need to use PHP
        • 8
          Easy to hire developers
        • 7
          Agile, packages simple to use
        • 7
          Love-hate relationship
        • 7
          Photoshop has 3 JS runtimes built in
        • 7
          Evolution of C
        • 7
          It's fun
        • 7
          Hard not to use
        • 7
          Versitile
        • 7
          Its fun and fast
        • 7
          Nice
        • 7
          Popularized Class-Less Architecture & Lambdas
        • 7
          Supports lambdas and closures
        • 6
          It let's me use Babel & Typescript
        • 6
          Can be used on frontend/backend/Mobile/create PRO Ui
        • 6
          1.6K Can be used on frontend/backend
        • 6
          Client side JS uses the visitors CPU to save Server Res
        • 6
          Easy to make something
        • 5
          Clojurescript
        • 5
          Promise relationship
        • 5
          Stockholm Syndrome
        • 5
          Function expressions are useful for callbacks
        • 5
          Scope manipulation
        • 5
          Everywhere
        • 5
          Client processing
        • 5
          What to add
        • 4
          Because it is so simple and lightweight
        • 4
          Only Programming language on browser
        • 1
          Test
        • 1
          Hard to learn
        • 1
          Test2
        • 1
          Not the best
        • 1
          Easy to understand
        • 1
          Subskill #4
        • 1
          Easy to learn
        • 0
          Hard 彤
        CONS OF JAVASCRIPT
        • 22
          A constant moving target, too much churn
        • 20
          Horribly inconsistent
        • 15
          Javascript is the New PHP
        • 9
          No ability to monitor memory utilitization
        • 8
          Shows Zero output in case of ANY error
        • 7
          Thinks strange results are better than errors
        • 6
          Can be ugly
        • 3
          No GitHub
        • 2
          Slow
        • 0
          HORRIBLE DOCUMENTS, faulty code, repo has bugs

        related JavaScript posts

        Zach Holman

        Oof. I have truly hated JavaScript for a long time. Like, for over twenty years now. Like, since the Clinton administration. It's always been a nightmare to deal with all of the aspects of that silly language.

        But wowza, things have changed. Tooling is just way, way better. I'm primarily web-oriented, and using React and Apollo together the past few years really opened my eyes to building rich apps. And I deeply apologize for using the phrase rich apps; I don't think I've ever said such Enterprisey words before.

        But yeah, things are different now. I still love Rails, and still use it for a lot of apps I build. But it's that silly rich apps phrase that's the problem. Users have way more comprehensive expectations than they did even five years ago, and the JS community does a good job at building tools and tech that tackle the problems of making heavy, complicated UI and frontend work.

        Obviously there's a lot of things happening here, so just saying "JavaScript isn't terrible" might encompass a huge amount of libraries and frameworks. But if you're like me, yeah, give things another shot- I'm somehow not hating on JavaScript anymore and... gulp... I kinda love it.

        See more
        Conor Myhrvold
        Tech Brand Mgr, Office of CTO at Uber · | 44 upvotes · 11.2M views

        How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

        Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

        Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

        https://eng.uber.com/distributed-tracing/

        (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

        Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

        See more
        Git logo

        Git

        293.6K
        175.7K
        6.6K
        Fast, scalable, distributed revision control system
        293.6K
        175.7K
        + 1
        6.6K
        PROS OF GIT
        • 1.4K
          Distributed version control system
        • 1.1K
          Efficient branching and merging
        • 959
          Fast
        • 845
          Open source
        • 726
          Better than svn
        • 368
          Great command-line application
        • 306
          Simple
        • 291
          Free
        • 232
          Easy to use
        • 222
          Does not require server
        • 27
          Distributed
        • 22
          Small & Fast
        • 18
          Feature based workflow
        • 15
          Staging Area
        • 13
          Most wide-spread VSC
        • 11
          Role-based codelines
        • 11
          Disposable Experimentation
        • 7
          Frictionless Context Switching
        • 6
          Data Assurance
        • 5
          Efficient
        • 4
          Just awesome
        • 3
          Github integration
        • 3
          Easy branching and merging
        • 2
          Compatible
        • 2
          Flexible
        • 2
          Possible to lose history and commits
        • 1
          Rebase supported natively; reflog; access to plumbing
        • 1
          Light
        • 1
          Team Integration
        • 1
          Fast, scalable, distributed revision control system
        • 1
          Easy
        • 1
          Flexible, easy, Safe, and fast
        • 1
          CLI is great, but the GUI tools are awesome
        • 1
          It's what you do
        • 0
          Phinx
        CONS OF GIT
        • 16
          Hard to learn
        • 11
          Inconsistent command line interface
        • 9
          Easy to lose uncommitted work
        • 7
          Worst documentation ever possibly made
        • 5
          Awful merge handling
        • 3
          Unexistent preventive security flows
        • 3
          Rebase hell
        • 2
          When --force is disabled, cannot rebase
        • 2
          Ironically even die-hard supporters screw up badly
        • 1
          Doesn't scale for big data

        related Git posts

        Simon Reymann
        Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 9.9M 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
        Tymoteusz Paul
        Devops guy at X20X Development LTD · | 23 upvotes · 8.9M views

        Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

        It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

        I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

        We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

        If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

        The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

        Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

        See more
        GitHub logo

        GitHub

        281.6K
        245.9K
        10.3K
        Powerful collaboration, review, and code management for open source and private development projects
        281.6K
        245.9K
        + 1
        10.3K
        PROS OF GITHUB
        • 1.8K
          Open source friendly
        • 1.5K
          Easy source control
        • 1.3K
          Nice UI
        • 1.1K
          Great for team collaboration
        • 867
          Easy setup
        • 504
          Issue tracker
        • 486
          Great community
        • 483
          Remote team collaboration
        • 451
          Great way to share
        • 442
          Pull request and features planning
        • 147
          Just works
        • 132
          Integrated in many tools
        • 121
          Free Public Repos
        • 116
          Github Gists
        • 112
          Github pages
        • 83
          Easy to find repos
        • 62
          Open source
        • 60
          It's free
        • 60
          Easy to find projects
        • 56
          Network effect
        • 49
          Extensive API
        • 43
          Organizations
        • 42
          Branching
        • 34
          Developer Profiles
        • 32
          Git Powered Wikis
        • 30
          Great for collaboration
        • 24
          It's fun
        • 23
          Clean interface and good integrations
        • 22
          Community SDK involvement
        • 20
          Learn from others source code
        • 16
          Because: Git
        • 14
          It integrates directly with Azure
        • 10
          Standard in Open Source collab
        • 10
          Newsfeed
        • 8
          It integrates directly with Hipchat
        • 8
          Fast
        • 8
          Beautiful user experience
        • 7
          Easy to discover new code libraries
        • 6
          Smooth integration
        • 6
          Cloud SCM
        • 6
          Nice API
        • 6
          Graphs
        • 6
          Integrations
        • 6
          It's awesome
        • 5
          Quick Onboarding
        • 5
          Reliable
        • 5
          Remarkable uptime
        • 5
          CI Integration
        • 5
          Hands down best online Git service available
        • 4
          Uses GIT
        • 4
          Version Control
        • 4
          Simple but powerful
        • 4
          Unlimited Public Repos at no cost
        • 4
          Free HTML hosting
        • 4
          Security options
        • 4
          Loved by developers
        • 4
          Easy to use and collaborate with others
        • 3
          Ci
        • 3
          IAM
        • 3
          Nice to use
        • 3
          Easy deployment via SSH
        • 2
          Easy to use
        • 2
          Leads the copycats
        • 2
          All in one development service
        • 2
          Free private repos
        • 2
          Free HTML hostings
        • 2
          Easy and efficient maintainance of the projects
        • 2
          Beautiful
        • 2
          Easy source control and everything is backed up
        • 2
          IAM integration
        • 2
          Very Easy to Use
        • 2
          Good tools support
        • 2
          Issues tracker
        • 2
          Never dethroned
        • 2
          Self Hosted
        • 1
          Dasf
        • 1
          Profound
        CONS OF GITHUB
        • 54
          Owned by micrcosoft
        • 38
          Expensive for lone developers that want private repos
        • 15
          Relatively slow product/feature release cadence
        • 10
          API scoping could be better
        • 9
          Only 3 collaborators for private repos
        • 4
          Limited featureset for issue management
        • 3
          Does not have a graph for showing history like git lens
        • 2
          GitHub Packages does not support SNAPSHOT versions
        • 1
          No multilingual interface
        • 1
          Takes a long time to commit
        • 1
          Expensive

        related GitHub posts

        Johnny Bell

        I was building a personal project that I needed to store items in a real time database. I am more comfortable with my Frontend skills than my backend so I didn't want to spend time building out anything in Ruby or Go.

        I stumbled on Firebase by #Google, and it was really all I needed. It had realtime data, an area for storing file uploads and best of all for the amount of data I needed it was free!

        I built out my application using tools I was familiar with, React for the framework, Redux.js to manage my state across components, and styled-components for the styling.

        Now as this was a project I was just working on in my free time for fun I didn't really want to pay for hosting. I did some research and I found Netlify. I had actually seen them at #ReactRally the year before and deployed a Gatsby site to Netlify already.

        Netlify was very easy to setup and link to my GitHub account you select a repo and pretty much with very little configuration you have a live site that will deploy every time you push to master.

        With the selection of these tools I was able to build out my application, connect it to a realtime database, and deploy to a live environment all with $0 spent.

        If you're looking to build out a small app I suggest giving these tools a go as you can get your idea out into the real world for absolutely no cost.

        See more

        Context: I wanted to create an end to end IoT data pipeline simulation in Google Cloud IoT Core and other GCP services. I never touched Terraform meaningfully until working on this project, and it's one of the best explorations in my development career. The documentation and syntax is incredibly human-readable and friendly. I'm used to building infrastructure through the google apis via Python , but I'm so glad past Sung did not make that decision. I was tempted to use Google Cloud Deployment Manager, but the templates were a bit convoluted by first impression. I'm glad past Sung did not make this decision either.

        Solution: Leveraging Google Cloud Build Google Cloud Run Google Cloud Bigtable Google BigQuery Google Cloud Storage Google Compute Engine along with some other fun tools, I can deploy over 40 GCP resources using Terraform!

        Check Out My Architecture: CLICK ME

        Check out the GitHub repo attached

        See more