Alternatives to ExpressJS logo

Alternatives to ExpressJS

Koa, React, Flask, Django, and Golang are the most popular alternatives and competitors to ExpressJS.
31.7K
23.4K
+ 1
1.6K

What is ExpressJS and what are its top alternatives?

Express is a minimal and flexible node.js web application framework, providing a robust set of features for building single and multi-page, and hybrid web applications.
ExpressJS is a tool in the Microframeworks (Backend) category of a tech stack.
ExpressJS is an open source tool with GitHub stars and GitHub forks. Here’s a link to ExpressJS's open source repository on GitHub

Top Alternatives to ExpressJS

  • Koa
    Koa

    Koa aims to be a smaller, more expressive, and more robust foundation for web applications and APIs. Through leveraging generators Koa allows you to ditch callbacks and greatly increase error-handling. Koa does not bundle any middleware. ...

  • React
    React

    Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project. ...

  • Flask
    Flask

    Flask is intended for getting started very quickly and was developed with best intentions in mind. ...

  • Django
    Django

    Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design. ...

  • Golang
    Golang

    Go is expressive, concise, clean, and efficient. Its concurrency mechanisms make it easy to write programs that get the most out of multicore and networked machines, while its novel type system enables flexible and modular program construction. Go compiles quickly to machine code yet has the convenience of garbage collection and the power of run-time reflection. It's a fast, statically typed, compiled language that feels like a dynamically typed, interpreted language. ...

  • NGINX
    NGINX

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

  • Laravel
    Laravel

    It is a web application framework with expressive, elegant syntax. It attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching. ...

  • hapi
    hapi

    hapi is a simple to use configuration-centric framework with built-in support for input validation, caching, authentication, and other essential facilities for building web applications and services. ...

ExpressJS alternatives & related posts

Koa logo

Koa

721
483
12
Next generation web framework for node.js
721
483
+ 1
12
PROS OF KOA
  • 6
    Async/Await
  • 5
    JavaScript
  • 1
    REST API
CONS OF KOA
    Be the first to leave a con

    related Koa posts

    ReactQL is a React + GraphQL front-end starter kit. #JSX is a natural way to think about building UI, and it renders to pure #HTML in the browser and on the server, making it trivial to build server-rendered Single Page Apps. GraphQL via Apollo was chosen for the data layer; #GraphQL makes it simple to request just the data your app needs, and #Apollo takes care of communicating with your API (written in any language; doesn't have to be JavaScript!), caching, and rendering to #React.

    ReactQL is written in TypeScript to provide full types/Intellisense, and pick up hard-to-diagnose goofs that might later show up at runtime. React makes heavy use of Webpack 4 to handle transforming your code to an optimised client-side bundle, and in throws back just enough code needed for the initial render, while seamlessly handling import statements asynchronously as needed, making the payload your user downloads ultimately much smaller than trying to do it by hand.

    React Helmet was chosen to handle <head> content, because it works universally, making it easy to throw back the correct <title> and other tags on the initial render, as well as inject new tags for subsequent client-side views.

    styled-components, Sass, Less and PostCSS were added to give developers a choice of whether to build styles purely in React / JavaScript, or whether to defer to a #css #preprocessor. This is especially useful for interop with UI frameworks like Bootstrap, Semantic UI, Foundation, etc - ReactQL lets you mix and match #css and renders to both a static .css file during bundling as well as generates per-page <style> tags when using #StyledComponents.

    React Router handles routing, because it works both on the server and in the client. ReactQL customises it further by capturing non-200 responses on the server, redirecting or throwing back custom 404 pages as needed.

    Koa is the web server that handles all incoming HTTP requests, because it's fast (TTFB < 5ms, even after fully rendering React), and its natively #async, making it easy to async/await inside routes and middleware.

    See more
    Antonio Kobashikawa
    Web developer | Blogger | Freelancer at Rulo Kobashikawa · | 6 upvotes · 239.5K views

    We are using Node.js and ExpressJS to build a REST services that is middleware of a legacy system. MongoDB as database. Vue.js helps us to make rapid UI to test use cases. Frontend is build for mobile with Ionic . We like using JavaScript and ES6 .

    I think next step could be to use Koa but I am not sure.

    See more
    React logo

    React

    170.4K
    140.7K
    4.1K
    A JavaScript library for building user interfaces
    170.4K
    140.7K
    + 1
    4.1K
    PROS OF REACT
    • 830
      Components
    • 672
      Virtual dom
    • 578
      Performance
    • 508
      Simplicity
    • 442
      Composable
    • 186
      Data flow
    • 166
      Declarative
    • 128
      Isn't an mvc framework
    • 120
      Reactive updates
    • 115
      Explicit app state
    • 50
      JSX
    • 29
      Learn once, write everywhere
    • 22
      Easy to Use
    • 21
      Uni-directional data flow
    • 17
      Works great with Flux Architecture
    • 11
      Great perfomance
    • 10
      Javascript
    • 9
      Built by Facebook
    • 8
      TypeScript support
    • 6
      Speed
    • 6
      Server Side Rendering
    • 5
      Feels like the 90s
    • 5
      Excellent Documentation
    • 5
      Props
    • 5
      Functional
    • 5
      Easy as Lego
    • 5
      Closer to standard JavaScript and HTML than others
    • 5
      Cross-platform
    • 5
      Easy to start
    • 5
      Hooks
    • 5
      Awesome
    • 5
      Scalable
    • 4
      Super easy
    • 4
      Allows creating single page applications
    • 4
      Server side views
    • 4
      Sdfsdfsdf
    • 4
      Start simple
    • 4
      Strong Community
    • 4
      Fancy third party tools
    • 4
      Scales super well
    • 3
      Has arrow functions
    • 3
      Beautiful and Neat Component Management
    • 3
      Just the View of MVC
    • 3
      Simple, easy to reason about and makes you productive
    • 3
      Fast evolving
    • 3
      SSR
    • 3
      Great migration pathway for older systems
    • 3
      Rich ecosystem
    • 3
      Simple
    • 3
      Has functional components
    • 3
      Every decision architecture wise makes sense
    • 3
      Very gentle learning curve
    • 2
      Split your UI into components with one true state
    • 2
      Recharts
    • 2
      Permissively-licensed
    • 2
      Fragments
    • 2
      Sharable
    • 2
      Image upload
    • 2
      HTML-like
    • 1
      React hooks
    • 1
      Datatables
    CONS OF REACT
    • 41
      Requires discipline to keep architecture organized
    • 30
      No predefined way to structure your app
    • 29
      Need to be familiar with lots of third party packages
    • 13
      JSX
    • 10
      Not enterprise friendly
    • 6
      One-way binding only
    • 3
      State consistency with backend neglected
    • 3
      Bad Documentation
    • 2
      Error boundary is needed
    • 2
      Paradigms change too fast

    related React 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
    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
    Flask logo

    Flask

    18.9K
    15.9K
    82
    A microframework for Python based on Werkzeug, Jinja 2 and good intentions
    18.9K
    15.9K
    + 1
    82
    PROS OF FLASK
    • 14
      Flexibilty
    • 10
      For it flexibility
    • 9
      Flexibilty and easy to use
    • 8
      Flask
    • 7
      User friendly
    • 6
      Secured
    • 5
      Unopinionated
    • 3
      Orm
    • 2
      Secure
    • 1
      Beautiful code
    • 1
      Easy to get started
    • 1
      Easy to develop and maintain applications
    • 1
      Not JS
    • 1
      Easy to use
    • 1
      Documentation
    • 1
      Python
    • 1
      Minimal
    • 1
      Lightweight
    • 1
      Easy to setup and get it going
    • 1
      Perfect for small to large projects with superb docs.
    • 1
      Easy to integrate
    • 1
      Speed
    • 1
      Get started quickly
    • 1
      Customizable
    • 1
      Simple to use
    • 1
      Powerful
    • 1
      Rapid development
    • 0
      Open source
    • 0
      Well designed
    • 0
      Productive
    • 0
      Awesome
    • 0
      Expressive
    • 0
      Love it
    CONS OF FLASK
    • 10
      Not JS
    • 7
      Context
    • 5
      Not fast
    • 1
      Don't has many module as in spring

    related Flask posts

    James Man
    Software Engineer at Pinterest · | 46 upvotes · 2.8M views
    Shared insights
    on
    FlaskFlaskReactReact
    at

    One of our top priorities at Pinterest is fostering a safe and trustworthy experience for all Pinners. As Pinterest’s user base and ads business grow, the review volume has been increasing exponentially, and more content types require moderation support. To solve greater engineering and operational challenges at scale, we needed a highly-reliable and performant system to detect, report, evaluate, and act on abusive content and users and so we created Pinqueue.

    Pinqueue-3.0 serves as a generic platform for content moderation and human labeling. Under the hood, Pinqueue3.0 is a Flask + React app powered by Pinterest’s very own Gestalt UI framework. On the backend, Pinqueue3.0 heavily relies on PinLater, a Pinterest-built reliable asynchronous job execution system, to handle the requests for enqueueing and action-taking. Using PinLater has significantly strengthened Pinqueue3.0’s overall infra with its capability of processing a massive load of events with configurable retry policies.

    Hundreds of millions of people around the world use Pinterest to discover and do what they love, and our job is to protect them from abusive and harmful content. We’re committed to providing an inspirational yet safe experience to all Pinners. Solving trust & safety problems is a joint effort requiring expertise across multiple domains. Pinqueue3.0 not only plays a critical role in responsively taking down unsafe content, it also has become an enabler for future ML/automation initiatives by providing high-quality human labels. Going forward, we will continue to improve the review experience, measure review quality and collaborate with our machine learning teams to solve content moderation beyond manual reviews at an even larger scale.

    See more

    Hey, so I developed a basic application with Python. But to use it, you need a python interpreter. I want to add a GUI to make it more appealing. What should I choose to develop a GUI? I have very basic skills in front end development (CSS, JavaScript). I am fluent in python. I'm looking for a tool that is easy to use and doesn't require too much code knowledge. I have recently tried out Flask, but it is kinda complicated. Should I stick with it, move to Django, or is there another nice framework to use?

    See more
    Django logo

    Django

    37.2K
    33.7K
    4.2K
    The Web framework for perfectionists with deadlines
    37.2K
    33.7K
    + 1
    4.2K
    PROS OF DJANGO
    • 672
      Rapid development
    • 488
      Open source
    • 425
      Great community
    • 379
      Easy to learn
    • 277
      Mvc
    • 232
      Beautiful code
    • 223
      Elegant
    • 207
      Free
    • 203
      Great packages
    • 194
      Great libraries
    • 80
      Comes with auth and crud admin panel
    • 79
      Restful
    • 78
      Powerful
    • 76
      Great documentation
    • 72
      Great for web
    • 57
      Python
    • 43
      Great orm
    • 41
      Great for api
    • 32
      All included
    • 29
      Fast
    • 25
      Web Apps
    • 23
      Easy setup
    • 23
      Clean
    • 21
      Used by top startups
    • 19
      Sexy
    • 19
      ORM
    • 15
      The Django community
    • 14
      Allows for very rapid development with great libraries
    • 14
      Convention over configuration
    • 11
      King of backend world
    • 10
      Full stack
    • 10
      Great MVC and templating engine
    • 8
      Fast prototyping
    • 8
      Mvt
    • 7
      Easy to develop end to end AI Models
    • 7
      Batteries included
    • 7
      Its elegant and practical
    • 6
      Have not found anything that it can't do
    • 6
      Very quick to get something up and running
    • 6
      Cross-Platform
    • 5
      Easy Structure , useful inbuilt library
    • 5
      Great peformance
    • 5
      Zero code burden to change databases
    • 5
      Python community
    • 4
      Map
    • 4
      Just the right level of abstraction
    • 4
      Easy to change database manager
    • 4
      Modular
    • 4
      Many libraries
    • 4
      Easy to use
    • 4
      Easy
    • 4
      Full-Text Search
    • 3
      Scaffold
    • 1
      Fastapi
    • 1
      Built in common security
    • 1
      Scalable
    • 1
      Great default admin panel
    • 1
      Node js
    • 1
      Gigante ta
    • 0
      Rails
    CONS OF DJANGO
    • 26
      Underpowered templating
    • 22
      Autoreload restarts whole server
    • 22
      Underpowered ORM
    • 15
      URL dispatcher ignores HTTP method
    • 10
      Internal subcomponents coupling
    • 8
      Not nodejs
    • 8
      Configuration hell
    • 7
      Admin
    • 5
      Not as clean and nice documentation like Laravel
    • 4
      Python
    • 3
      Not typed
    • 3
      Bloated admin panel included
    • 2
      Overwhelming folder structure
    • 2
      InEffective Multithreading
    • 1
      Not type safe

    related Django posts

    Dmitry Mukhin
    Engineer at Uploadcare · | 25 upvotes · 2.4M views

    Simple controls over complex technologies, as we put it, wouldn't be possible without neat UIs for our user areas including start page, dashboard, settings, and docs.

    Initially, there was Django. Back in 2011, considering our Python-centric approach, that was the best choice. Later, we realized we needed to iterate on our website more quickly. And this led us to detaching Django from our front end. That was when we decided to build an SPA.

    For building user interfaces, we're currently using React as it provided the fastest rendering back when we were building our toolkit. It’s worth mentioning Uploadcare is not a front-end-focused SPA: we aren’t running at high levels of complexity. If it were, we’d go with Ember.js.

    However, there's a chance we will shift to the faster Preact, with its motto of using as little code as possible, and because it makes more use of browser APIs. One of our future tasks for our front end is to configure our Webpack bundler to split up the code for different site sections. For styles, we use PostCSS along with its plugins such as cssnano which minifies all the code.

    All that allows us to provide a great user experience and quickly implement changes where they are needed with as little code as possible.

    See more

    Hey, so I developed a basic application with Python. But to use it, you need a python interpreter. I want to add a GUI to make it more appealing. What should I choose to develop a GUI? I have very basic skills in front end development (CSS, JavaScript). I am fluent in python. I'm looking for a tool that is easy to use and doesn't require too much code knowledge. I have recently tried out Flask, but it is kinda complicated. Should I stick with it, move to Django, or is there another nice framework to use?

    See more
    Golang logo

    Golang

    22.3K
    13.7K
    3.3K
    An open source programming language that makes it easy to build simple, reliable, and efficient software
    22.3K
    13.7K
    + 1
    3.3K
    PROS OF GOLANG
    • 548
      High-performance
    • 395
      Simple, minimal syntax
    • 363
      Fun to write
    • 301
      Easy concurrency support via goroutines
    • 273
      Fast compilation times
    • 193
      Goroutines
    • 180
      Statically linked binaries that are simple to deploy
    • 150
      Simple compile build/run procedures
    • 136
      Backed by google
    • 136
      Great community
    • 53
      Garbage collection built-in
    • 45
      Built-in Testing
    • 44
      Excellent tools - gofmt, godoc etc
    • 39
      Elegant and concise like Python, fast like C
    • 37
      Awesome to Develop
    • 26
      Used for Docker
    • 25
      Flexible interface system
    • 24
      Deploy as executable
    • 24
      Great concurrency pattern
    • 20
      Open-source Integration
    • 18
      Easy to read
    • 17
      Fun to write and so many feature out of the box
    • 16
      Go is God
    • 14
      Easy to deploy
    • 14
      Powerful and simple
    • 14
      Its Simple and Heavy duty
    • 13
      Best language for concurrency
    • 13
      Concurrency
    • 11
      Rich standard library
    • 11
      Safe GOTOs
    • 10
      Clean code, high performance
    • 10
      Easy setup
    • 9
      High performance
    • 9
      Simplicity, Concurrency, Performance
    • 8
      Hassle free deployment
    • 8
      Single binary avoids library dependency issues
    • 7
      Gofmt
    • 7
      Cross compiling
    • 7
      Simple, powerful, and great performance
    • 7
      Used by Giants of the industry
    • 6
      Garbage Collection
    • 5
      Very sophisticated syntax
    • 5
      Excellent tooling
    • 5
      WYSIWYG
    • 4
      Keep it simple and stupid
    • 4
      Widely used
    • 4
      Kubernetes written on Go
    • 2
      No generics
    • 1
      Operator goto
    • 1
      Looks not fancy, but promoting pragmatic idioms
    CONS OF GOLANG
    • 42
      You waste time in plumbing code catching errors
    • 25
      Verbose
    • 23
      Packages and their path dependencies are braindead
    • 16
      Google's documentations aren't beginer friendly
    • 15
      Dependency management when working on multiple projects
    • 10
      Automatic garbage collection overheads
    • 8
      Uncommon syntax
    • 7
      Type system is lacking (no generics, etc)
    • 5
      Collection framework is lacking (list, set, map)
    • 3
      Best programming language
    • 1
      A failed experiment to combine c and python

    related Golang posts

    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
    Nick Parsons
    Building cool things on the internet 🛠️ at Stream · | 35 upvotes · 4M views

    Winds 2.0 is an open source Podcast/RSS reader developed by Stream with a core goal to enable a wide range of developers to contribute.

    We chose JavaScript because nearly every developer knows or can, at the very least, read JavaScript. With ES6 and Node.js v10.x.x, it’s become a very capable language. Async/Await is powerful and easy to use (Async/Await vs Promises). Babel allows us to experiment with next-generation JavaScript (features that are not in the official JavaScript spec yet). Yarn allows us to consistently install packages quickly (and is filled with tons of new tricks)

    We’re using JavaScript for everything – both front and backend. Most of our team is experienced with Go and Python, so Node was not an obvious choice for this app.

    Sure... there will be haters who refuse to acknowledge that there is anything remotely positive about JavaScript (there are even rants on Hacker News about Node.js); however, without writing completely in JavaScript, we would not have seen the results we did.

    #FrameworksFullStack #Languages

    See more
    NGINX logo

    NGINX

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

    related NGINX posts

    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 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
    John-Daniel Trask
    Co-founder & CEO at Raygun · | 19 upvotes · 266.8K views

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

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

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

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

    #CloudHosting #WebServers #CloudStorage #LoadBalancerReverseProxy

    See more
    Laravel logo

    Laravel

    27.7K
    23K
    3.9K
    A PHP Framework For Web Artisans
    27.7K
    23K
    + 1
    3.9K
    PROS OF LARAVEL
    • 553
      Clean architecture
    • 392
      Growing community
    • 370
      Composer friendly
    • 344
      Open source
    • 324
      The only framework to consider for php
    • 220
      Mvc
    • 210
      Quickly develop
    • 168
      Dependency injection
    • 156
      Application architecture
    • 143
      Embraces good community packages
    • 73
      Write less, do more
    • 71
      Orm (eloquent)
    • 66
      Restful routing
    • 57
      Database migrations & seeds
    • 55
      Artisan scaffolding and migrations
    • 41
      Great documentation
    • 40
      Awesome
    • 30
      Awsome, Powerfull, Fast and Rapid
    • 29
      Build Apps faster, easier and better
    • 28
      Eloquent ORM
    • 26
      Promotes elegant coding
    • 26
      JSON friendly
    • 26
      Modern PHP
    • 25
      Most easy for me
    • 24
      Easy to learn, scalability
    • 23
      Beautiful
    • 22
      Blade Template
    • 21
      Test-Driven
    • 15
      Security
    • 15
      Based on SOLID
    • 13
      Cool
    • 13
      Clean Documentation
    • 13
      Easy to attach Middleware
    • 12
      Simple
    • 12
      Convention over Configuration
    • 11
      Easy Request Validatin
    • 10
      Simpler
    • 10
      Easy to use
    • 10
      Fast
    • 9
      Get going quickly straight out of the box. BYOKDM
    • 9
      Its just wow
    • 8
      Laravel + Cassandra = Killer Framework
    • 8
      Simplistic , easy and faster
    • 8
      Friendly API
    • 7
      Less dependencies
    • 7
      Super easy and powerful
    • 6
      Great customer support
    • 6
      Its beautiful to code in
    • 5
      Speed
    • 5
      Eloquent
    • 5
      Composer
    • 5
      Minimum system requirements
    • 5
      Laravel Mix
    • 5
      Easy
    • 5
      The only "cons" is wrong! No static method just Facades
    • 5
      Fast and Clarify framework
    • 5
      Active Record
    • 5
      Php7
    • 4
      Ease of use
    • 4
      Laragon
    • 4
      Laravel casher
    • 4
      Easy views handling and great ORM
    • 4
      Laravel Forge and Envoy
    • 4
      Cashier with Braintree and Stripe
    • 3
      Laravel Passport
    • 3
      Laravel Spark
    • 3
      Intuitive usage
    • 3
      Laravel Horizon and Telescope
    • 3
      Laravel Nova
    • 3
      Rapid development
    • 2
      Laravel Vite
    • 2
      Scout
    • 2
      Deployment
    • 1
      Succint sintax
    CONS OF LARAVEL
    • 54
      PHP
    • 33
      Too many dependency
    • 23
      Slower than the other two
    • 17
      A lot of static method calls for convenience
    • 15
      Too many include
    • 13
      Heavy
    • 9
      Bloated
    • 8
      Laravel
    • 7
      Confusing
    • 5
      Too underrated
    • 4
      Not fast with MongoDB
    • 1
      Slow and too much big
    • 1
      Not using SOLID principles
    • 1
      Difficult to learn

    related Laravel posts

    I need to build a web application plus android and IOS apps for an enterprise, like an e-commerce portal. It will have intensive use of MySQL to display thousands (40-50k) of live product information in an interactive table (searchable, filterable), live delivery tracking. It has to be secure, as it will handle information on customers, sales, inventory. Here is the technology stack: Backend: Laravel 7 Frondend: Vue.js, React or AngularJS?

    Need help deciding technology stack. Thanks.

    See more
    Christopher Wray
    Web Developer at Soltech LLC · | 15 upvotes · 175.1K views

    This week, we finally released NurseryPeople.com. In the end, I chose to provision our server on DigitalOcean. So far, I am SO happy with that decision. Although setting everything up was a challenge, and I learned a lot, DigitalOceans blogs helped in so many ways. I was able to set up nginx and the Laravel web app pretty smoothly. I am also using Buddy for deploying changes made in git, which is super awesome. All I have to do in order to deploy is push my code to my private repo, and buddy transfers everything over to DigitalOcean. So far, we haven't had any downtime and DigitalOceans prices are quite fair for the power under the hood.

    See more
    hapi logo

    hapi

    434
    455
    87
    Server Framework for Node.js
    434
    455
    + 1
    87
    PROS OF HAPI
    • 27
      Makes me Hapi making REST APIs
    • 14
      Simpler than other REST libraries
    • 14
      Configuration
    • 13
      Quality Driven Ecosystem
    • 13
      Modularization
    • 5
      Easy testability
    • 1
      Better validation
    • 0
      Restify
    CONS OF HAPI
      Be the first to leave a con

      related hapi posts

      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
      Tim Nolet

      JavaScript Node.js hapi Vue.js Swagger UI Slate

      Two weeks ago we released the public API for Checkly. We already had an API that was serving our frontend Vue.js app. We decided to create an new set of API endpoints and not reuse the already existing one. The blog post linked below details what parts we needed to refactor, what parts we added and how we handled generating API documentation. More specifically, the post dives into:

      • Refactoring the existing Hapi.js based API
      • API key based authentication
      • Refactoring models with Objection.js
      • Validating plan limits
      • Generating Swagger & Slate based documentation
      See more