Separating a code base in many small, isolated, pieces of code prevents coupling and forces you to think about separation of concerns. Modularity makes it much easier to develop and maintain a large code base. Amdatu takes a different approach in that it’s core concept is modularity. So how is this different from other frameworks? Most frameworks (Java EE, Spring, Grails etc.) are just more convenient ways to build applications using the same old architecture. The software components are just (very useful) enablers of this architecture. This is what brings maintainability and scalability. The architectural part is by far the most important. PulseOn is of course built on Amdatu, but what does that mean exactly? Is Amdatu the framework to rule them all? There are two different ways we can look at Amdatu:Īn architecture blueprint for “cloud†applications That has nothing to do with the fact that we are using Amdatu and OSGi per se, but is all about the advantages of an architecture enabled by these technologies. The two main factors why people are looking at our architecture is because we have a way to maintain a high quality code base in a very agile environment, and because the way we deal with scalability. We have been presenting at several conferences, and had several meetings with (potential) customers interested in how we are doing things. In the past few months I have talked about the PulseOn technology stack with many people. As a side note about training, it’s funny how many OMG WTF moments I recently had in the supermarket now that I started paying more attention to what’s in food.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |