We want to keep our private artifacts private, making sure that only people with appropriate rights have an access to them. AWS S3 is a good candidate to consume and deploy such artifacts.
I started school when I was 6 years old, in 1996. I saw the very first computer in my life in 2002. I’ve managed to buy myself my own Pentium 3 in 2004, at the age of 14. In fact, I was one of the luckies back then in Armenia who had a personal computer. The internet connection with 100MB monthly limit gave me a chance to know about the amazing world of computer science, in fact that was the time I decided to become a programmer.
JDK9 is on its way. Meanwhile, the early access version is available for playing around and experimenting.
I guess we all have experienced a job change at least once. There might be different reasons to change the job; new opportunities, better salary, problems with coworkers and so on. I call it a trigger of a change. When it triggers, it’s hard to stop and there are two possible scenarios afterwards
One of the important design decisions while building a RESTful API is to decide which HTTP Status to return. In theory, this should be easy, because there is a clear specification which describes each and every HTTP Status, so all is needed is to go through the protocol and find a status appropriate for the specific resource.