I had an unproductive day yesterday!
I did nothing, but slept through most of the day. And then late night this next challenge of deploying the hush-hush java app over the cloud started to bother me.(afterall it was not a totally unproductive day, thinking wise!)
Then yesterday happened, and then it clicked:: we Java devs(web ones, not hard core jdk ones) are orchestrating everything in lifecycle of what Elon Musk is trying to do!
Here is the analogy(it can be extended wonderfully!):
- The WAR(Web ARchieve)(sorry, I am old fashioned) is like the unmanned space ship.
- The dev JVM is like simulated Mars environment.
- The cloud is the SPACE where the bits travel to-and-fro in form of data/packets.
- The machine IP Address is like the lat/long of where you want to deploy.
So my current app is in its final integraton phase(hush-hush…) and I am trying to accomplish Slide Driven Development.(nice term!).
Slice Driven Development :: A development approach where a feature/flow is shipped to staging environment as soon as it becomes usable.
Currently I(with @explorer) are trying to integrate all features/flow of the hush-hush app, While I am totally unsure/unaware how it will behave when deployed on staging/production environment. Therefore, I had come up with this approach :: The momemt a feature becomes bug-discoverable, it ought be shipped so that:
- Move to the next flow..
- Bugs can be quashed..
- (most imp)Our path of going from dev–>staging–>production for any feature should be seamless and smooth like skating on butter!
And then, a Eureka moment happened!! And this blog post came about!
Your Takeaway: If you are on a team working with Elon Musk(or anyone trying to transport stuff from place X to place Y, in an unsure environment), you can leverage from the experience of thousand if not millions of deployments of web java developers trying to deploy WAR file formats from local dev JVM to production JVM.
We know the nuances of this lifecycle!
It might save you some time! 🙂