Software development involves several tasks in building the development environment. In a typical web application scenario such as Liferay these tasks include:
- Installation of a run-time environment (Java)
- Installation and configuration of a database
- Installation and configuration of an application server
- Configuration and integration of external systems
- Environment configuration (Path, Proxy, etc)
These tasks are usually done manually and hence the different environments across developers tend to differ in small parts and the effort is quite high for each developer. Additionally if one is developing for multiple projects there is a chance that these projects each require their own environment. This further leads to possible collisions in environment settings or different versions of artifacts.
In the end the software must run successfully on a series of production and test systems. Because of the small inconsistencies it can never be guaranteed that the local environment is exactly the same as the production system. This can lead to subtle errors which are hard to find.
All code described here can be found on GitHub: https://github.com/mimacom/liferay-puppet-deployment
Visualise the recording of our Webinar “Spring for the Elephant” (in German) and see how Hadoop
are used to develop stunning BIG DATA Software applications.
Apache Hadoop and its rapidly growing ecosystem (eg . As Pig , Hive , HBase , etc.) has enjoyed a lot of attention in recent time.
We answer the following questions:
- How easy is development using these tools?
- How can you connect conventional applications to it?
There are plenty of interviews and articles praising the added value of using Atlassian
tools. To check those perspectives, as an experiment, we turned it around …
Big Data visualization, easy and beautiful with Kibana. The Webinar in German “Visualize Data with ELK” focuses on the data visualization with Kibana, which is part of the elasticsearch ELK application stack.
I bet you have heard about React, but what about Flux?
There are too many technologies to navigate effectively and frameworks are becoming obsolete even before becoming the standard (I am looking at you Angular 1.3, hmm 1.4 but still…). Angular is nice and productive to work with, but recently announced Angular 2.0 is so different from Angular 1.3 (1.4) that it made many developers consider other possibilities. There are popular jokes that the the only thing Angular 2.0 shares with its former incarnation is the name 🙂