Outstanding Infrastructure
Previous Next 1 2 3 4 5 6 7 8 9 10
Firefly is a fourth generation SCM tool. Its outstanding infrastructure design bares fruit to many advance features and system benefits. Let’s take a look at some of them:
Performance
Firefly’s advanced algorithm and SmartTransfer technology makes client-server transactions lightening fast. When Bringover or Submit is executed, Firefly is able to determine the difference between server files and local files much quickly than legacy version control tools. After the difference is determined, only delta information is transferred for both directions.
FleXtream technology makes branching and baseline creation a snap of the fingers – with ease and speed. No files are copied even if they were modified on the new branch. Only references were made.
Firefly employs a distributed computing model. This greatly reduces server and network stress and efficiently utilizes resources on the client-side.
Java Remoting is the communication protocol used by Firefly server and client. It is based on the mature and industry standard TCP/IP protocol, entirely written by Hansky from scratch and optimized for version control needs. It is a lightweight communication protocol due to its lightweight object serialization mechanism. So right off the bat it already uses network resources efficiently because it requires less network overhead than heavyweight protocols like Sun Java RMI. Streaming made Firefly operation much more efficient than other similar products using non-streaming protocols. It kept function calls to a minimum to reduce the communication overhead between server and client. Java Remoting is much faster when it comes to transfer large file between server and client than other non-streaming protocols.
Scalability
Firefly supports projects from individual level to full scale enterprise development teams. It has the ability to support multiple repositories. Aside from the obvious scalable benefits, this feature also helps to better partition and archive projects. Firefly also supports a large amount of concurrent users.
Atomic Operations
Atomic operation means either all data are transferred and the transaction is successfully completed or it fails. There is no in-between state. In Firefly, Changeset commit, label and branching practices: creation and merge, are all atomic transactions. This guarantees the data integrity in your repository.
Previous Next 1 2 3 4 5 6 7 8 9 10