You might not have required rights to read this.
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! 🙂
If you are being tailgated, we recommend you follow this approach to come out of that situation!
Go Absolutely Slow!
YES, surprisingly it works out just fine!
Purpose: To know who is tail-gating you AND Why?
How it works?
- If the vehicle following you sees you slowing down, they will have no choice to speed up (which means they were not following you) or look-you-in-the-eye. (either ways, the problem is solved!)
Benefits of slowing down…
- By slowing down, you opened an opportunity to talk.. Human Connect!
- By slowing down, maybe you can have a running conversation, you are driving + talking(giving direction who knows). Saves time!
- By slowing down, you saved lifes! No stats but still true!
- By slowing down, You enjoy the road-side scenary. (remember enjoy the journey not just the destination!)
- By slowing down, You literally look the problem in the eye than running away from it.
There goes, we have the Slow Moving Manifesto!
Credits: Smita, Rachit + (KennyG played in our neighbouring park @ 1000 hrs) 🙂
Couple of days back, 21-October-2016 everyone connected on the web experienced sluggishness in connecting to the normal sites and saw obstruction in their regular works.
The scenario can be visually described as follows:
Incase you might be wondering why this attack happened now, the internet is way mature, why can’t it protect itself from such attacks?
Well, then do read on…
From an ideal perspective the players in the attack are listed:
- Users of the web (us) (attackers and victims)
- ISP’s (medium through which attack was carried out)
- Device Manufacturers (Things, which got compromised — zombies)
- Regulatory Organizations (They are mostly sleeping or doing other important silly stuff, lets leave them out of this discussion)
Let us look at those questions asked earlier and more:
What is dDos?
It stands for distributed Denial of Service. Consider your regular pesky thing that you have to do and can’t live without?(siblings,kids,neighbours.. anyhuman thing). They come nagging to you, you can handle it but maybe 10 requests in a day a max! The 11th request from that pesky thing will get a denial of service response!(simply a No!)
Now,Imagine yourself at a play house. And you are already having a minor headache(it was Friday, everyone was in the mood to relax). Multiply your single pesky thing with say 10, you are bombarded with pesky request from everywhere, what will happen to you? You might handle say 20 requests at that moment, looking at the situation, but a time will come soon where you will get exhausted and simply stop responding to important requests of like : open the door, and you are standing still!
You just got dDos’ed 🙂
Can you explain it in layman’s terms?
Here is the wikipedia entry.
I still did not get it..
Why this attack happened now?
It was waiting to happen, its like too many cooks, spoil the broth kinda scenario. Lot of unpatched/sloppy devices connected to the internet working for you and they all had a common zombie entry point, that simply got activated!
The internet is way mature, why can’t it protect itself from such attacks?
I am sure there are some orgn that were actually fighting this menace! Imagine a hospital unable to get reports of a patient in critical condition!So I am pretty sure what got reported and what actually got fixed and treated is somewhat different. So the internet is not at all mature, we are still not ready to have our life depend on it, our livelihood might depend on it but not life!So some orgn might be involved (even now) preventing many such attacks to keep the internet working, and some sleeping regulations might have also protected and saved us from a much more severe attack!
The rules are pretty simple, everyone is united on this matter and no one likes a dDos attack to happen! It actually interrupts normal/perceived flow of life on a day-to-day basis.
So basically its the attackers who (misued?) a compromised device and affected the network. Its pretty clear, there is something that needs to be fixed/controlled in the wild. And its not impossible..
Onto the solution then, shall we proceed?
Two parts solution can be proposed:
- Regulation. In an ideal world, regulation is already in place and device manufacturers are supposed to follow them and hence they are able to sell their products. So something stronger needs to be put in place for regulation. Say if a device is an IoT kinda device, then as per regulation it should be allowed to use 5% of the bandwidth. If its a phone or a computer, then it will not have such a restriction, or maybe it can have!
- ISP Level Quota Software. ISP’s would want to pitch in this idea, where a custom configuration software would be installed at per user site and there based on the MAC address the bandwidth quotas can be defined. Say you got a new IoT device for your home, you will get to configure and set a max bandwidth that device is allowed to consume on your home network.
There was once a log, ready to have a meeting with the Sculptor, getting ready for the grind!
Casually it approached the scene, not knowing what is to happen to it next,
Waiting to see who/what is the Sculptor is and what can he do for it?
Seeing a couple of wasted logs around the scene, it could not resist but ask their state!
They said in chorus – “One word, Do as the sculptor says” as they were tossed out of the view.
“Ahh, What could the Sculptor ask me to do” was the only thought pacing up and down the log’s mind!
And the moment of the log’s meeting arrived…
Placed in the hands of the Sculptor, the log could not giggle profusely!
And then.. Bam! Sculptor’s chisel tore apart a big chunk from the log.
And the log screamed to the Sculptor, “What are you doing, please stop”
The Sculptor stopped, and asked whether the this log did not have a chatter with other logs?
The log said, “They said only-to listen to you,they did not tell you’ll make me undergo this chisel”
The Sculptor looked clueless, and the log asked itself to be excused.
After some time of pondering…
The log thought of going through the process as one strike a day…
And the deal was made…
Days,Weeks,Months passed and the log took the blow daily and frowned and complained..
And then one fine day, the Sculptor said to the log, I’m done with you.
And then the sculpted-log was moved to a different place — not knowing where and for what, it cooperated!
A few days later…
The log was placed at a higher platform, and then by chance it got to see itself in a mirror!
And it could not believe what it could see — A beautiful deity crossed its sight.
Not believing that was It, the log waited for another such day and then the belief was confirmed.
The log had a good after thought..
All the suffering, the chiseling, was given to it for its shaping.
Had it complained and not gone through the grind, it might have become another wasted log…
Thanking the Sculptor, (and the wasted logs for the advice), for his efforts, it just smiled.
(This post is inspired from a story over-heard — all images are googled, no claim on ownership)