In this presentation, Joan Touzet explained the design decisions that led her to rewrite the supporting API layer to her company's back-end systems in Python using the Flask microframework to create a unified, RESTful API.
One of my key points about software architecture is that it introduces structure and guidelines into a software system, which in turn leads to consistency and clarity of the overall design. Basically, I'm saying that there are some real benefits from thinking about your design upfront.
As more companies adopt SaaS sales and marketing applications, SaaS providers are under the gun to create and offer functionality that supports the business process and automation requirements of these individual and sometimes silo teams.
Haven’t you ever wondered how GoDaddy, Tucows, eNom and 1&1 (just to name a few) are enabling you, me, us to find available or for sale domain names? The answer is DomainsBot, and they now have a Domain Suggestion API.
It is a common scenario that once you have validated a SAML Assertion at a Gateway layer, you then insert the name identifier from the SAML Assertion into a HTTP Header. Here is how you configure that...
This build process for Apache Axis2 (the C version) should work on other versions of Mountain Lion as well. The easiest way (at least for me) was to install them through macports.
We're adding new functionality into some of the existing use cases. If you imagine that these use cases are implemented by the users working through a number of pages in a web application, we're basically modifying the final step across a number of them.
For those of you that are loading data into Salesforce or other CRM systems such as SAP, Sugar CRM, Zoho, NetSuite and others, how do these stats compare? Get started with dataloader.io by visiting us on the AppExchange.
This blog post explains how to configure WSO2 Identity Server SAML2 IdP with SimpleSAMLphp Service Provider.
The purpose of this article is to see how to integrate Spring Security on top of an Openxava standalone application.
As part of the Kepler simultaneous release, ECF has just released version 3.6.1. The complete new and noteworthy is here, but the highlights are described here.
The basic premise of the session is that many software teams structure their code by layer. In other words, if you open up a codebase, you'll see a package for domain classes, one for UI stuff, one for "business services", one for data access, another for integration points and so on.
In this post I would like to give an example or two on strategy pattern and then rewrite the same example using lambda expressions to be introduced in Java 8.
Problem at hand: Setting up a HornetQ as a standalone instance and running a JMS queue on it. Then getting a Spring webapplication connect to the queue to send and receive messages.
Flightstats' API has key components in PostgresSQL, MongoDB, Java, Apache Tomcat, JAX-RS.
Signals are one of the most basic ways programs can receive messages from the outside world. I’ve found limited tutorial-type documentation on them, so this post covers how to set them up and some debugging techniques.
With Websockets gaining more and more adoption, and wide support of the text-oriented protocols like STOMP (used to communicate with message broker or exchange) are going to make a difference.
LINQ has been quite a successful, but also controversial addition to the .NET ecosystem.
SonarQube (previously Sonar) is a quality management platform aimed mainly at Java (although other programming languages are supported to a varying degree.
I remain one of the few people in irc://chat.freenode.net/##java who will consistently recommend a Head First book. But there’s only a single book from that series that I’ll recommend - Head First Design Patterns.
A lot of readers have asked me to provide details on what tools and software infrastructure is needed to enable systematic reuse. That is a very good question and it is a critical enabler for building on early wins with reuse. At a minimum you need to setup the following as your asset base grows...
If software architecture is about the structure of a software system, it's worth understanding what the major building blocks are and how they fit together at differing levels of abstraction.
It was interesting to see the discussion on today’s API panel at the IIS 2012 Summit. The panelists covered a range of areas of value but there was also some confusion as to what impacts openness and distribution would have.
For me, software architecture is about reducing the number of assumptions that are typically made on software projects, thereby reducing the number of ugly surprises that bite you further down the line.
Many of today’s identity management solutions focus on the internal systems of the enterprise – which employees, divisions and systems are permitted to access which systems. This is an extremely challenging problem.