Need advice about which tool to choose?Ask the StackShare community!

Apex

155
110
+ 1
0
AWS Lambda

22.1K
16.1K
+ 1
427
Add tool

Apex vs AWS Lambda: What are the differences?

Developers describe Apex as "Serverless Architecture with AWS Lambda". Apex is a small tool for deploying and managing AWS Lambda functions. With shims for languages not yet supported by Lambda, you can use Golang out of the box. On the other hand, AWS Lambda is detailed as "Automatically run code in response to modifications to objects in Amazon S3 buckets, messages in Kinesis streams, or updates in DynamoDB". 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.

Apex and AWS Lambda can be categorized as "Serverless / Task Processing" tools.

Some of the features offered by Apex are:

  • Supports languages Lambda does not natively support via shim, such as Go
  • Binary install (useful for continuous deployment in CI etc)
  • Project level function and resource management

On the other hand, AWS Lambda provides the following key features:

  • Extend other AWS services with custom logic
  • Build custom back-end services
  • Completely Automated Administration

Apex is an open source tool with 7.84K GitHub stars and 568 GitHub forks. Here's a link to Apex's open source repository on GitHub.

Advice on Apex and AWS Lambda

Need advice on what platform, systems and tools to use.

Evaluating whether to start a new digital business for which we will need to build a website that handles all traffic. Website only right now. May add smartphone apps later. No desktop app will ever be added. Website to serve various countries and languages. B2B and B2C type customers. Need to handle heavy traffic, be low cost, and scale well.

We are open to either build it on AWS or on Microsoft Azure.

Apologies if I'm leaving out some info. My first post. :) Thanks in advance!

See more
Replies (2)
Anis Zehani

I recommend this : -Spring reactive for back end : the fact it's reactive (async) it consumes half of the resources that a sync platform needs (so less CPU -> less money). -Angular : Web Front end ; it's gives you the possibility to use PWA which is a cheap replacement for a mobile app (but more less popular). -Docker images. -Kubernetes to orchestrate all the containers. -I Use Jenkins / blueocean, ansible for my CI/CD (with Github of course) -AWS of course : u can run a K8S cluster there, make it multi AZ (availability zones) to be highly available, use a load balancer and an auto scaler and ur good to go. -You can store data by taking any managed DB or u can deploy ur own (cheap but risky).

You pay less money, but u need some technical 2 - 3 guys to make that done.

Good luck

See more

My advice will be Front end: React Backend: Language: Java, Kotlin. Database: SQL: Postgres, MySQL, Aurora NOSQL: Mongo db. Caching: Redis. Public : Spring Webflux for async public facing operation. Admin api: Spring boot, Hibrernate, Rest API. Build Container image. Kuberenetes: AWS EKS, AWS ECS, Google GKE. Use Jenkins for CI/CD pipeline. Buddy works is good for AWS. Static content: Host on AWS S3 bucket, Use Cloudfront or Cloudflare as CDN.

Serverless Solution: Api gateway Lambda, Serveless Aurora (SQL). AWS S3 bucket.

See more
Decisions about Apex and AWS Lambda
Cory Bell

Netlfiy Functions uses AWS Lambda under the hood, but Netlify adds some nice sugar. The biggest advantage is the local development experience with netlify-cli. This allows you to run your functions locally with local configuration or pull configs from the Netlify dashboard. I built a health-check endpoint in about 2 minutes, and my send-email function in less than an hour.

See more

When adding a new feature to Checkly rearchitecting some older piece, I tend to pick Heroku for rolling it out. But not always, because sometimes I pick AWS Lambda . The short story:

  • Developer Experience trumps everything.
  • AWS Lambda is cheap. Up to a limit though. This impact not only your wallet.
  • If you need geographic spread, AWS is lonely at the top.
The setup

Recently, I was doing a brainstorm at a startup here in Berlin on the future of their infrastructure. They were ready to move on from their initial, almost 100% Ec2 + Chef based setup. Everything was on the table. But we crossed out a lot quite quickly:

  • Pure, uncut, self hosted Kubernetes — way too much complexity
  • Managed Kubernetes in various flavors — still too much complexity
  • Zeit — Maybe, but no Docker support
  • Elastic Beanstalk — Maybe, bit old but does the job
  • Heroku
  • Lambda

It became clear a mix of PaaS and FaaS was the way to go. What a surprise! That is exactly what I use for Checkly! But when do you pick which model?

I chopped that question up into the following categories:

  • Developer Experience / DX 🤓
  • Ops Experience / OX 🐂 (?)
  • Cost 💵
  • Lock in 🔐

Read the full post linked below for all details

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Apex
Pros of AWS Lambda
    Be the first to leave a pro
    • 128
      No infrastructure
    • 82
      Cheap
    • 69
      Quick
    • 58
      Stateless
    • 47
      No deploy, no server, great sleep
    • 11
      AWS Lambda went down taking many sites with it
    • 6
      Event Driven Governance
    • 6
      Easy to deploy
    • 6
      Extensive API
    • 6
      Auto scale and cost effective
    • 5
      VPC Support
    • 3
      Integrated with various AWS services

    Sign up to add or upvote prosMake informed product decisions

    Cons of Apex
    Cons of AWS Lambda
      Be the first to leave a con
      • 6
        Cant execute ruby or go
      • 2
        Compute time limited
      • 0
        Can't execute PHP w/o significant effort

      Sign up to add or upvote consMake informed product decisions

      - No public GitHub repository available -

      What is Apex?

      Apex is a small tool for deploying and managing AWS Lambda functions. With shims for languages not yet supported by Lambda, you can use Golang out of the box.

      What is 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.

      Need advice about which tool to choose?Ask the StackShare community!

      Jobs that mention Apex and AWS Lambda as a desired skillset
      What companies use Apex?
      What companies use AWS Lambda?
      See which teams inside your own company are using Apex or AWS Lambda.
      Sign up for StackShare EnterpriseLearn More

      Sign up to get full access to all the companiesMake informed product decisions

      What tools integrate with Apex?
      What tools integrate with AWS Lambda?

      Sign up to get full access to all the tool integrationsMake informed product decisions

      Blog Posts

      GitHubPythonNode.js+47
      53
      70941
      GitHubDockerAmazon EC2+23
      12
      6429
      JavaScriptGitHubPython+42
      53
      20821
      What are some alternatives to Apex and AWS Lambda?
      Java
      Java is a programming language and computing platform first released by Sun Microsystems in 1995. There are lots of applications and websites that will not work unless you have Java installed, and more are created every day. Java is fast, secure, and reliable. From laptops to datacenters, game consoles to scientific supercomputers, cell phones to the Internet, Java is everywhere!
      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.
      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.
      Google Cloud Functions
      Construct applications from bite-sized business logic billed to the nearest 100 milliseconds, only while your code is running
      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.
      See all alternatives