How Do Cloud Developers Know When an App is "Done"? (JavaOne 2014)
Join the DZone community and get the full member experience.Join For Free
This slideshow from a recent JavaOne session by Daniel Bryant was posted that elaborates on some of the obstacles for developing in the cloud. Bryant is a principal consultant at OpenCredo, and he has a lot to say about cloud development, useful tools, and helpful techniques. Right out the gate he identifies some of the problems in not respecting the underlying environment, a lack of application/platform monitoring, bizarre failure nodes, difficulty understanding the architecture, and not testing in the cloud.
A core focus of Bryant's session was the creation of a cloud development checklist that centers on the principles of "DHARMA:"
- Highly cohesive/loosely coupled
- Automated from commit to cloud
- Resource aware
- Monitored thoroughly
You can see the full slideshow below.
Opinions expressed by DZone contributors are their own.
Automating the Migration From JS to TS for the ZK Framework
How To Use Geo-Partitioning to Comply With Data Regulations and Deliver Low Latency Globally
Revolutionizing Algorithmic Trading: The Power of Reinforcement Learning
Replacing Apache Hive, Elasticsearch, and PostgreSQL With Apache Doris