Alternatives to Apigility logo

Alternatives to Apigility

Slim, Lumen, Laravel, API Platform, and Expressive are the most popular alternatives and competitors to Apigility.
37
99
+ 1
2

What is Apigility and what are its top alternatives?

An API-based architecture is essential to agile delivery of mobile applications. Apigility provides JSON representations that can be parsed and used in any mobile framework; write for the web or native applications simultaneously!
Apigility is a tool in the API Tools category of a tech stack.
Apigility is an open source tool with 461 GitHub stars and 134 GitHub forks. Here’s a link to Apigility's open source repository on GitHub

Top Alternatives to Apigility

  • Slim

    Slim

    Slim is easy to use for both beginners and professionals. Slim favors cleanliness over terseness and common cases over edge cases. Its interface is simple, intuitive, and extensively documented — both online and in the code itself. ...

  • Lumen

    Lumen

    Laravel Lumen is a stunningly fast PHP micro-framework for building web applications with expressive, elegant syntax. We believe development must be an enjoyable, creative experience to be truly fulfilling. Lumen attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as routing, database abstraction, queueing, and caching. ...

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

  • API Platform

    API Platform

    It is a set of tools to build and consume web APIs. You can build a fully-featured hypermedia or GraphQL API in minutes. Leverage its awesome features to develop complex and high performance API-first projects. Extend or override everything you want. ...

  • Expressive

    Expressive

    Make your code flexible and robust, using the dependency injection container of your choice. ...

  • Postman

    Postman

    It is the only complete API development environment, used by nearly five million developers and more than 100,000 companies worldwide. ...

  • Amazon API Gateway

    Amazon API Gateway

    Amazon API Gateway handles all the tasks involved in accepting and processing up to hundreds of thousands of concurrent API calls, including traffic management, authorization and access control, monitoring, and API version management. ...

  • Insomnia REST Client

    Insomnia REST Client

    Insomnia is a powerful REST API Client with cookie management, environment variables, code generation, and authentication for Mac, Window, and Linux. ...

Apigility alternatives & related posts

Slim logo

Slim

244
327
134
A PHP micro framework
244
327
+ 1
134
PROS OF SLIM
  • 29
    Microframework
  • 25
    API
  • 21
    Open source
  • 19
    Php
  • 11
    Fast
  • 8
    Restful & fast framework
  • 7
    Easy Setup, Great Documentation
  • 5
    Good document to upgrade from previous version
  • 5
    Clear and straightforward
  • 4
    Modular
CONS OF SLIM
    Be the first to leave a con

    related Slim posts

    Y. Taborda
    Shared insights
    on
    PHP
    Lumen
    Yii
    Slim

    I'm about to start a new project to build a REST API, and I got to this point: Yii2 Vs Lumen Vs Slim, I used Yii 1.1 a while a go and it was awesome, really easy to work with, as a developer you don't have to worry about almost anything, just setup the framework, get your php extensions, and start coding your app.

    But, I was told about performance and someone recomended Lumen or Slim to work with a micro framework and a less bloated framework, what worries me is the lack of advantages that Yii2 offers, ACF and RBAC as a native tool on the framework, gii, the model validations and all the security props already in it.

    Is it worth it? Is the performance so great on those frameworks to leave aside the advantages of a framework like Yii2?

    How do you suggest to make the test to prove wich one is better?

    PHP Lumen Yii Slim

    See more
    Lumen logo

    Lumen

    368
    549
    152
    The stunningly fast PHP micro-framework by Laravel
    368
    549
    + 1
    152
    PROS OF LUMEN
    • 33
      API
    • 25
      Microframework
    • 19
      MVC
    • 16
      PHP
    • 12
      Open source
    • 11
      Eloquent
    • 10
      Restful & fast framework
    • 7
      Illuminate support
    • 7
      Composer
    • 4
      Brother of laravel and fast
    • 4
      Easy to learn
    • 4
      Fast
    CONS OF LUMEN
    • 3
      Not fast
    • 2
      PHP
    • 1
      Not fast with MongoDB

    related Lumen posts

    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
    Aimad Quouninich

    Hello everyone,

    I have a final-study project, and I'm responsible for making decisions for what frameworks to use (both front-end and back-end) and the software architecture to adapt.

    The project is a web application for a concrete company. The main goal is to calculate what is called OEE (Overall Equipment Effectiveness), meaning simply the efficiency of the machine. The calculation and display of OEE will be in real-time, meaning that this rate will be updated every two minutes, and it will appear in a graph. Also, we have the state of the machines to display whether the machines are working just fine or there is some problem.

    This will be done using IoT, meaning that important data will be sent from the machine to the web application that I will create via the API (someone else will be responsible for this matter). Of course, the application will include employees, factories, as well as machines, ... etc.

    The most important thing in the application is real-time performance monitoring of machines and the OEE.

    A real example of what we want to do => https://evocon.com/

    I choose to use Laravel because : - This type of applications could be implemented by Laravel - Me and my colleague have some knowledge and practice with this framework (choosing other technologies like Node.js means a huge learning curve) - Easy documentation and abandon tutorials

    The only reason why I choose Vue.js because It goes well with Laravel (from what I have learned).

    The second important question, which software architecture should I adapt ? should I use Microservice Architecture or the normal and well-known Monolithic Architecture? I know the benefits and disadvantages of the first and second methods, but I do not want to make a wrong decision.

    If I choose microservice for this project, I will use Lumen (PHP Micro-Framework By Laravel).

    Should I use micro-frontend as well? Like VuMS, or it's not necessary for this project?

    I don't think that the reasons to choose Laravel are enough, so I want to understand the obstacles that I may face during the development.

    In the end, I decided to ask and take expert opinions.

    NOTE: this web application will be used by other companies, like in the case of evocon.

    If there are tips and things that I must know to accomplish this project, please mention them.

    Thank you very much.

    See more
    Laravel logo

    Laravel

    19.4K
    15.4K
    3.5K
    A PHP Framework For Web Artisans
    19.4K
    15.4K
    + 1
    3.5K
    PROS OF LARAVEL
    • 507
      Clean architecture
    • 369
      Growing community
    • 343
      Composer friendly
    • 317
      Open source
    • 298
      The only framework to consider for php
    • 196
      Mvc
    • 191
      Quickly develop
    • 157
      Dependency injection
    • 145
      Application architecture
    • 131
      Embraces good community packages
    • 60
      Write less, do more
    • 54
      Restful routing
    • 48
      Orm (eloquent)
    • 45
      Artisan scaffolding and migrations
    • 44
      Database migrations & seeds
    • 35
      Awesome
    • 33
      Great documentation
    • 25
      Promotes elegant coding
    • 25
      Awsome, Powerfull, Fast and Rapid
    • 24
      Build Apps faster, easier and better
    • 22
      JSON friendly
    • 22
      Easy to learn, scalability
    • 21
      Eloquent ORM
    • 21
      Most easy for me
    • 20
      Modern PHP
    • 19
      Test-Driven
    • 18
      Beautiful
    • 18
      Blade Template
    • 13
      Security
    • 12
      Based on SOLID
    • 11
      Clean Documentation
    • 11
      Simple
    • 11
      Cool
    • 10
      Convention over Configuration
    • 10
      Easy to attach Middleware
    • 9
      Easy Request Validatin
    • 8
      Laravel + Cassandra = Killer Framework
    • 8
      Simpler
    • 8
      Get going quickly straight out of the box. BYOKDM
    • 8
      Its just wow
    • 8
      Easy to use
    • 8
      Fast
    • 7
      Less dependencies
    • 7
      Simplistic , easy and faster
    • 7
      Super easy and powerful
    • 7
      Friendly API
    • 6
      Its beautiful to code in
    • 6
      Great customer support
    • 5
      Speed
    • 5
      Easy
    • 5
      The only "cons" is wrong! No static method just Facades
    • 5
      Fast and Clarify framework
    • 5
      Active Record
    • 5
      Php7
    • 4
      Composer
    • 4
      Laragon
    • 4
      Easy views handling and great ORM
    • 4
      Minimum system requirements
    • 4
      Laravel Mix
    • 4
      Eloquent
    • 3
      Laravel Spark
    • 3
      Laravel Nova
    • 3
      Laravel casher
    • 3
      Laravel Passport
    • 3
      Laravel Horizon and Telescope
    • 3
      Laravel Forge and Envoy
    • 3
      Cashier with Braintree and Stripe
    • 3
      Ease of use
    • 3
      Intuitive usage
    • 2
      Like heart beat
    • 2
      Rapid development
    • 2
      Laravel love live long
    • 2
      Touch heart artisan
    • 2
      Scout
    • 2
      Heart touch
    CONS OF LARAVEL
    • 42
      PHP
    • 28
      Too many dependency
    • 20
      Slower than the other two
    • 16
      A lot of static method calls for convenience
    • 13
      Too many include
    • 10
      Heavy
    • 7
      Bloated
    • 6
      Laravel
    • 5
      Confusing
    • 4
      Does not work well for file uploads in Shared Hosting
    • 3
      Too underrated
    • 2
      Not fast with MongoDB
    • 1
      Difficult to learn
    • 1
      Not using SOLID principles

    related Laravel posts

    Antonio Sanchez

    Back at the start of 2017, we decided to create a web-based tool for the SEO OnPage analysis of our clients' websites. We had over 2.000 websites to analyze, so we had to perform thousands of requests to get every single page from those websites, process the information and save the big amounts of data somewhere.

    Very soon we realized that the initial chosen script language and database, PHP, Laravel and MySQL, was not going to be able to cope efficiently with such a task.

    By that time, we were doing some experiments for other projects with a language we had recently get to know, Go , so we decided to get a try and code the crawler using it. It was fantastic, we could process much more data with way less CPU power and in less time. By using the concurrency abilites that the language has to offers, we could also do more Http requests in less time.

    Unfortunately, I have no comparison numbers to show about the performance differences between Go and PHP since the difference was so clear from the beginning and that we didn't feel the need to do further comparison tests nor document it. We just switched fully to Go.

    There was still a problem: despite the big amount of Data we were generating, MySQL was performing very well, but as we were adding more and more features to the software and with those features more and more different type of data to save, it was a nightmare for the database architects to structure everything correctly on the database, so it was clear what we had to do next: switch to a NoSQL database. So we switched to MongoDB, and it was also fantastic: we were expending almost zero time in thinking how to structure the Database and the performance also seemed to be better, but again, I have no comparison numbers to show due to the lack of time.

    We also decided to switch the website from PHP and Laravel to JavaScript and Node.js and ExpressJS since working with the JSON Data that we were saving now in the Database would be easier.

    As of now, we don't only use the tool intern but we also opened it for everyone to use for free: https://tool-seo.com

    See more

    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
    API Platform logo

    API Platform

    60
    87
    7
    REST and GraphQL framework to build modern API-first projects
    60
    87
    + 1
    7
    PROS OF API PLATFORM
    • 1
      Headless
    • 1
      Symfony
    • 1
      Open source
    • 1
      Composer
    • 1
      Easy to use
    • 1
      Automated api-docs
    • 1
      Restful
    CONS OF API PLATFORM
      Be the first to leave a con

      related API Platform posts

      Expressive logo

      Expressive

      12
      10
      0
      Build PHP microservices and web applications in minutes
      12
      10
      + 1
      0
      PROS OF EXPRESSIVE
        Be the first to leave a pro
        CONS OF EXPRESSIVE
          Be the first to leave a con

          related Expressive posts

          Postman logo

          Postman

          60.2K
          48.5K
          1.8K
          Only complete API development environment
          60.2K
          48.5K
          + 1
          1.8K
          PROS OF POSTMAN
          • 484
            Easy to use
          • 368
            Great tool
          • 275
            Makes developing rest api's easy peasy
          • 155
            Easy setup, looks good
          • 143
            The best api workflow out there
          • 53
            It's the best
          • 53
            History feature
          • 44
            Adds real value to my workflow
          • 42
            Great interface that magically predicts your needs
          • 34
            The best in class app
          • 11
            Can save and share script
          • 9
            Fully featured without looking cluttered
          • 7
            Global/Environment Variables
          • 7
            Option to run scrips
          • 7
            Collections
          • 6
            Shareable Collections
          • 6
            Dead simple and useful. Excellent
          • 6
            Dark theme easy on the eyes
          • 5
            Awesome customer support
          • 5
            Great integration with newman
          • 4
            The test script is useful
          • 3
            Makes testing API's as easy as 1,2,3
          • 3
            Easy as pie
          • 3
            Saves responses
          • 3
            This has simplified my testing significantly
          • 3
            Simple
          • 3
            Documentation
          • 2
            Mocking API calls with predefined response
          • 2
            I'd recommend it to everyone who works with apis
          • 2
            API-network
          • 1
            Easy to setup, test and provides test storage
          • 1
            Continuous integration using newman
          • 1
            Graph
          • 1
            Pre-request Script and Test attributes are invaluable
          • 1
            Postman Runner CI Integration
          • 1
            Now supports GraphQL
          • 0
            <a href="http://fixbit.com/">useful tool</a>
          • 0
            Runner
          CONS OF POSTMAN
          • 9
            Stores credentials in HTTP
          • 7
            Bloated features and UI
          • 7
            Poor GraphQL support
          • 6
            Cumbersome to switch authentication tokens
          • 2
            Expensive
          • 1
            Can't prompt for per-request variables
          • 1
            Import curl
          • 1
            Support websocket
          • 1
            Import swagger

          related Postman posts

          Noah Zoschke
          Engineering Manager at Segment · | 30 upvotes · 2M views

          We just launched the Segment Config API (try it out for yourself here) — a set of public REST APIs that enable you to manage your Segment configuration. A public API is only as good as its #documentation. For the API reference doc we are using Postman.

          Postman is an “API development environment”. You download the desktop app, and build API requests by URL and payload. Over time you can build up a set of requests and organize them into a “Postman Collection”. You can generalize a collection with “collection variables”. This allows you to parameterize things like username, password and workspace_name so a user can fill their own values in before making an API call. This makes it possible to use Postman for one-off API tasks instead of writing code.

          Then you can add Markdown content to the entire collection, a folder of related methods, and/or every API method to explain how the APIs work. You can publish a collection and easily share it with a URL.

          This turns Postman from a personal #API utility to full-blown public interactive API documentation. The result is a great looking web page with all the API calls, docs and sample requests and responses in one place. Check out the results here.

          Postman’s powers don’t end here. You can automate Postman with “test scripts” and have it periodically run a collection scripts as “monitors”. We now have #QA around all the APIs in public docs to make sure they are always correct

          Along the way we tried other techniques for documenting APIs like ReadMe.io or Swagger UI. These required a lot of effort to customize.

          Writing and maintaining a Postman collection takes some work, but the resulting documentation site, interactivity and API testing tools are well worth it.

          See more
          Simon Reymann
          Senior Fullstack Developer at QUANTUSflow Software GmbH · | 25 upvotes · 2M views

          Our whole Node.js backend stack consists of the following tools:

          • Lerna as a tool for multi package and multi repository management
          • npm as package manager
          • NestJS as Node.js framework
          • TypeScript as programming language
          • ExpressJS as web server
          • Swagger UI for visualizing and interacting with the API’s resources
          • Postman as a tool for API development
          • TypeORM as object relational mapping layer
          • JSON Web Token for access token management

          The main reason we have chosen Node.js over PHP is related to the following artifacts:

          • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
          • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
          • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
          • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
          See more
          Amazon API Gateway logo

          Amazon API Gateway

          1.1K
          824
          41
          Create, publish, maintain, monitor, and secure APIs at any scale
          1.1K
          824
          + 1
          41
          PROS OF AMAZON API GATEWAY
          • 35
            AWS Integration
          • 5
            Websockets
          • 1
            Serverless
          CONS OF AMAZON API GATEWAY
          • 1
            Less expensive
          • 1
            No websocket broadcast

          related Amazon API Gateway posts

          A Luthra
          VP Software Engrg at Reliant · | 2 upvotes · 390.1K views
          Shared insights
          on
          Apigee
          Amazon API Gateway

          Amazon API Gateway vs Apigee. How do they compare as an API Gateway? What is the equivalent functionality, similarities, and differences moving from Apigee API GW to AWS API GW?

          See more
          Insomnia REST Client logo

          Insomnia REST Client

          538
          451
          37
          The most intuitive cross-platform REST API Client 😴
          538
          451
          + 1
          37
          PROS OF INSOMNIA REST CLIENT
          • 15
            Easy to work with
          • 10
            Great user interface
          • 6
            Works with GraphQL
          • 2
            Cross platform, available for Mac, Windows, and Linux
          • 2
            Opensource
          • 2
            Preserves request templates
          • 0
            Vim and Emacs key map
          • 0
            Does not have history feature
          CONS OF INSOMNIA REST CLIENT
          • 2
            Do not store credentials in HTTP
          • 2
            Do not have team sharing options

          related Insomnia REST Client posts

          Jason Barry
          Cofounder at FeaturePeek · | 4 upvotes · 1.9M 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