Alternatives to Cloudflare Workers logo

Alternatives to Cloudflare Workers

Fastly, AWS Lambda, Netlify, Azure Functions, and Firebase are the most popular alternatives and competitors to Cloudflare Workers.
94
82
+ 1
0

What is Cloudflare Workers and what are its top alternatives?

Build serverless applications on Cloudflare's global cloud network of 165 data centers. It provides a lightweight JavaScript execution environment that allows developers to augment existing applications or create entirely new ones without configuring or maintaining infrastructure.
Cloudflare Workers is a tool in the Serverless / Task Processing category of a tech stack.

Top Alternatives to Cloudflare Workers

  • Fastly
    Fastly

    Fastly's real-time content delivery network gives you total control over your content, unprecedented access to performance analytics, and the ability to instantly update content in 150 milliseconds. ...

  • AWS Lambda
    AWS Lambda

    AWS Lambda is a compute service that runs your code in response to events and automatically manages the underlying compute resources for you. You can use AWS Lambda to extend other AWS services with custom logic, or create your own back-end services that operate at AWS scale, performance, and security. ...

  • Netlify
    Netlify

    Netlify is smart enough to process your site and make sure all assets gets optimized and served with perfect caching-headers from a cookie-less domain. We make sure your HTML is served straight from our CDN edge nodes without any round-trip to our backend servers and are the only ones to give you instant cache invalidation when you push a new deploy. Netlify is also the only static hosting service with integrated continuous deployment. ...

  • Azure Functions
    Azure Functions

    Azure Functions is an event driven, compute-on-demand experience that extends the existing Azure application platform with capabilities to implement code triggered by events occurring in virtually any Azure or 3rd party service as well as on-premises systems. ...

  • 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. ...

  • Serverless
    Serverless

    Build applications comprised of microservices that run in response to events, auto-scale for you, and only charge you when they run. This lowers the total cost of maintaining your apps, enabling you to build more logic, faster. The Framework uses new event-driven compute services, like AWS Lambda, Google CloudFunctions, and more. ...

  • Cloud Functions for Firebase
    Cloud Functions for Firebase

    Cloud Functions for Firebase lets you create functions that are triggered by Firebase products, such as changes to data in the Realtime Database, uploads to Cloud Storage, new user sign ups via Authentication, and conversion events in Analytics. ...

  • Google Cloud Functions
    Google Cloud Functions

    Construct applications from bite-sized business logic billed to the nearest 100 milliseconds, only while your code is running ...

Cloudflare Workers alternatives & related posts

Fastly logo

Fastly

1K
474
137
We're redefining content delivery.
1K
474
+ 1
137
PROS OF FASTLY
  • 27
    Real-time updates
  • 23
    Fastest CDN
  • 20
    Powerful API
  • 19
    Great support
  • 13
    Great customer support
  • 6
    Instant Purging
  • 6
    Custom VCL
  • 5
    Good pricing
  • 5
    Tag-based Purging
  • 4
    HTTP/2 Support
  • 3
    Speed & functionality
  • 3
    Image processing on demande (Fastly IO)
  • 3
    Best CDN
CONS OF FASTLY
  • 1
    Minimum $50/mo spend

related Fastly posts

Justin Dorfman
Open Source Program Manager at Reblaze · | 4 upvotes · 197.7K views

When my SSL cert MaxCDN was expiring on my personal site I decided it was a good time to revamp some things. Since GitHub Services is depreciated I can no longer have #CDN cache purges automated among other things. So I decided on the following: GitHub Pages, Netlify, Let's Encrypt and Jekyll. Staying the same was Bootstrap, jQuery, Grunt & #GoogleFonts.

What's awesome about GitHub Pages is that it has a #CDN (Fastly) built-in and anytime you push to master, it purges the cache instantaneously without you have to do anything special. Netlify is magic, I highly recommend it to anyone using #StaticSiteGenerators.

For the most part, everything went smoothly. The only things I had issues with were the following:

  • If you want to point www to GitHub Pages you need to rename the repo to www
  • If you edit something in the _config.yml you need to restart bundle exec jekyll s or changes won't show
  • I had to disable the Grunt htmlmin module. I replaced it with Jekyll layout that compresses HTML for #webperf

Last but certainly not least, I made a donation to Let's Encrypt. If you use their service consider doing it too: https://letsencrypt.org/donate/

See more
AWS Lambda logo

AWS Lambda

19.3K
14.4K
425
Automatically run code in response to modifications to objects in Amazon S3 buckets, messages in Kinesis streams, or...
19.3K
14.4K
+ 1
425
PROS OF AWS LAMBDA
  • 128
    No infrastructure
  • 82
    Cheap
  • 69
    Quick
  • 58
    Stateless
  • 47
    No deploy, no server, great sleep
  • 9
    AWS Lambda went down taking many sites with it
  • 6
    Easy to deploy
  • 6
    Extensive API
  • 6
    Auto scale and cost effective
  • 6
    Event Driven Governance
  • 5
    VPC Support
  • 3
    Integrated with various AWS services
CONS OF AWS LAMBDA
  • 5
    Cant execute ruby or go
  • 1
    Compute time limited
  • 0
    Can't execute PHP w/o significant effort

related AWS Lambda 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
Tim Nolet

Heroku Docker GitHub Node.js hapi Vue.js AWS Lambda Amazon S3 PostgreSQL Knex.js Checkly is a fairly young company and we're still working hard to find the correct mix of product features, price and audience.

We are focussed on tech B2B, but I always wanted to serve solo developers too. So I decided to make a $7 plan.

Why $7? Simply put, it seems to be a sweet spot for tech companies: Heroku, Docker, Github, Appoptics (Librato) all offer $7 plans. They must have done a ton of research into this, so why not piggy back that and try it out.

Enough biz talk, onto tech. The challenges were:

  • Slice of a portion of the functionality so a $7 plan is still profitable. We call this the "plan limits"
  • Update API and back end services to handle and enforce plan limits.
  • Update the UI to kindly state plan limits are in effect on some part of the UI.
  • Update the pricing page to reflect all changes.
  • Keep the actual processing backend, storage and API's as untouched as possible.

In essence, we went from strictly volume based pricing to value based pricing. Here come the technical steps & decisions we made to get there.

  1. We updated our PostgreSQL schema so plans now have an array of "features". These are string constants that represent feature toggles.
  2. The Vue.js frontend reads these from the vuex store on login.
  3. Based on these values, the UI has simple v-if statements to either just show the feature or show a friendly "please upgrade" button.
  4. The hapi API has a hook on each relevant API endpoint that checks whether a user's plan has the feature enabled, or not.

Side note: We offer 10 SMS messages per month on the developer plan. However, we were not actually counting how many people were sending. We had to update our alerting daemon (that runs on Heroku and triggers SMS messages via AWS SNS) to actually bump a counter.

What we build is basically feature-toggling based on plan features. It is very extensible for future additions. Our scheduling and storage backend that actually runs users' monitoring requests (AWS Lambda) and stores the results (S3 and Postgres) has no knowledge of all of this and remained unchanged.

Hope this helps anyone building out their SaaS and is in a similar situation.

See more
Netlify logo

Netlify

2.5K
1.8K
196
Build, deploy and host your static site or app with a drag and drop interface and automatic delpoys...
2.5K
1.8K
+ 1
196
PROS OF NETLIFY
  • 43
    Easy deploy
  • 42
    Fastest static hosting and continuous deployments
  • 21
    Super simple deploys
  • 21
    Free SSL support
  • 15
    Easy Setup and Continous deployments
  • 9
    Free plan for personal websites
  • 9
    Faster than any other option in the market
  • 7
    Deploy previews
  • 6
    Free Open Source (Pro) plan
  • 4
    Easy to use and great support
  • 4
    Analytics
  • 4
    Great loop-in material on a blog
  • 3
    Great drag and drop functionality
  • 3
    Fastest static hosting and continuous deployments
  • 2
    Custom domains support
  • 1
    Canary Releases (Split Tests)
  • 1
    Tech oriented support
  • 1
    Supports static site generators
CONS OF NETLIFY
  • 7
    It's expensive
  • 1
    Bandwidth limitation

related Netlify 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
Stephen Gheysens
Senior Solutions Engineer at Twilio · | 14 upvotes · 616.2K 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
Azure Functions logo

Azure Functions

526
574
43
Listen and react to events across your stack
526
574
+ 1
43
PROS OF AZURE FUNCTIONS
  • 12
    Pay only when invoked
  • 9
    Great developer experience for C#
  • 6
    Multiple languages supported
  • 5
    Great debugging support
  • 3
    Can be used as lightweight https service
  • 2
    Poor developer experience for C#
  • 2
    Easy scalability
  • 1
    WebHooks
  • 1
    Azure component events for Storage, services etc
  • 1
    Event driven
  • 1
    Costo
CONS OF AZURE FUNCTIONS
  • 1
    No persistent (writable) file system available
  • 1
    Poor support for Linux environments
  • 1
    Sporadic server & language runtime issues
  • 1
    Not suited for long-running applications

related Azure Functions posts

Kestas Barzdaitis
Entrepreneur & Engineer · | 16 upvotes · 495.8K views

CodeFactor being a #SAAS product, our goal was to run on a cloud-native infrastructure since day one. We wanted to stay product focused, rather than having to work on the infrastructure that supports the application. We needed a cloud-hosting provider that would be reliable, economical and most efficient for our product.

CodeFactor.io aims to provide an automated and frictionless code review service for software developers. That requires agility, instant provisioning, autoscaling, security, availability and compliance management features. We looked at the top three #IAAS providers that take up the majority of market share: Amazon's Amazon EC2 , Microsoft's Microsoft Azure, and Google Compute Engine.

AWS has been available since 2006 and has developed the most extensive services ant tools variety at a massive scale. Azure and GCP are about half the AWS age, but also satisfied our technical requirements.

It is worth noting that even though all three providers support Docker containerization services, GCP has the most robust offering due to their investments in Kubernetes. Also, if you are a Microsoft shop, and develop in .NET - Visual Studio Azure shines at integration there and all your existing .NET code works seamlessly on Azure. All three providers have serverless computing offerings (AWS Lambda, Azure Functions, and Google Cloud Functions). Additionally, all three providers have machine learning tools, but GCP appears to be the most developer-friendly, intuitive and complete when it comes to #Machinelearning and #AI.

The prices between providers are competitive across the board. For our requirements, AWS would have been the most expensive, GCP the least expensive and Azure was in the middle. Plus, if you #Autoscale frequently with large deltas, note that Azure and GCP have per minute billing, where AWS bills you per hour. We also applied for the #Startup programs with all three providers, and this is where Azure shined. While AWS and GCP for startups would have covered us for about one year of infrastructure costs, Azure Sponsorship would cover about two years of CodeFactor's hosting costs. Moreover, Azure Team was terrific - I felt that they wanted to work with us where for AWS and GCP we were just another startup.

In summary, we were leaning towards GCP. GCP's advantages in containerization, automation toolset, #Devops mindset, and pricing were the driving factors there. Nevertheless, we could not say no to Azure's financial incentives and a strong sense of partnership and support throughout the process.

Bottom line is, IAAS offerings with AWS, Azure, and GCP are evolving fast. At CodeFactor, we aim to be platform agnostic where it is practical and retain the flexibility to cherry-pick the best products across providers.

See more
Michal Nowak

In a couple of recent projects we had an opportunity to try out the new Serverless approach to building web applications. It wasn't necessarily a question if we should use any particular vendor but rather "if" we can consider serverless a viable option for building apps. Obviously our goal was also to get a feel for this technology and gain some hands-on experience.

We did consider AWS Lambda, Firebase from Google as well as Azure Functions. Eventually we went with AWS Lambdas.

PROS
  • No servers to manage (obviously!)
  • Limited fixed costs – you pay only for used time
  • Automated scaling and balancing
  • Automatic failover (or, at this level of abstraction, no failover problem at all)
  • Security easier to provide and audit
  • Low overhead at the start (with the certain level of knowledge)
  • Short time to market
  • Easy handover - deployment coupled with code
  • Perfect choice for lean startups with fast-paced iterations
  • Augmentation for the classic cloud, server(full) approach
CONS
  • Not much know-how and best practices available about structuring the code and projects on the market
  • Not suitable for complex business logic due to the risk of producing highly coupled code
  • Cost difficult to estimate (helpful tools: serverlesscalc.com)
  • Difficulty in migration to other platforms (Vendor lock⚠️)
  • Little engineers with experience in serverless on the job market
  • Steep learning curve for engineers without any cloud experience

More details are on our blog: https://evojam.com/blog/2018/12/5/should-you-go-serverless-meet-the-benefits-and-flaws-of-new-wave-of-cloud-solutions I hope it helps 🙌 & I'm curious of your experiences.

See more
Firebase logo

Firebase

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

related Firebase posts

Stephen Gheysens
Senior Solutions Engineer at Twilio · | 14 upvotes · 616.2K 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
Tassanai Singprom

This is my stack in Application & Data

JavaScript PHP HTML5 jQuery Redis Amazon EC2 Ubuntu Sass Vue.js Firebase Laravel Lumen Amazon RDS GraphQL MariaDB

My Utilities Tools

Google Analytics Postman Elasticsearch

My Devops Tools

Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack

My Business Tools

Slack

See more
Serverless logo

Serverless

1.4K
1.1K
23
The most widely-adopted toolkit for building serverless applications
1.4K
1.1K
+ 1
23
PROS OF SERVERLESS
  • 12
    API integration
  • 7
    Supports cloud functions for Google, Azure, and IBM
  • 2
    Lower cost
  • 1
    Openwhisk
  • 1
    Auto scale
CONS OF SERVERLESS
    Be the first to leave a con

    related Serverless posts

    Praveen Mooli
    Engineering Manager at Taylor and Francis · | 17 upvotes · 2.3M views

    We are in the process of building a modern content platform to deliver our content through various channels. We decided to go with Microservices architecture as we wanted scale. Microservice architecture style is an approach to developing an application as a suite of small independently deployable services built around specific business capabilities. You can gain modularity, extensive parallelism and cost-effective scaling by deploying services across many distributed servers. Microservices modularity facilitates independent updates/deployments, and helps to avoid single point of failure, which can help prevent large-scale outages. We also decided to use Event Driven Architecture pattern which is a popular distributed asynchronous architecture pattern used to produce highly scalable applications. The event-driven architecture is made up of highly decoupled, single-purpose event processing components that asynchronously receive and process events.

    To build our #Backend capabilities we decided to use the following: 1. #Microservices - Java with Spring Boot , Node.js with ExpressJS and Python with Flask 2. #Eventsourcingframework - Amazon Kinesis , Amazon Kinesis Firehose , Amazon SNS , Amazon SQS, AWS Lambda 3. #Data - Amazon RDS , Amazon DynamoDB , Amazon S3 , MongoDB Atlas

    To build #Webapps we decided to use Angular 2 with RxJS

    #Devops - GitHub , Travis CI , Terraform , Docker , Serverless

    See more
    Nitzan Shapira

    At Epsagon, we use hundreds of AWS Lambda functions, most of them are written in Python, and the Serverless Framework to pack and deploy them. One of the issues we've encountered is the difficulty to package external libraries into the Lambda environment using the Serverless Framework. This limitation is probably by design since the external code your Lambda needs can be usually included with a package manager.

    In order to overcome this issue, we've developed a tool, which we also published as open-source (see link below), which automatically packs these libraries using a simple npm package and a YAML configuration file. Support for Node.js, Go, and Java will be available soon.

    The GitHub respoitory: https://github.com/epsagon/serverless-package-external

    See more
    Cloud Functions for Firebase logo

    Cloud Functions for Firebase

    433
    359
    6
    Run your mobile backend code without managing servers
    433
    359
    + 1
    6
    PROS OF CLOUD FUNCTIONS FOR FIREBASE
    • 4
      Up and running
    • 1
      Multi-region
    • 1
      Affordable
    CONS OF CLOUD FUNCTIONS FOR FIREBASE
      Be the first to leave a con

      related Cloud Functions for Firebase posts

      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
      Aliadoc Team

      In #Aliadoc, we're exploring the crowdfunding option to get traction before launch. We are building a SaaS platform for website design customization.

      For the Admin UI and website editor we use React and we're currently transitioning from a Create React App setup to a custom one because our needs have become more specific. We use CloudFlare as much as possible, it's a great service.

      For routing dynamic resources and proxy tasks to feed websites to the editor we leverage CloudFlare Workers for improved responsiveness. We use Firebase for our hosting needs and user authentication while also using several Cloud Functions for Firebase to interact with other services along with Google App Engine and Google Cloud Storage, but also the Real Time Database is on the radar for collaborative website editing.

      We generally hate configuration but honestly because of the stage of our project we lack resources for doing heavy sysops work. So we are basically just relying on Serverless technologies as much as we can to do all server side processing.

      Visual Studio Code definitively makes programming a much easier and enjoyable task, we just love it. We combine it with Bitbucket for our source code control needs.

      See more
      Google Cloud Functions logo

      Google Cloud Functions

      429
      417
      20
      A serverless environment to build and connect cloud services
      429
      417
      + 1
      20
      PROS OF GOOGLE CLOUD FUNCTIONS
      • 6
        Serverless Applications
      • 4
        Its not AWS
      • 3
        Simplicity
      • 2
        Free Tiers and Trainging
      • 1
        Simple config with GitLab CI/CD
      • 1
        Customer Support
      • 1
        Typescript Support
      • 1
        Blaze, pay as you go
      • 1
        Built-in Webhook trigger
      CONS OF GOOGLE CLOUD FUNCTIONS
      • 1
        Node.js only
      • 0
        Typescript Support
      • 0
        Blaze, pay as you go
      • 0
        Simple config with GitLab CI/CD

      related Google Cloud Functions posts

      Kestas Barzdaitis
      Entrepreneur & Engineer · | 16 upvotes · 495.8K views

      CodeFactor being a #SAAS product, our goal was to run on a cloud-native infrastructure since day one. We wanted to stay product focused, rather than having to work on the infrastructure that supports the application. We needed a cloud-hosting provider that would be reliable, economical and most efficient for our product.

      CodeFactor.io aims to provide an automated and frictionless code review service for software developers. That requires agility, instant provisioning, autoscaling, security, availability and compliance management features. We looked at the top three #IAAS providers that take up the majority of market share: Amazon's Amazon EC2 , Microsoft's Microsoft Azure, and Google Compute Engine.

      AWS has been available since 2006 and has developed the most extensive services ant tools variety at a massive scale. Azure and GCP are about half the AWS age, but also satisfied our technical requirements.

      It is worth noting that even though all three providers support Docker containerization services, GCP has the most robust offering due to their investments in Kubernetes. Also, if you are a Microsoft shop, and develop in .NET - Visual Studio Azure shines at integration there and all your existing .NET code works seamlessly on Azure. All three providers have serverless computing offerings (AWS Lambda, Azure Functions, and Google Cloud Functions). Additionally, all three providers have machine learning tools, but GCP appears to be the most developer-friendly, intuitive and complete when it comes to #Machinelearning and #AI.

      The prices between providers are competitive across the board. For our requirements, AWS would have been the most expensive, GCP the least expensive and Azure was in the middle. Plus, if you #Autoscale frequently with large deltas, note that Azure and GCP have per minute billing, where AWS bills you per hour. We also applied for the #Startup programs with all three providers, and this is where Azure shined. While AWS and GCP for startups would have covered us for about one year of infrastructure costs, Azure Sponsorship would cover about two years of CodeFactor's hosting costs. Moreover, Azure Team was terrific - I felt that they wanted to work with us where for AWS and GCP we were just another startup.

      In summary, we were leaning towards GCP. GCP's advantages in containerization, automation toolset, #Devops mindset, and pricing were the driving factors there. Nevertheless, we could not say no to Azure's financial incentives and a strong sense of partnership and support throughout the process.

      Bottom line is, IAAS offerings with AWS, Azure, and GCP are evolving fast. At CodeFactor, we aim to be platform agnostic where it is practical and retain the flexibility to cherry-pick the best products across providers.

      See more
      Tim Nolet

      AWS Lambda Serverless Amazon CloudWatch Azure Functions Google Cloud Functions Node.js

      In the last year or so, I moved all Checkly monitoring workloads to AWS Lambda. Here are some stats:

      • We run three core functions in all AWS regions. They handle API checks, browser checks and setup / teardown scripts. Check our docs to find out what that means.
      • All functions are hooked up to SNS topics but can also be triggered directly through AWS SDK calls.
      • The busiest function is a plumbing function that forwards data to our database. It is invoked anywhere between 7000 and 10.000 times per hour with an average duration of about 179 ms.
      • We run separate dev and test versions of each function in each region.

      Moving all this to AWS Lambda took some work and considerations. The blog post linked below goes into the following topics:

      • Why Lambda is an almost perfect match for SaaS. Especially when you're small.
      • Why I don't use a "big" framework around it.
      • Why distributed background jobs triggered by queues are Lambda's raison d'être.
      • Why monitoring & logging is still an issue.

      https://blog.checklyhq.com/how-i-made-aws-lambda-work-for-my-saas/

      See more