What is Apigility and what are its top alternatives?
Top Alternatives to Apigility
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. ...
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. ...
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. ...
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. ...
Make your code flexible and robust, using the dependency injection container of your choice. ...
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 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 is a powerful REST API Client with cookie management, environment variables, code generation, and authentication for Mac, Window, and Linux. ...
Apigility alternatives & related posts
- Open source21
- Restful & fast framework8
- Easy Setup, Great Documentation7
- Good document to upgrade from previous version5
- Clear and straightforward5
related Slim posts
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
- Open source12
- Restful & fast framework10
- Illuminate support7
- Brother of laravel and fast4
- Easy to learn4
- Not fast3
- Not fast with MongoDB1
related Lumen posts
This is my stack in Application & Data
My Utilities Tools
Google Analytics Postman Elasticsearch
My Devops Tools
Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack
My Business Tools
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.
- Clean architecture507
- Growing community369
- Composer friendly343
- Open source317
- The only framework to consider for php298
- Quickly develop191
- Dependency injection157
- Application architecture145
- Embraces good community packages131
- Write less, do more60
- Restful routing54
- Orm (eloquent)48
- Artisan scaffolding and migrations45
- Database migrations & seeds44
- Great documentation33
- Promotes elegant coding25
- Awsome, Powerfull, Fast and Rapid25
- Build Apps faster, easier and better24
- JSON friendly22
- Easy to learn, scalability22
- Eloquent ORM21
- Most easy for me21
- Modern PHP20
- Blade Template18
- Based on SOLID12
- Clean Documentation11
- Convention over Configuration10
- Easy to attach Middleware10
- Easy Request Validatin9
- Laravel + Cassandra = Killer Framework8
- Get going quickly straight out of the box. BYOKDM8
- Its just wow8
- Easy to use8
- Less dependencies7
- Simplistic , easy and faster7
- Super easy and powerful7
- Friendly API7
- Its beautiful to code in6
- Great customer support6
- The only "cons" is wrong! No static method just Facades5
- Fast and Clarify framework5
- Active Record5
- Easy views handling and great ORM4
- Minimum system requirements4
- Laravel Mix4
- Laravel Spark3
- Laravel Nova3
- Laravel casher3
- Laravel Passport3
- Laravel Horizon and Telescope3
- Laravel Forge and Envoy3
- Cashier with Braintree and Stripe3
- Ease of use3
- Intuitive usage3
- Like heart beat2
- Rapid development2
- Laravel love live long2
- Touch heart artisan2
- Heart touch2
- Too many dependency28
- Slower than the other two20
- A lot of static method calls for convenience16
- Too many include13
- Does not work well for file uploads in Shared Hosting4
- Too underrated3
- Not fast with MongoDB2
- Difficult to learn1
- Not using SOLID principles1
related Laravel posts
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.
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
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.
- Open source1
- Easy to use1
- Automated api-docs1
related API Platform posts
related Expressive posts
- Easy to use484
- Great tool368
- Makes developing rest api's easy peasy275
- Easy setup, looks good155
- The best api workflow out there143
- It's the best53
- History feature53
- Adds real value to my workflow44
- Great interface that magically predicts your needs42
- The best in class app34
- Can save and share script11
- Fully featured without looking cluttered9
- Global/Environment Variables7
- Option to run scrips7
- Shareable Collections6
- Dead simple and useful. Excellent6
- Dark theme easy on the eyes6
- Awesome customer support5
- Great integration with newman5
- The test script is useful4
- Makes testing API's as easy as 1,2,33
- Easy as pie3
- Saves responses3
- This has simplified my testing significantly3
- Mocking API calls with predefined response2
- I'd recommend it to everyone who works with apis2
- Easy to setup, test and provides test storage1
- Continuous integration using newman1
- Pre-request Script and Test attributes are invaluable1
- Postman Runner CI Integration1
- Now supports GraphQL1
- <a href="http://fixbit.com/">useful tool</a>0
- Stores credentials in HTTP9
- Bloated features and UI7
- Poor GraphQL support7
- Cumbersome to switch authentication tokens6
- Can't prompt for per-request variables1
- Import curl1
- Support websocket1
- Import swagger1
related Postman posts
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
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.
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:
- 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.
- AWS Integration35
- Less expensive1
- No websocket broadcast1
related Amazon API Gateway posts
- Easy to work with15
- Great user interface10
- Works with GraphQL6
- Cross platform, available for Mac, Windows, and Linux2
- Preserves request templates2
- Vim and Emacs key map0
- Does not have history feature0
- Do not store credentials in HTTP2
- Do not have team sharing options2
related Insomnia REST Client posts
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.