We’ve set up a simple Node.js application called codefish which contains some Jasmine specs. We’ll use screenshots of this application in this blog post. If you haven’t got your own project to set up but you want to follow along on your computer, just fork the repository.
An actual deployment of a network requires attachment to things that are not pristine. It needs to be attached to existing cabling. It needs to interact with other network equipment, from other vendors. It will have servers, storage and in a campus setting wireless access points, PCs, VoIP phones, printers, etc.
During our lab, we wanted to implement an application with Akka and Scala, because we’re going to evaluate highly performing and scalable software architectures on the JVM. I
I still remember my first early forays into using vagrant and puppet together to provision local development environments. Everything was easy accept figuring out a proper way to bundle puppet modules with a project. Basically it was a three step phase of discovery.
Make sure you didn't miss anything with this list of the Best of the Week in the DevOps Zone (Apr. 18 to Apr. 24). This week's topics include the a article from the DZone lead research analyst on CD and automation, loading classes from modules, clojure, TDD and rails, and Linux config version control.
A summarized view (notes) of the Stateless EJB pooling and life-cycle. Useful for newbies
Java 8 comes with a new Optional type, similar to what is available in other languages. This post will go over how this new type is meant to be used, namely what is it's main use case.
Last week we added a new feature to the Eclipse Project Management Infrastructure: we automatically generate a bug list for each release. The bug list is generated by matching the “target milestones” from Bugzilla to the name of the release record.
During a recent discussion with a group of experienced Devops practitioners, we came up with the following "taxonomy" for the service delivery part of the Devops tooling landscape:
Static code analyzer now become very common and useful while teams will be working specially using RAD. As to meet close deadlines and sprint dates developers usually get out of the right path and use some narrow tactics to accomplish some task.
Maybe Rails apps are too sophisticated in terms of coding constructs to be easily and cheaply test driven. At least compared to Java. Maybe frameworks are harder to TDD too, compared to libraries. Refactoring, in tools like Intellij for Java, is like giving the Mona-Lisa a proper smile with your fingers, hundreds of years after the last brush stroke, and perfectly. Not only that, but Intellij’s local-history undo is perfect too. Don’t like that smile? Hit Ctrl-Z.
David talks about the future DevOps educational programs validating the importance of the movement. He also speculates on future computing trends in storage and security based on past market patterns giving examples of how we need to reimagine problems as technology improves and internet bandwidth grows.
The only value you get while writing a test, is when the code is not there yet. That’s right, in TDD. In that case, you get all of the above, plus insight about the design and safe incremental progress. If your test passes the FAIL test, then it is a unit test.
There's a new feature in Java 8 called the Optional class which is supposed to cure NullPointerExceptions. The catch with this new Optional class is of course the word "class". Optional is only a wrapper that contains a reference to some other object and isn't close to being a panacea for NullPointerExceptions.
Spring Boot is a brand new application framework from Spring. It allows fabulously quick development and rapid prototyping (even including CLI).
Many continuous delivery concepts are most applicable for software that is running on your own servers whether as part of a website, internal application or SaaS offering. For teams who write products that are installed by their customers, some continuous delivery concepts are hard to implement.
here is a lot of talk in the devops community about the importance of sharing principles and values, and about silo busting: breaking down the “wall of confusion” between developers and operations to create agile, cross-functional teams.
There is an ongoing discussion about TDD and Rails. It was recently
heated by some some of the DHH statements in his RailsConf keynote and
in the blog post: http://david.heinemeierhansson.com/2014/tdd-is-dead-long-live-testing.html
One aspect of...
About the flamed debate around the death of TDD and why it isn't an excuse for not doing automated testing
Having written the code and the tests, and being fairly certain it’ll work the next and final step is to package the whole thing up and deploy it to a production machine.
Every week here and in our newsletter, we feature a new developer/blogger from the DZone community to catch up and find out what he or she is working on now and what's coming next. This week we're talking to Dustin Marx, software developer, writer, and presenter.
Entrepreneur, researcher, and author, Gene Kim, took some time to sit down with Rajat Bhargava, CEO of JumpCloud, to discuss different aspects of high-performing technology organizations he has been studying for over a decade.
I had a problem writing to the cache directory in my vagrant project due to file permissions. Fortunately Jeremy Kendall has already solved this problem in his Vagrant Synced Folders Permissions article.
Tony Hoare called the invention of the null reference the “billion dollars mistake”. May be the use of primitives in Java could be called the million dollars mistake.
The best piece of advice to about using Infrastructure as Code is to stay connected to the vast community of innovative developers. If your systems remain open to the rapid changes in that community, you’ll be able to share and benefit from the cutting-edge ideas that will make your organization successful.