Ask HN: What is the future of back-end development?

Post by [deleted] » Fri, Aug 12, 2016, 12:02 PM UTC

tzakrajs wrote: post #30

I had this long rant, then I deleted it because I realized I misunderstood you. Another attempt: The vast majority of compute will live in the datacenter for the next 30 years bc quantum computers require superconductivity. That compute will become like a common utility and will most certainly be used to power the APIs that consumer electronics call. The P2P adds unnecessary complexity when client/server, a simpler s…

Post by rimantas » Fri, Aug 12, 2016, 12:03 PM UTC

digitalarborist wrote: post #24

mrweasel wrote: post #9

The ability to build a solid backend platform and infrastructure is going to be increasingly important in the future. The "backend" is becoming increasingly anonymous (as in not seen, not as in privacy), but it has never been more important. If nothing else the increasing focus on data collection and processing will push the need for custom backend forward for many years. Any every application that needs to store or…

I don't think custom backends are going away either, I do think it will become way less prevalent then it is today though, similarly how all programs used to do manual memory management, this hasn't gone away but most programmers now rely on garbage collection. So much of backend work is redundant, login, user info management, allowing the creation of groups of users, user following, user data uploading or sharing. N…

Post by mrweasel » Fri, Aug 12, 2016, 12:05 PM UTC

digitalarborist wrote: post #24

mrweasel wrote: post #9

The ability to build a solid backend platform and infrastructure is going to be increasingly important in the future. The "backend" is becoming increasingly anonymous (as in not seen, not as in privacy), but it has never been more important. If nothing else the increasing focus on data collection and processing will push the need for custom backend forward for many years. Any every application that needs to store or…

I don't think custom backends are going away either, I do think it will become way less prevalent then it is today though, similarly how all programs used to do manual memory management, this hasn't gone away but most programmers now rely on garbage collection. So much of backend work is redundant, login, user info management, allowing the creation of groups of users, user following, user data uploading or sharing. N…

Post by douche » Fri, Aug 12, 2016, 12:07 PM UTC

caseymarquis wrote: post #31

douche wrote: post #19

Earlier quoted context omitted.

It's the classic "Can't you just add another checkbox here?" situation. Yes, I can add a checkbox there. But I have to add the code to include that setting in the API that the front-end calls, to give you a way to retrieve it and change it. Then I have to add code to the data access layer for this new setting. Then I have to write the SQL scripts to add columns/tables for this new setting, as well as change scripts t…

Sounds like your framework sucks. With an orm and some sort of json serialization that's literally just: Put bagel in toaster. Update the db model. Add a migration. Update the viewmodel db model translation in relevant requests. Get bagel and butter it. Commit. Test the migration on a staging db if feeling paranoid, cause it's just adding a column. Push to master. Update production. Take last bite of bagel. If you ar…

Post by blowski » Fri, Aug 12, 2016, 12:09 PM UTC

mabbo wrote: post #21

Some people don't like the word much, but "serverless" is going to become a bigger deal. You'll write your code, complex or simple; you'll hand it off to some cloud system; you'll write a bit of configuration; you're done. Likely the configuration part will become less and less required. You won't think about hardware, scaling, load balancing, etc, it will just happen for you. The data store being used will be abstra…