Unfortunately we reached the point of low noise, high productivity. Now you could fully focus on domain logic and start implementing client's use cases with the very first line of code. Sounds good, but is really boring.
These rules make your daily developer live more exciting:
- Forget for a moment the nonfunctional requirements and the users. Focus on infrastructure.
- Wisely assume your in-house application has similar nonfunctional requirements as Netflix, Twitter, Facebook or Google have. One day you will surely achieve their scale.
- Justified by 2. ignore existing Java 8 and Java EE functionality. Use third party libraries and frameworks on top of existing functionality.
- Start with implementing infrastructural frameworks first. Implementing logging, configuration, asynchronous communication, caching and discovery frameworks is a good place to start.
- Fat WARs are recognized as common microservice best practice. Don't stop adding external dependencies until the size of the WAR reaches at least 20 MB. Anything below that size does not look serious.
- Write reflection test utilities to maximize code coverage. Now you can easily achieve > 50% code coverage without writing a single assert.
- Complain about high complexity, defects, slow deployments and bloat.
- Suggest to start over with
node.js, but follow the rules. Start with 1.
Cloudy Jakarta EE and MicroProfile: Microservices, Clouds and Beyond Jakarta EE / MicroProfile airhacks workshops at MUC airport, Winter Edition
airhacks.fm the podcast:
Stay in touch: airhacks.news.