Industry standard usually only gets you so far. You still have to answer a lot of questions specific to your app/organization/workflow imo.
Also it's fun when you strictly adhere to industry standard and 2 years later the big players are putting out talks about how bad that approach is. Prime example: half my books seem to think an API Gateway is some kind of an anti-pattern. While the other half think it's great:
https://medium.com/paypal-engineerin...y-2c18849ab3e2
Lol dude -
orchestration isn't cool. It's all about
choreography now.
I just read a bunch of microservices books and other than "Keep microservices small and don't share a DB" - I couldn't tell you what industry standard is. Even less so with Lambda - which makes it a lot more fun to develop in.
The current industry standard for node seems to be an awful typescript-express app with one layer for back end services and at least one for route-handling - in a many to many relationship. And maybe a models directory thrown in to gunk things up and make it even more like a Spring app or something. Bleh.
I much prefer a flat component-based structure where pretty much all the business logic is in one route-handler - and just use low-level supporting libs. No models and definitely no stickiness with the front end.
Correction: the awful typescript thing might not exactly be an industry standard. But if you're a Java dev looking to get started, it's probably the one that will appeal to you. Which is another potential downfall in that deciding what is and is not the "industry standard" could leave room for a lot of implicit bias.
Last edited by suzzer99; 12-05-2018 at 11:37 AM.