How Do They Do It?

How Do They Do It?

Last time, we revealed how Resultly was conceived and born. Today, we
are going to take a sneak peek behind the scene of our robot that
breathe a new meaning into the term “Search”. Resultly is an automated
machine, and it takes an entire team of software engineers to make sure
its gears are well oiled and running at full steam.

!Apple meets Resultly

Most of the hardware used in Resultly is Apple branded. We believe that
the smoothest integration is achieved when hardware and software are
provided by the same vendor (speaking of iPhone). We apply this
principle whenever possible. In addition to being a single source of
software and hardware, Apple is chosen for its reliability, generous
warranty, and quite reasonable price-to-quality ratio. Not to mention
that Apple Inc. is renowned for its achievements in the field of
industrial design. Human factor plays an important role here in Resultly

Every engineer in Resultly is given a personal MacBook Pro - we use
laptops in our development process. We subscribe to the principle, that
can briefly be summarized by an old Latin proverb "Omnia mea mecum
Should an exception occur, our engineers will have ability to address it
24/7 at any location through a company provided terminal.

Resultly is the product of a creative process, and we believe any
creative processes should have no artificial constraints. Flight of
thought and storm of ideas should be subject to no limitations including
the size of a monitor on an engineer's desk. Here at Resultly, each
workstation is equipped with two 27" portals into the world of code.
Thunderbolt LCD monitors from Apple provide abundance of screen real
estate. Besides increased productivity, Apple's slick design, crisp and
vivid colors ensure a pleasant working experience for our developers.

Resultly engine is written in .NET C# and the entire project is managed
with MS Visual Studio 2010. It would be quite a challenge to run Visual
Studio on Mac OS X. Parallels Desktop 7 is a perfect solution to
reconcile these two discordant platforms. Plethora of RAM (8Gb), a
speedy 2.2GHz Intel Core i7, and a roomy SSD allow anyone to seamlessly
submerge into Windows 7 experience… on a Mac laptop.

Back to Resultly's inner workings. As we mentioned before, we used C#
to build the engine. Telerik for MVC .NET was
chosen to design the front end of Resultly. Our choice was based on
Telerik's rich set of features and its excellent support. It is in
general a very high quality product that turns development into an
effortless flow.

As for the back end of Resultly, we succumbed to the emerging
NoSQL paradigm in data management approaches. Apache
Cassandra interfaced by Aquiles was an obvious choice for our purposes. Resultly is in its infancy right now, but it is expected to
grow fast devouring web pages, organizing vast amounts information, and
acquiring users at exponential rate. We needed a reliable, scalable, and
easily distributed data management system. Moreover, the nature of
queries to Resultly engine prevents us from fixing a static data schema
- not only the data but the data structure itself is dynamic for our purposes. We wanted to have a correct approach from the beginning and we
chose Cassandra.

Article by Resultly

Close Window