Lofi model @ work

I had a chance to talk about my litte experience of implementing and doing the operation of microservice-based application. Here are my slides in German language: Enterprise-Application-Customization mit Microservices - Ein Erfahrungsbericht

Enjoy!

It is interesting to see that even Google cannot make Dart - after more than 5 years - as a real challange to JavaScript. At the end Dart is "just" another insignificant programming language and compiles those codes to JavaScript. In this point Microsoft is more intelligent by doing TypeScript which is nearer to JavaScript. Check this article for comparison between Dart and TypeScript: Why did the Angular team choose TypeScript over Dart?

If Google were to invest that amount of ressources for Dart in GWT (Java to JavaScript compiler), which is definitely a very good product and Java is still the number one programming language... I cannot imagine where we are today with GWT.

So I would stick to Java with GWT and if I need to write directly in JavaScript I would use TypeScript. No place for Dart. Just curious, Google seems to be very clear with its target, if a product is not successful, remove it (see iGoogle, Google Wave, etc.). This could also happen to Dart?

Introduction As the world was still at Java's hand we often define what so called a component-based platform. I had this experience in the year 2000 with OpenUSS (Open University Support System). At that time I had an idea to develop a platform which is extendable using component architecture and J2EE technology (OpenUSS Component Architecture). After a while we saw the birth of portal and portlet technology. Everyone tried to build portlets which can be easily installed in a portal server, all Java based. Do you remember all those portals like Apache Jetspeed, Liferay, JBoss Portal, IBM Webshepe Portal, etc?

After the portal wave there was OpenSocial gadget which is not only specified for Java but generally available for different technology implementations. It uses HTML, JavaScript and REST completely independent from Java. Apache Shindig was an Open Source implementation for OpenSocial gadgets container. OpenSocial gadget was also the main technology for iGoogle, Orkut, MySpa…

Invitation I was lucky that my daughter asked me whether I would answer all the questions of her classmates - most of them are nine years old - about my profession. They had "professions" as the topic of their general knowledge lesson. So my daughter told me that they invited teacher, school caretaker, stewardess, nurse and also me software developer. Her classmates and she would ask the invited person some questions. I directly said yes because I think that the new generation needs to be introduced in software stuff especially that the current professions will change a lot in the near future. Reuters had a very interesting article about how Robots and Artificial Intellegence will cost five millions jobs by 2020. In my opinion software development will be much more important by 2020, so this is my chance to introduce my profession to the kids in my daughter's class.
Preparation In my preparation I thought that I need to show them something cool so I began to google and…

Introduction Today in highly paced enterprise environment you, as the leader of enterprise IT division, need to be fast. Simplicity is the key for the speed. What are the key factors to simplify your IT? Three different areas are very important to take care of: Technology, Organisation and Environment(TOE Framework: http://goo.gl/tQlX5z). Here are some detail points for technology and organisation:

1. Technology: in most enterprises there are already one or more ERP and CRM solutions the so called Enterprise Applications. We need to manage them carefully as they support the business processes. In context of the core compentencies most enterprises customize the enterprise applications to fit their needs. We need to manage the customizations in detail as they represent the core competencies and at the same time the differentiation of our enterprise to other competitors. 2. Organisation: working in a small team with different roles and functions is already proved as the best …

Today if you want to deploy your webapp or webservice you first think to do this in the cloud by using PaaS (Platform as a Service). The problem is you have many alternatives in this area:

- Microsoft Azure: http://azure.microsoft.com
- Google AppEngine: https://cloud.google.com/appengine
- Amazon AWS (Elastic Beanstalk): http://aws.amazon.com/elasticbeanstalk
- Heroku (from salesforce): https://www.heroku.com
- OpenShift (RedHat): https://developers.openshift.com
- CloudFoundry (Pivotal): https://run.pivotal.io

The problem: what PaaS should you choose? This presentation helps a bit: http://goo.gl/dGnpGP

BTW.: if you want to run Docker, AWS Elastic Beanstalk is the easiest way to do: http://goo.gl/mtMk5J 

It would be nice to hear your opinions!

Cheers,
Lofi