HN user

LeZuse

89 karma

[ my public key: https://keybase.io/zuse; my proof: https://keybase.io/zuse/sigs/O-eqa3jAIMdutY8jC2DIKsHtO-jvIdp8M66qe-diCNs ]

Posts3
Comments11
View on HN

There are so many misconceptions about what microservices are or what problems they are trying to solve. Most people don't even experience the problems (yet or ever) they are meant to solve and they go straight to micro. 5 person teams making 5 services to power their product :faceplam:. A relatively simple b2b web application without any serious traffic also does not need microservices to handle its load.

People just read up on whatever seems to be the newest, coolest thing. The issue is that MS articles are usually coming from FAANG/ex-FANNG. These companies are solving problems that 99% of others do not.

As engineers we should be looking for the most effective solutions to a given business problem. Sadly, I see engineers with senior/staff titles just throwing cool tech terms/libs around. Boring tech club ftw

I also recommend Zach's presensation https://speakerdeck.com/holman/how-github-uses-github-to-bui... [selfpromo:] When we were thinking about deploying our frontend builds, we got inspired by Ember's CLI Deploy pipeline (http://blog.firstiwaslike.com/deploying-ember-cli-apps/) and we've built something similar for our Webpack based app (https://github.com/productboard/webpack-deploy). Together with Git flow methodology we basically removed all friction from deploying new versions. Would love to hear your thoughts!

LayerVault is a great tool if you want to keep your design files version controlled and nicely organized, which is the primary function. They have also introduced a handoff feature (http://layervault.tumblr.com/post/82302518939/introducing-as...) that is somewhat closer to Avocode. But Avocode aims to be your tool of choice when it comes to designer->developer interaction and VICE VERSA. Many services often forget those developers who must code the same parts over and over again.