Posts Tagged with "Architecture"

Geolocation is critical to creating a relevant experience, but creating a stellar geolocation experience is more complicated than just a simple development task.

Discusses architectural options around integrating Web Content Management Systems, such as Adobe Experience Manager with Single Page Applications. Including which integration paradigms are most appropriate for certain situations.

The dark corners of the internet and many an extranet are filled with enterprise applications collecting dust. These applications were once viewed as a potential solution to all of the businesses problems, but they have withered on the vine and are now an impediment to doing business every day.

In many applications, although the application itself has an MVC structure, the application is built as a monolith. Services, libraries, and the application code are all intermingled, making the process of extending or creating a similar application far more difficult than should be required.

In my previous post Creating a Scalable Application Ecosystem, I described how to create an ecosystem of applications, libraries, and services rather than isolated applications. With this paradigm, you should end up with smaller, more manageable projects, but how do you manage all of these separate codebases?

Being certified can help your career and just the act of studying for and taking the test, if done honestly, will help you expand your knowledge and skills. But the Certification in itself does not mean someone will be a good developer / BA / architect than getting good marks on a standardized test means someone will be successful in life.

Here's a neat trick for AEM developers and architects: you can create a diagram representation of the service dependencies using Composum.

Adobe recently announced the availability of AEM as a Cloud Service, a new service offering for Adobe Experience Manager customers to run AEM natively as a Platform as a Service (PaaS) in Adobe's cloud.

The most important part of identifying the correct architecture is to approach the current context without bias and chose the simplest solution that meets the need.

Conflating completion and success makes developer's jobs harder. These two ideas are similar, but there are significant differences in the meaning and situations where the two concepts are useful.

Building a great API is much more than picking the right tech, the quality of an API is driven by the quality of the documentation, upgrade path, libraries and the consistency and execution of the API. However, bu chosing the most applicable format you can get a great start and best position your API for the consumers needs.

As developers, we're looking to make APIs that other developers love, but before such a lofty goal, how about making APIs other developers don't hate.