Alternatives to Blade logo
Node.js, ASP.NET, Rails, Django, and Laravel are the most popular alternatives and competitors to Blade.
6
9
+ 1
0

What is Blade?

Blade is a lightweight MVC framework. It is based on the principles of simplicity and elegance.
Blade is a tool in the Frameworks (Full Stack) category of a tech stack.
Blade is an open source tool with 4.9K GitHub stars and 1K GitHub forks. Here’s a link to Blade's open source repository on GitHub

Blade alternatives & related posts

Node.js logo

Node.js

27.9K
21.9K
7.9K
27.9K
21.9K
+ 1
7.9K
A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
Node.js logo
VS
Blade logo
Compare Node.js vs Blade
Node.js logo
Node.js
VS
Blade logo
Blade

related Node.js posts

Nick Parsons
Nick Parsons
Director of Developer Marketing at Stream · | 33 upvotes · 108.6K views
atStreamStream
Go
Go
Stream
Stream
Python
Python
Yarn
Yarn
Babel
Babel
Node.js
Node.js
ES6
ES6
JavaScript
JavaScript
#Languages
#FrameworksFullStack

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
Nick Rockwell
Nick Rockwell
CTO at NY Times · | 26 upvotes · 195.2K views
atThe New York TimesThe New York Times
Apache HTTP Server
Apache HTTP Server
Kafka
Kafka
Node.js
Node.js
GraphQL
GraphQL
Apollo
Apollo
React
React
PHP
PHP
MySQL
MySQL

When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

See more
ASP.NET logo

ASP.NET

12.9K
239
0
12.9K
239
+ 1
0
An open source web framework for building modern web apps and services with .NET
    Be the first to leave a pro
    ASP.NET logo
    VS
    Blade logo
    Compare ASP.NET vs Blade
    ASP.NET logo
    ASP.NET
    VS
    Blade logo
    Blade

    related ASP.NET posts

    Greg Neumann
    Greg Neumann
    Indie, Solo, Developer · | 6 upvotes · 7K views
    TypeScript
    TypeScript
    Vue.js
    Vue.js
    Electron
    Electron
    Quasar Framework
    Quasar Framework
    ASP.NET
    ASP.NET
    Xamarin Forms
    Xamarin Forms
    .NET Core
    .NET Core
    Xamarin
    Xamarin

    Finding the most effective dev stack for a solo developer. Over the past year, I've been looking at many tech stacks that would be 'best' for me, as a solo, indie, developer to deliver a desktop app (Windows & Mac) plus mobile - iOS mainly. Initially, Xamarin started to stand-out. Using .NET Core as the run-time, Xamarin as the native API provider and Xamarin Forms for the UI seemed to solve all issues. But, the cracks soon started to appear. Xamarin Forms is mobile only; the Windows incarnation is different. There is no Mac UI solution (you have to code it natively in Mac OS Storyboard. I was also worried how Xamarin Forms , if I was to use it, was going to cope, in future, with Apple's new SwiftUI and Google's new Fuchsia.

    This plethora of techs for the UI-layer made me reach for the safer waters of using Web-techs for the UI. Lovely! Consistency everywhere (well, mostly). But that consistency evaporates when platform issues are addressed. There are so many web frameworks!

    But, I made a simple decision. It's just me...I am clever, but there is no army of coders here. And I have big plans for a business app. How could just 1 developer go-on to deploy a decent app to Windows, iPhone, iPad & Mac OS? I remembered earlier days when I've used Microsoft's ASP.NET to scaffold - generate - loads of Code for a web-app that I needed for several charities that I worked with. What 'generators' exist that do a lot of the platform-specific rubbish, allow the necessary customisation of such platform integration and provide a decent UI?

    I've placed my colours to the Quasar Framework mast. Oh dear, that means Electron desktop apps doesn't it? Well, Ive had enough of loads of Developers saying that "the menus won't look native" or "it uses too much RAM" and so on. I've been using non-native UI-wrapped apps for ages - the date picker in Outlook on iOS is way better than the native date-picker and I'd been using it for years without getting hot under the collar about it. Developers do get so hung-up on things that busy Users hardly notice; don't you think?. As to the RAM usage issue; that's a bit true. But Users only really notice when an app uses so much RAM that the machine starts to page-out. Electron contributes towards that horizon but does not cause it. My Users will be business-users after all. Somewhat decent machines.

    Looking forward to all that lovely Vue.js around my TypeScript and all those really, really, b e a u t I f u l UI controls of Quasar Framework . Still not sure that 1 dev can deliver all that... but I'm up for trying...

    See more
    ASP.NET
    ASP.NET
    Puppeteer
    Puppeteer
    vuex
    vuex
    ExpressJS
    ExpressJS
    React
    React
    Angular 2
    Angular 2
    Vue.js
    Vue.js
    Netlify
    Netlify
    Heroku
    Heroku
    #Seo
    #Heroku

    I found Heroku to be a great option to get ExpressJS up and running with very little hustle. The free tier is great, but I'd recommend to set up a cronjob to visit your site every few minutes so that the server stays awake. Netlify was the option to host the front-end because doing the server side rendering on #Heroku would have taken a little more time than I'd like to. For the moment pre-rendering the app with prerender-spa-plugin is enough to help with #seo. Puppeteer was my choice over other options because it made it easier to scrape websites made on ASP.NET which is what I needed in this case. And Vue.js is my top choice at the moment because it's really beginner friendly and it has a lot of the features I like about Angular 2 and React. vuex is a must in most of the app I build.

    See more

    related Rails posts

    Zach Holman
    Zach Holman
    at Zach Holman · | 20 upvotes · 135K views
    JavaScript
    JavaScript
    Rails
    Rails
    Apollo
    Apollo
    React
    React

    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
    Julien DeFrance
    Julien DeFrance
    Full Stack Engineering Manager at ValiMail · | 16 upvotes · 171.5K views
    atSmartZipSmartZip
    Amazon DynamoDB
    Amazon DynamoDB
    Ruby
    Ruby
    Node.js
    Node.js
    AWS Lambda
    AWS Lambda
    New Relic
    New Relic
    Amazon Elasticsearch Service
    Amazon Elasticsearch Service
    Elasticsearch
    Elasticsearch
    Superset
    Superset
    Amazon Quicksight
    Amazon Quicksight
    Amazon Redshift
    Amazon Redshift
    Zapier
    Zapier
    Segment
    Segment
    Amazon CloudFront
    Amazon CloudFront
    Memcached
    Memcached
    Amazon ElastiCache
    Amazon ElastiCache
    Amazon RDS for Aurora
    Amazon RDS for Aurora
    MySQL
    MySQL
    Amazon RDS
    Amazon RDS
    Amazon S3
    Amazon S3
    Docker
    Docker
    Capistrano
    Capistrano
    AWS Elastic Beanstalk
    AWS Elastic Beanstalk
    Rails API
    Rails API
    Rails
    Rails
    Algolia
    Algolia

    Back in 2014, I was given an opportunity to re-architect SmartZip Analytics platform, and flagship product: SmartTargeting. This is a SaaS software helping real estate professionals keeping up with their prospects and leads in a given neighborhood/territory, finding out (thanks to predictive analytics) who's the most likely to list/sell their home, and running cross-channel marketing automation against them: direct mail, online ads, email... The company also does provide Data APIs to Enterprise customers.

    I had inherited years and years of technical debt and I knew things had to change radically. The first enabler to this was to make use of the cloud and go with AWS, so we would stop re-inventing the wheel, and build around managed/scalable services.

    For the SaaS product, we kept on working with Rails as this was what my team had the most knowledge in. We've however broken up the monolith and decoupled the front-end application from the backend thanks to the use of Rails API so we'd get independently scalable micro-services from now on.

    Our various applications could now be deployed using AWS Elastic Beanstalk so we wouldn't waste any more efforts writing time-consuming Capistrano deployment scripts for instance. Combined with Docker so our application would run within its own container, independently from the underlying host configuration.

    Storage-wise, we went with Amazon S3 and ditched any pre-existing local or network storage people used to deal with in our legacy systems. On the database side: Amazon RDS / MySQL initially. Ultimately migrated to Amazon RDS for Aurora / MySQL when it got released. Once again, here you need a managed service your cloud provider handles for you.

    Future improvements / technology decisions included:

    Caching: Amazon ElastiCache / Memcached CDN: Amazon CloudFront Systems Integration: Segment / Zapier Data-warehousing: Amazon Redshift BI: Amazon Quicksight / Superset Search: Elasticsearch / Amazon Elasticsearch Service / Algolia Monitoring: New Relic

    As our usage grows, patterns changed, and/or our business needs evolved, my role as Engineering Manager then Director of Engineering was also to ensure my team kept on learning and innovating, while delivering on business value.

    One of these innovations was to get ourselves into Serverless : Adopting AWS Lambda was a big step forward. At the time, only available for Node.js (Not Ruby ) but a great way to handle cost efficiency, unpredictable traffic, sudden bursts of traffic... Ultimately you want the whole chain of services involved in a call to be serverless, and that's when we've started leveraging Amazon DynamoDB on these projects so they'd be fully scalable.

    See more
    Django logo

    Django

    7.3K
    5.1K
    2.8K
    7.3K
    5.1K
    + 1
    2.8K
    The Web framework for perfectionists with deadlines
    Django logo
    VS
    Blade logo
    Compare Django vs Blade
    Django logo
    Django
    VS
    Blade logo
    Blade

    related Django posts

    Dmitry Mukhin
    Dmitry Mukhin
    at Uploadcare · | 22 upvotes · 110.8K views
    atUploadcareUploadcare
    PostCSS
    PostCSS
    Preact
    Preact
    Ember.js
    Ember.js
    React
    React
    Python
    Python
    Django
    Django

    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
    Python
    Python
    Django
    Django
    JavaScript
    JavaScript
    Node.js
    Node.js

    Django or NodeJS? Hi, I’m thinking about which software I should use for my web-app. What about Node.js or Django for the back-end? I want to create an online preparation course for the final school exams in my country. At the beginning for maths. The course should contain tutorials and a lot of exercises of different types. E.g. multiple choice, user text/number input and drawing tasks. The exercises should change (different levels) with the learning progress. Wrong questions should asked again with different numbers. I also want a score system and statistics. So far, I have got only limited web development skills. (some HTML, CSS, Bootstrap and Wordpress). I don’t know JavaScript or Python.

    Possible pros for Python / Django: - easy syntax, easier to learn for me as a beginner - fast development, earlier release - libraries for mathematical and scientific computation

    Possible pros for JavaScript / Node.js: - great performance, better choice for real time applications: user should get the answer for a question quickly

    Which software would you use in my case? Are my arguments for Python/NodeJS right? Which kind of database would you use?

    Thank you for your answer!

    Node.js JavaScript Django Python

    See more

    related Laravel posts

    Epistol
    Epistol
    PHP
    PHP
    Bulma
    Bulma
    Asana
    Asana
    Stripe
    Stripe
    Let's Encrypt
    Let's Encrypt
    CloudFlare
    CloudFlare
    Deployer
    Deployer
    Git
    Git
    GitHub
    GitHub
    Ubuntu
    Ubuntu
    nginx
    nginx
    Buddy
    Buddy
    Webpack
    Webpack
    Vue.js
    Vue.js
    JavaScript
    JavaScript
    HTML5
    HTML5
    Sass
    Sass
    Google Analytics
    Google Analytics
    PhpStorm
    PhpStorm
    Laravel
    Laravel
    #CDG
    CDG

    I use Laravel because it's the most advances PHP framework out there, easy to maintain, easy to upgrade and most of all : easy to get a handle on, and to follow every new technology ! PhpStorm is our main software to code, as of simplicity and full range of tools for a modern application.

    Google Analytics Analytics of course for a tailored analytics, Bulma as an innovative CSS framework, coupled with our Sass (Scss) pre-processor.

    As of more basic stuff, we use HTML5, JavaScript (but with Vue.js too) and Webpack to handle the generation of all this.

    To deploy, we set up Buddy to easily send the updates on our nginx / Ubuntu server, where it will connect to our GitHub Git private repository, pull and do all the operations needed with Deployer .

    CloudFlare ensure the rapidity of distribution of our content, and Let's Encrypt the https certificate that is more than necessary when we'll want to sell some products with our Stripe api calls.

    Asana is here to let us list all the functionalities, possibilities and ideas we want to implement.

    See more
    Antonio Sanchez
    Antonio Sanchez
    CEO at Kokoen GmbH · | 10 upvotes · 56.1K views
    atKokoen GmbHKokoen GmbH
    ExpressJS
    ExpressJS
    Node.js
    Node.js
    JavaScript
    JavaScript
    MongoDB
    MongoDB
    Go
    Go
    MySQL
    MySQL
    Laravel
    Laravel
    PHP
    PHP

    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
    Android SDK logo

    Android SDK

    6.7K
    4.7K
    774
    6.7K
    4.7K
    + 1
    774
    An SDK that provides you the API libraries and developer tools necessary to build, test, and debug apps...
    Android SDK logo
    VS
    Blade logo
    Compare Android SDK vs Blade
    Android SDK logo
    Android SDK
    VS
    Blade logo
    Blade

    related Android SDK posts

    Jesus Dario Rivera Rubio
    Jesus Dario Rivera Rubio
    Telecomm Engineering at Netbeast · | 10 upvotes · 63.2K views
    atNetbeastNetbeast
    Mailjet
    Mailjet
    Intercom
    Intercom
    Amplitude
    Amplitude
    Firebase
    Firebase
    GitHub
    GitHub
    Bitrise
    Bitrise
    Travis CI
    Travis CI
    Objective-C
    Objective-C
    Android SDK
    Android SDK
    React Native
    React Native
    #End2end
    #SmartHome

    We are using React Native in #SmartHome to share the business logic between Android and iOS team and approach users with a unique brand experience. The drawback is that we require lots of native Android SDK and Objective-C modules, so a good part of the invested time is there. The gain for a app that relies less on native communication, sensors and OS tools should be even higher.

    Also it helps us set different testing stages: we use Travis CI for the javascript (business logic), Bitrise to run build tests and @Detox for #end2end automated user tests.

    We use a microservices structure on top of Zeit's @now that read from firebase. We use JWT auth to authenticate requests among services and from users, following GitHub philosophy of using the same infrastructure than its API consumers. Firebase is used mainly as a key-value store between services and as a backup database for users. We also use its authentication mechanisms.

    You can be super locked-in if you also rely on it's analytics, but we use Amplitude for that, which offers us great insights. Intercom for communications with end-user and Mailjet for marketing.

    See more
    Sezgi Uluçam
    Sezgi Uluçam
    Sr. Software Engineer at StackShare · | 6 upvotes · 30K views
    Android SDK
    Android SDK
    Android Studio
    Android Studio
    React Native
    React Native
    Xcode
    Xcode
    Expo
    Expo

    I've recently switched to using Expo for initializing and developing my React Native apps. Compared to React Native CLI, it's so much easier to get set up and going. Setting up and maintaining Android Studio, Android SDK, and virtual devices used to be such a headache. Thanks to Expo, I can now test my apps directly on my Android phone, just by installing the Expo app. I still use Xcode Simulator for iOS testing, since I don't have an iPhone, but that's easy anyway. The big win for me with Expo is ease of Android testing.

    The Expo SDK also provides convenient features like Facebook login, MapView, push notifications, and many others. https://docs.expo.io/versions/v31.0.0/sdk/

    See more
    Spring Boot logo

    Spring Boot

    4K
    3.1K
    477
    4K
    3.1K
    + 1
    477
    Create Spring-powered, production-grade applications and services with absolute minimum fuss
    Spring Boot logo
    VS
    Blade logo
    Compare Spring Boot vs Blade
    Spring Boot logo
    Spring Boot
    VS
    Blade logo
    Blade

    related Spring Boot posts

    Praveen Mooli
    Praveen Mooli
    Technical Leader at Taylor and Francis · | 11 upvotes · 27.7K views
    Amazon S3
    Amazon S3
    Amazon DynamoDB
    Amazon DynamoDB
    Amazon RDS
    Amazon RDS
    Serverless
    Serverless
    Docker
    Docker
    Terraform
    Terraform
    Travis CI
    Travis CI
    GitHub
    GitHub
    RxJS
    RxJS
    Angular 2
    Angular 2
    AWS Lambda
    AWS Lambda
    Amazon SQS
    Amazon SQS
    Amazon SNS
    Amazon SNS
    Amazon Kinesis Firehose
    Amazon Kinesis Firehose
    Amazon Kinesis
    Amazon Kinesis
    Flask
    Flask
    Python
    Python
    ExpressJS
    ExpressJS
    Node.js
    Node.js
    Spring Boot
    Spring Boot
    Java
    Java
    #Devops
    #Webapps
    #Eventsourcingframework
    #Microservices
    #Backend

    We are in the process of building a modern content platform to deliver our content through various channels. We decided to go with Microservices architecture as we wanted scale. Microservice architecture style is an approach to developing an application as a suite of small independently deployable services built around specific business capabilities. You can gain modularity, extensive parallelism and cost-effective scaling by deploying services across many distributed servers. Microservices modularity facilitates independent updates/deployments, and helps to avoid single point of failure, which can help prevent large-scale outages. We also decided to use Event Driven Architecture pattern which is a popular distributed asynchronous architecture pattern used to produce highly scalable applications. The event-driven architecture is made up of highly decoupled, single-purpose event processing components that asynchronously receive and process events.

    To build our #Backend capabilities we decided to use the following: 1. #Microservices - Java with Spring Boot , Node.js with ExpressJS and Python with Flask 2. #Eventsourcingframework - Amazon Kinesis , Amazon Kinesis Firehose , Amazon SNS , Amazon SQS, AWS Lambda , Amazon RDS , Amazon DynamoDB , Amazon S3

    To build #Webapps we decided to use Angular 2 with RxJS

    #Devops Tools - GitHub , Travis CI , Terraform , Docker , Serverless

    See more
    IntelliJ IDEA
    IntelliJ IDEA
    Linux
    Linux
    GitHub
    GitHub
    MongoDB
    MongoDB
    Kafka
    Kafka
    RabbitMQ
    RabbitMQ
    Redis
    Redis
    MySQL
    MySQL
    Elasticsearch
    Elasticsearch
    Spring Cloud
    Spring Cloud
    Spring Boot
    Spring Boot

    Spring-Boot Spring Cloud Elasticsearch MySQL Redis RabbitMQ Kafka MongoDB GitHub Linux IntelliJ IDEA

    See more
    .NET logo

    .NET

    3.8K
    2K
    1.4K
    3.8K
    2K
    + 1
    1.4K
    A free, cross-platform, open source developer platform for building many different types of applications.
    .NET logo
    VS
    Blade logo
    Compare .NET vs Blade
    .NET logo
    .NET
    VS
    Blade logo
    Blade

    related .NET posts

    John-Daniel Trask
    John-Daniel Trask
    Co-founder & CEO at Raygun · | 23 upvotes · 54K views
    atRaygunRaygun
    .NET
    .NET
    Node.js
    Node.js
    #FrameworksFullStack
    #Languages

    The core Web application of Raygun is still a Microsoft ASP.NET MVC application. Not too much has changed from a fundamental technology standpoint. We originally built using Mono, which just bled memory and would need to be constantly recycled. So we looked around at the options and what would be well suited to the highly transactional nature of our API. We settled on Node.js, feeling that the event loop model worked well given the lightweight workload of each message being processed. This served us well for several years.

    When we started to look at .NET Core in early 2016, it became quite obvious that being able to asynchronously hand off to our queuing service greatly improved throughput. Unfortunately, at the time, Node.js didn’t provide an easy mechanism to do this, while .NET Core had great concurrency capabilities from day one. This meant that our servers spent less time blocking on the hand off, and could start processing the next inbound message. This was the core component of the performance improvement.

    We chose .NET because it was a platform that our team was familiar with. Also we were skilled enough with it to know many performance tips and tricks to get the most from it. Due to this experience, it helped us get to market faster and deliver great performance.

    #Languages #FrameworksFullStack

    See more
    Spenser Coke
    Spenser Coke
    Product Engineer at Loanlink.de · | 8 upvotes · 98.5K views
    atLoanlink GmbhLoanlink Gmbh
    HTML5
    HTML5
    Vue.js
    Vue.js
    Google Drive
    Google Drive
    Mailchimp
    Mailchimp
    Zapier
    Zapier
    Trello
    Trello
    GitHub
    GitHub
    React
    React
    Node.js
    Node.js
    .NET
    .NET
    AngularJS
    AngularJS
    Rails
    Rails

    When starting a new company and building a new product w/ limited engineering we chose to optimize for expertise and rapid development, landing on Rails API, w/ AngularJS on the front.

    The reality is that we're building a CRUD app, so we considered going w/ vanilla Rails MVC to optimize velocity early on (it may not be sexy, but it gets the job done). Instead, we opted to split the codebase to allow for a richer front-end experience, focus on skill specificity when hiring, and give us the flexibility to be consumed by multiple clients in the future.

    We also considered .NET core or Node.js for the API layer, and React on the front-end, but our experiences dealing with mature Node APIs and the rapid-fire changes that comes with state management in React-land put us off, given our level of experience with those tools.

    We're using GitHub and Trello to track issues and projects, and a plethora of other tools to help the operational team, like Zapier, MailChimp, Google Drive with some basic Vue.js & HTML5 apps for smaller internal-facing web projects.

    See more

    related CodeIgniter posts

    Saikat Chakrabortty
    Saikat Chakrabortty
    Software Engineer · | 1 upvotes · 1.3K views
    CodeIgniter
    CodeIgniter
    Laravel
    Laravel
    PHP
    PHP

    I have used PHP to do end to end developments , using Laravel CodeIgniter frameworks.

    See more

    related Symfony posts

    Benjamin Bernard-Bouissières
    Benjamin Bernard-Bouissières
    Web Developer at ipexia · | 11 upvotes · 12.8K views
    atipexiaipexia
    PythonAnywhere
    PythonAnywhere
    Symfony
    Symfony
    Python
    Python
    Django
    Django

    I really love Django because it is really fast to create a web application from scratch and it has a lot a facilities like the ORM or the Admin module ! The Python language is really easy to read and powerful, that's why I prefer Django over Symfony.

    I use Django at work to make tools for the technicians but I also use it for me to build my personal website which I host on PythonAnywhere.

    See more
    Samuel Webster
    Samuel Webster
    Principal Developer at Colart · | 6 upvotes · 14.9K views
    WordPress
    WordPress
    RabbitMQ
    RabbitMQ
    Symfony
    Symfony
    WooCommerce
    WooCommerce
    #Pim

    We needed our e-commerce platform (built using WooCommerce) to be able to keep products in sync with our #pim (provided by #akeneo) which is built in Symfony . We hooked into the kernel.event_listener to send RabbitMQ messages to a WordPress API endpoint that triggers the updated product to rebuild with fresh data.

    See more
    Spring logo

    Spring

    1.8K
    1.5K
    938
    1.8K
    1.5K
    + 1
    938
    Provides a comprehensive programming and configuration model for modern Java-based enterprise applications
    Spring logo
    VS
    Blade logo
    Compare Spring vs Blade
    Spring logo
    Spring
    VS
    Blade logo
    Blade

    related Spring posts

    Slack
    Slack
    IntelliJ IDEA
    IntelliJ IDEA
    Java
    Java
    Spring Boot
    Spring Boot
    Spring
    Spring

    Spring Spring-Boot Java IntelliJ IDEA Slack

    See more
    Meteor logo

    Meteor

    1.4K
    1.1K
    1.7K
    1.4K
    1.1K
    + 1
    1.7K
    An ultra-simple, database-everywhere, data-on-the-wire, pure-Javascript web framework