Sign up to add or upvote prosMake informed product decisions
Sign up to add or upvote consMake informed product decisions
What is Android SDK?
What is Laravel?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Red Hat, Inc.
I moved from .NET and Rails to Laravel, and since then never thought to go back. I feel Laravel framework has the capability to overcome all modern frameworks.
At Soft Pyramid we are developing rich business applications using Laravel Framework, and never feel any limitation even for complex reporting.We have written REST apis, complex ERP solutions and found awsome in all areas.
I have benchmarked Node.js and other popular frameworks using a real life application example. You can find the results here: https://firstname.lastname@example.org/web-rest-api-benchmark-on-a-real-life-application-ebb743a5d7a3
We decided to move the provisioning process to an API-driven process, and had to decide among a few implementation languages:
- Go, the server-side language from Google
We built prototypes in both languages, and decided on NodeJS:
- NodeJS is asynchronous-by-default, which suited the problem domain. Provisioning is more like “start the job, let me know when you’re done” than a traditional C-style program that’s CPU-bound and needs low-level efficiency.
- NodeJS acts as an HTTP-based service, so exposing the API was trivial
Getting into the headspace and internalizing the assumptions of a tool helps pick the right one. NodeJS assumes services will be non-blocking/event-driven and HTTP-accessible, which snapped into our scenario perfectly. The new NodeJS architecture resulted in a staggering 95% reduction in processing time: requests went from 7.5 seconds to under a second.
The server side of Trello is built in Node.js. We knew we wanted instant propagation of updates, which meant that we needed to be able to hold a lot of open connections, so an event-driven, non-blocking server seemed like a good choice. Node also turned out to be an amazing prototyping tool for a single-page app. The prototype version of the Trello server was really just a library of functions that operated on arrays of Models in the memory of a single Node.js process, and the client simply invoked those functions through a very thin wrapper over a WebSocket. This was a very fast way for us to get started trying things out with Trello and making sure that the design was headed in the right direction. We used the prototype version to manage the development of Trello and other internal projects at Fog Creek.
All backend code is done in node.js
We have a SOA for our systems. It isn't quite Microservices jsut yet, but it does provide domain encapsulation for our systems allowing the leaderboards to fail without affecting the login or education content.
We've written a few internal modules including a very simple api framework.
I don't know how well this will scale if/when I have hundreds of people connected simultaneously, but I suspect that when that time comes, it may be just a matter of increasing the hardware.
Used node.js server as backend. Interacts with MongoDB using MongoSkin package which is a wrapper for the MongoDB node.js driver. It uses express for routing and cors package for enabling cors and eyes package for enhancing readability of logs. Also I use nodemon which takes away the effort to restart the server after making changes.
So we very, very early on, we were iOS only, then we thought, well we’re missing out on half of the market. We need to add Android. So we had a friend of ours start working on the Android app, and I had to build the API for him, but I was having a really hard time doing that because I didn’t know what he needed exactly, so I built the first version of the web store over the weekend because I wanted to have a client to consume myself for the API I was building.
The best PHP framework right now, intuitive and growing up quickly.
We use Laravel in the outer layer of our Clean Architecture codebases, whereby the domain model does not rely on the framework as a whole.
Self taught : acquired knowledge or skill on one's own initiative. Unity and app compatible porposes : software development kit that enables developers to create applications for the Android platform.
See "PHP", I don't really choose to use it, but I can step in and operate in Laravel when necessary. Same goes for quite a few other PHP frameworks, including my own full-featured proprietary stack.
The Android SDK is the key-component of all Android-based development and had to be included in this stack for sure. We work with the SDK through IntelliJ IDEA and the command-line.
An excellent PHP framework employing SOLID principles to rapidly develop web-site systems and connect them to databases. Custom development of admin screens for website management.
A clean, easy to understand, well documented framework with excellent tools and a great community providing every imaginable extension to add functionality to your project.
last time i used the android sdk was converting the tiktok app to ios. what a mess it was back then. the developer nature of the sdk was apparent vs apples offering.
Laravel is the PHP framework we use. It speeds up development and simplifies a lot of PHP. Complicated at first but saves time once you're comfortable with it.