Best practices for low code development:
- Finalize the domain / entity model early
- Check the capabilities of platform before writing code for any feature
- Learn XPath
- Try to have daily builds, daily demos, daily development goals with short sprints – comes from agile world
- Learn to use the CI/CD and Code management tools of the platform
- Avoid deep linking URLs, avoid page URL altogether if possible
- Check security / roles / entity access settings regularly
- Integrate using in-built tools rather than custom code
- For features like audit, associations, validations try to work at the entity level to start with. Incase you are unable to manage them their then move to workflow level validations
- Understand the limitations of platform and then make appropriate suggestions
- Old components, modules, etc. building up in apps should be cleared regularly
- Check the app stores of the platform for modules that are already available before you build one
- Check added libraries regularly for unused or deprecated / insecure versions
- Scan uploaded files before using
- Try to use architecture / design principles like SOLID in terms of singular responsibility and so on
- Think of SSL, containerization, cloud, kubernetes, automation testing, logging, user interface & licensing in advance and not as a reaction later
Low code has arrived !!!
Topic: “What can Jenkins do for you?” might sound a bit old fashioned and cliched as Jenkins has been around for a while but it has very varied capabilities via plugins & build pipelines to manage many things. Brief list of capabilities which in no way are exhaustive are given below:
- Continuous build management
- Continuous deployment
- Continuous testing
- Continuous quality checks and code scans
- Continuous security testing
- Continous license checks
- Continous Kubernetes, cloud & docker deployment / monitoring
- Continuous email notifications for events
- Integration with JIRA
- Integration with notification systems
- Continuous monitoring
- Continuous reports & test results analysis
Here are some important concepts, documentation and keywords of Kafka that you can refer and learn. There are two major flavors of Kafka – Apache Kafka & Confluent Kafka, I have listed major keywords, documentation and concepts from both here:
- Broker
- Zookeeper
- kSQL
- REST-Proxy
- Schema-Registry
- Connectors
- Operator
- Control Center
- Streams
- Topics
- Consumers
- Producers
- Partitions
- Offset
- Log
- Node
- Replica
- Message
- Leader
- Follower
- Replicator
- Schema management
- Confluent Hub
- Events
- Associated keywords in today’s cloud deployments: Docker containers, Kubernetes, Ansible, Security
Associated documentation:
Ideas on Innovation around Software. We Thrive On Ideas. We are Learner Centered, Open Source & Digital Focused.