Follow Us on Twitter

How APEX will help you create a Sustainable Software Environment

by Douwe Pieter van den Bos on February 8, 2010 · 0 comments

Team Development

Last time, I wrote about Software Development, done Sustainable. How to do this and where my thoughts go when looking on the topic. In this post an example. How does Oracle Application Express, APEX, help you to create a Sustainable Software Environment.

Two elements are to be considered. One is the, absolute necessary, runtime footprint. The other, at least just as important, is the development in APEX itself. As we noticed in the last post Sustainable Software Development is creating a solution that lasts, without stressing the elements of environment, resources and people.

During Runtime, in order to lower the complete energy footprint of the solution, we need to take a look inside Oracle APEX. The simplicity of the architecture of APEX, learns us that well working customized office applications don’t need to run on lot’s of designated servers. A simple database server is sufficient to serve an entire organization.

When we run the APEX applications on virtualized environment, or even in the cloud (like Amazon’s EC2), it’s even quite simple to manage the server’s resources. In other words: only run when you actually need it. Lot’s of energy is spilled running servers that don’t do anything.

During development we actually design and implement the solution. Using APEX, together with an Agile Approach, we can develop smart functionality in a short amount of time. These solutions are also very sustainable. APEX is completely based on the Oracle Database and PL/SQL, which both will still be here for quite some time.

Remote Development in APEX, which is done completely browser based, is another part that gives sustainability a chance. Developers are not bound to one location, therefore they don’t have to travel distances in order to develop, or to make a change in the features of the application. There aren’t a lot of development environments that offer the same possibilities, and therefore this is a major advantage of Oracle’s Application Express.

Possible the main point is recycling. Within APEX we have the possibility to re-use elements of our application within and in other applications. This means that we don’t have to code everything over and over again. Therefore we have the possibility to implement variations of functionality fast. With the plugins offered to us in APEX 4.0 we will have even more possibilities to re-use code and functionality.

Oracle APEX offers us the possibilities to create a Sustainable Software environment. Both in Runtime as during the development of functionality. Short, yet effective projects can be done with this tool, using an Agile approach.

Read the full article →

Thoughts on Sustainable Software Development

by Douwe Pieter van den Bos on February 5, 2010 · 0 comments

Let's go Bananas

Sustainability is hip. When we look at the footprint of our actions in the world, IT (or ICT) is responsible for some of the carbon-dioxide emissions (don’t ask me how much, but I can imagine there’s a lot to win). It must be possible to reduce this by working more efficient and by creating more effective solutions.

Sustainability is also a strange concept. It’s a phrase that has a lot of meaning lied beneath it. What is Sustainable Development? What do we need to do with this concept and aren’t there any dimensions given how to test if something is sustainable? There’s a lot of information on the web about sustainable energy and other measurements, but nothing when you take a look in the services department.

The Cambridge Online Dictionary tells us the meaning of the adjective Sustainable.

sustainable adjective
• able to continue over a period of time
• causing little or no damage to the environment and therefore able to continue for a long time

The first explanation doesn’t say anything about ‘greenness’ of a solution, but the second explanation does. But is environment the only part of sustainability? Or are there more factors to be considered?

Wikipedia gives us further explanation on the subject. On Sustainability Wikipedia describes three ‘pillars’: environmental, social and economic. See, now we’re getting somewhere. So not only our environmental footprint is of the essence when we’re looking into sustainable software development, also the solution needs to make ‘a difference’ and the costs can’t be to much.

When we look into another, possibly related, concept, ‘Green IT’, we mainly hear about hardware which is energy efficient, or IT solutions that helps organizations to reduce CO2 emissions, like software that helps people to work from home. But we also must be able to ‘Greenify’ Software Development itself.

So, we need to create real and structural solutions that treats the environment and the people in it with respect, at low costs. Isn’t this Agile Software Development in it’s core? (help me out here.) Here I think about concepts like SOA integration of legacy systems, cloud-computing in order to balance hardware resources, Theory of Constraints analysis, remote development, and more.

Read the full article →

The Future of Office Productivity is in The Cloud

February 2, 2010

There has been a lot to do about the Oracle acquisition of Sun Microsystems. I’ve found it an appealing time and last weeks announcements have been great. It’s all about innovation and more and more research and development. Oracle, or at least it seams that way, really is into it for the win.
One great example [...]

Read the full article →

Let Fortune Cookies Develop for you

February 1, 2010

Alright, Software Development is hard. Or, at least it is said to be hard and difficult. As I have mentioned loads of times, I really do believe it’s difficult, but us software developers make it more hard than it has to be. We tend to think in problems and difficulties, and create hard to maintain [...]

Read the full article →

When Software Development is (or is not) a Democratic Process

January 31, 2010

Although the Agile Manifesto tells us that the team in a Software Development Project is self steering it also tells us that we should build a project around motivated individuals. How large is the team? And why do organizations still support a strange, overly large and democratic system when it comes to Software Development Projects?
In [...]

Read the full article →

Doing it Different: change the roles

January 30, 2010

When we are writing down User Stories, or simply analyzing a new system, doing things different just might be the right touch to get the information you want on the table. People tend to do what they are used to, so we can assume a lot of assumptions are within the information they give you. [...]

Read the full article →