Eneris Solutions » BlogThis page is for the technically inclined - for those of you who are wondering what technologies are behind some of the high-quality solutions developed by Eneris. Eneris' strives to always find the correct technological solution to the requirements Note: this page is part of a blog by the CEO so does have some personal opinions - which hopefully are reflected by the company ;) May 15th, 2008. Brave new world Fedora 9 arrives, and HP Pavilion. Seam EJB3 update..Enterprise Java - since 1999. Eneris has been intimate with EJB's since 2000. We had a ban on EJB2 Container Managed Persistence until EJB3 finally arrived! (See Hibernate). EJB3 was a savior for Enterprise Java. Instead of Spring we prefer Seam, EJB3, JSF. Hibernate. Another winning technology. Map objects into relational databases and back again. This technology is so good that it was essentially adopted as the EJB3 standard and you can even use it on .NET with .NHibernate. JBoss since its inception. We use JBoss when we need to have > 99.99% uptime. Clustering and failover configurations are key to this. JBoss also has efficient caching, and great security. Netbeans. Java IDE's just don't get any better than this... Visual design, J2ME, Web support, JSF, etc., etc., Ok sometimes you can find someone running Eclipse at Eneris, but usually it is a anomally.Java Server Faces. We develop applications at Eneris; we don't want to waste our lifetime trying to learn about obscure browser incompatibilities. When I need to put a combobox in a web interface I reach for my JSF components. Seam. Newcomer on the block. JBoss + JSF. Gives Ruby on Rails a run for its money. And at the end of the day we'd rather see the application running on a proven Enterprise server. Seam is a RAD tool for web applications in Java. This technology is in use with several production application and it works great. Seam also has integrated AJAX/RichFaces support so you can do those cool web 2.0 stuff. Microsoft .NET (C#). C# was born out of the good ideas from Java and Borlands CBuilder. (I consider myself somewhat of an expert on Microsoft for Microserf reasons). For those customers that are Microsoft oriented - this is the way to go. We happily use our Enterprise skills to develop with C#, and apply structured and layered development that is really needed in this environment. MySql, PostgreSQL, Oracle. Is it possible to make an application with a database nowadays? We reach for the database that is appropriate for the situation. They are all good stuff. Linux. Our standard development and server environment. Which one? Fedora. Fedora Linux (and Red Hat before that) has been the standard at Eneris for 8 years. Stable, solid, Linux, with good developer support - from other professional like Eneris. C++/MFC/COM Our deep experience includes solid technology skills. .Net Compact Framework. A J2ME from Microsoft. Symbian. We do some of this too. J2ME Been there, done it. Agile/SCRUM. We follow agile methods whenever possible. Sometimes customer projects require a more traditional phased approach, with rigorous (unflexible) feature requirements, and schedules. Agile development works best at achieving clear goals when customers have a good idea what they want and want teams to work together flexibly towards those goals. XWiki. This is a 2nd generation Wiki. We use it for communcations with customers, etc. It's a great collaboration tool. It's open source, based on Java and Hibernate (Groovy too). |