How To Write A Dead-Simple Online Network Drive using Java & WebDAV | North Concepts There are a variety of ways you can enhance your application with WebDAV access which we will be going into in a latter part of the WebDAV series. For now we will show you how to create a basic online network drive using WebDAV via Milton, a Java WebDAV Server library. Example We will write the logic to create a network drive containing just one file, scratchpad.txt, which can be modified at will from any location where the drive is mounted. You may want to load the project into your IDE so that you can follow along. Step 1: Create The Domain Object This is a simple POJO which will allow us to hold some text and attributes which will nicely represent a virtual scratchpad.txt file. Step 2: Create The Equivalent Resource Class As A Composition In this step, we have created a class with a “has-a” relationship with the original domain object. To keep the file-structure analogy going, we should have a root folder to contain our one file. That’s it! Concluding Thoughts Download
Mina Mina lets you build and run scripts to manage your app deployments on servers via SSH. $ gem install mina $ mina Really bloody fast Mina works really fast because it’s a deploy Bash script generator. $ mina deploy --verbose -----> Creating the build path $ mkdir tmp/build-128293482394 -----> Cloning the Git repository $ git clone . Compare this to the likes of Vlad or Capistrano, where each command is ran separately on their own SSH sessions. See the deploying guide for more information. Incredibly customizable All your settings are stored in a Ruby file config/deploy.rb. config/deploy.rb require 'mina/git' require 'mina/bundler' set :domain, 'your.server.com' set :user, 'flipstack' set :repository, 'flipstack' task :deploy do deploy do # Preparations here invoke :'git:clone' invoke :'bundle:install' endend task :restart do queue 'sudo service restart apache'end In this file, you will define tasks that queue up commands to be ran remotely via SSH.
Microservices "Microservices" - yet another new term on the crowded streets of software architecture. Although our natural inclination is to pass such things by with a contemptuous glance, this bit of terminology describes a style of software systems that we are finding more and more appealing. We've seen many projects use this style in the last few years, and results so far have been positive, so much so that for many of our colleagues this is becoming the default style for building enterprise applications. Sadly, however, there's not much information that outlines what the microservice style is and how to do it. In short, the microservice architectural style  is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API. To start explaining the microservice style it's useful to compare it to the monolithic style: a monolithic application built as a single unit.
Caucho Resin : Reliable, Open-Source Application Server Codeception - BDD-style PHP testing. Microservices Guide "Microservices" became the hot term in 2014, attracting lots of attention as a new way to think about structuring applications. I'd come across this style several years earlier, talking with my contacts both in ThoughtWorks and beyond. It's a style that many good people find is an effective way to work with a significant class of systems. This is a guide to useful resources to find out more about microservices.
Fixing SSD Performance Degradation, Part 2: Page 3 For IOzone the system specifications are fairly important since they affect the command line options. In particular, the amount of system memory is important because this can have a large impact on the caching effects. If the problem sizes are small enough to fit into the system or file system cache (or at least partially), it can skew the results. For this article, cache effects will be limited as much as possible. For this article, the total file size was fixed at 16GB and four record sizes were tested: (1) 1MB, (2) 4MB, (3) 8MB, and (4) 16MB. The command line for the first record size (1MB) is, . The command line for the second record size (4MB) is, . The command line for the third record size (8MB) is, . The command line for the fourth record size (16MB) is, . IOPS Using IOzone For measuring IOPS performance I'm also going to also use IOzone. For this article, IOzone was used to run four specific IOPS tests. Write Read Random Read Random Write . . . . Metarates time mpirun -machinefile . Results