Suppose we will fetch some Amazon AWS news into a MongoDB database. These few lines made it possible with the use of Groovy and the Gmongo module:
After we find out how replication works with MySQL lets look at mongoDB
Use the following steps to implement mongoDB Replication:
For a project we need a second MySQL database for reporting, so whe can split the day to day business (forms) and the analytic reporting. Another thing is that the data must be very actual, so a nightly backup is not really an option.
In my latest post about Amazon Beanstalk I explained how to deploy to Amazon Beanstalk in 3 simple steps. Of course this a manual activity. We often deploy new versions of apps to Amazon Beanstalk, so it is a ‘must have’ to automate this proces.
Since I have an Android Honeycomb Asus Transformer the default email adres is from Google’s Gmail. The standard Yahoo mail App is not really nice and you want to integrate all the mail accounts into the mail system of Android Honeycomb. Adding a yahoo mail account is easy:
After deploying Grails Apps to Amazon Beanstalk, it’s now time to look at CloudBees. At the moment CloudBees offers the only Platform as a Service (PaaS) that spans the complete develop-to-deploy lifecycle of Java web applications in the cloud; without any servers, any virtual machines or any IT staff. See the Cloudbees website for more info. For a random Grails App named ‘KnowledgeMatch’ we follow some simple steps:
Implementing business rules can be a tedious and error-prone task in application development. Business rules are often ambiguously defined and recorded. Since implementing business rules is usually a major task in each project, this can introduce a significant risk to the success of your Grails application.
We can easy deploy the Grails WAR file to Amazon Beanstalk in 3 simple steps:
For a Grails project we use Tomcat for our demo environment on Windows. Our Grails App is using MySQL as datasource. Here are 3 simple steps to get your Grails Apps deployed.
Just ’Hotnews’ that the takeover is a reality. What does the acquisition of Sun by Oracle mean for the Java world? I think this is bad news for the Java community. Oracle is no longer focused on developing tools for application development. Yes ok, they develop their own Oracle Fusion Applications in Java, but with the aim to expand globally and try to beat SAP in this market. If Oracle has put his sights on Oracle Fusion Application and the maintenance (Oracle Fusion Middleware), there is no urgency to develop tools for application development. This is unfortunate. I am so curious of the future of products such as Sun NetBeans (latest version 6.8, it’s become a very nice product) and Glashfish.Glashfish, I think it will not make it. Oracle has recently chosen for the BEA WebLogic product, now known as Oracle Weblogic. Jdeveloper and Netbeans are almost equal products. Jdeveloper supports Oracle’s proprietary natural solution like Toplink and ADF. The MySQL database is under pressure. Oracle will in my opinion not drop its own database!