TECHNOLOGIES WE USE

Whenever we start a new client project, we select one of our standard technology stacks depending on project type and customer need.
Within just a few minutes the selected technology basis is deployed fully automated onto our cloud.
And yes, it's Infrastructure as code (IAC) and can be custom tailored to your needs.

Java EE Technology Stack

Used for web & rich/mobile clients our Java EE stack is our most used one, it has been deployed in most of the projects we have worked on in the last years. Web based applications gain more and more popularity and today's web frameworks produce rich user experience. Our Java EE stack is frequently updated to reflect newest technologies and is highly customizable, eg. for different front or database technologies.

  • Java SE 7/8
  • Java Enterprise Edition 7, Tomcat, JBoss WildFly, NGINX
  • Jax-RS, EJB, CDI, JPA/Hibernate, Spring, JSP, JSF, PrimeFaces, GWT/Vaadin
  • Atmosphere, ActiveMQ, Lucene/ElasticSearch
  • HTML5, CSS3, Bootstrap
  • JavaScript, TypeScript, Less/Sass, AngularJS, jQuery, KnockoutJS
  • Git, Maven, Nexus, Gulp, compass, DBmaintain, Togglz
  • JUnit, Mockito, Powermock, Cucumber, Selenium, Arquilian, SoapUI, JMeter, DBunit
  • MySQL, PostgreSQL, MongoDB, Redis

Rich Client Technology Stack

There are special use cases where rich clients make a lot of sense - beyond their offline capabilities rich clients come in handy when a highly interactive user interface is required, e.g. for digging and managing huge amounts of interdependent data, editing documents or data sets. Whenever users need to be fast on the keyboard rich clients still score higher.

  • Java SE 7/8
  • Eclipse RCP, SWT/JFace, OSGi, recently we added JavaFX
  • Jax-RS, CDI, JPA/Hibernate
  • Git, Maven, Nexus, DBmaintain
  • JUnit, Mockito, Powermock, DBunit
  • MySQL, PostgreSQL, MongoDB, Redis

Mobile Client Technology Stack - Android

Android, with a market share of more than 80 % is the largest installed base on mobile devices such as smartphones and tablets. Most applications went from supporting mobile devices via web only to native applications that run on the device and connect to a backend service avaible on the web. Typically native applications support Android's neative features such as sensors, guestures and offline capabilites. With the advent of smartwatches modern applications are also requested to support Android Wear.

  • Java SE 8
  • Android 6.x Marshmallow, Android Wear
  • OrmLite, Dagger/Butterknife/RoboGuice, GCM
  • Git, Gradle, Nexus
  • JUnit, Robolectric, Mockito/Powermock, Cucumber, Robotium
  • SQLite

Mobile Client Technology Stack - iOS and WatchOS

Apple has the second largest installed base focusing on high end users. All modern applications and products are required to support at least both worlds, iOS and Android mobile devices in their diversity of device type, screen size and resolutions - resulting in a reach of about 97 % of all mobile device users. We recently added support for applications with counterpart features on Apple Watch to our iOS stack.

  • Objective-C, Swift
  • iOS 7/8/9, WatchOS 2
  • Git, Xcode tools + core frameworks
  • CocoaPods
  • Cucumber, Frank

Ruby On Rails Technology Stack

We have been building Ruby and Rails applications since it's beginning in 2006 and we love the stunning support for agile development right out of the box, be it for test-driven or behaviour driven development, continuous delivery or simply the avoidance of boiler plate code that comes with a lot of convention over configuration.

  • Ruby 2.x and Rails 4.x
  • Mongrel, Nginx, Unicorn
  • Ruby Gems, dRuby
  • Cucumber, Mocha, RSpec
  • Rack, Devise, Capybara
  • Git, Rake, Phusion, Capistrano, Vagrant, Puppet
  • MySQL, PostgreSQL, MongoDB