In the first part of our post , we explained why user-defined passwords are not a sustainable mean for making the Web a safer place for private matters or business. So what? As there’s no going back in the use of the Internet – on the opposite, whole sectors of our activity continue to shift online – authentication needs to be fixed in some reliable, standard, future-proofed way. Here are some thoughts on realistic paths to take – and some dead-ends to skip.
Troy Hunt, the world's security guru, reveals his new API for the awesome site he made, haveibeenpwned.com, which tells you if your email address has been part of a major security breach.
Take a look at some of these messaging patterns that can be used beneficially even in modern, startup-esque applications, despite their "enterprise" label.
I’ll walk you through an example of how to use this TCP transport based on Netty to improve certain systems running on Mule.
Mule makes the fork-join pattern much simpler to implement, but here is how you can implement a custom message processor that will run faster than the using the default Mule pattern.
JBoss Fuse is an open-source ESB and is the evolution of Fuse ESB after the Red Hat acquisition of FuseSource. It’s open-source, Apache v2 Licensed, and fully supported by Red Hat.
Knowing that WebSphere Commerce v7.0 includes the Apache Wink framework; we can leverage this to create a REST service client that is also based upon Apache Wink, and leverages a framework pattern rather than just pieces of code put together to execute HTTP calls and retrieve the responses.
Here's a screencast showing how to get started using JBoss Fuse 6.1 Early Access release on OpenShift for creating integration solutions based on Apache Camel in the hybrid cloud.
When you build applications based on Mule EE (Enterprise Edition) and you are using Maven to build your projects, you will notice you have dependencies to libraries that are not available in the public Maven repos.
Learn about the importance of micro-features and how they fuel disruptive applications, as well as how companies with API strategies will be the ones to succeed. But how exactly do you arm yourself?
One of the most welcoming features of the new Mule Studio 3.4 is the Maven support. I was very keen to try out this new feature. I grabbed one of the projects I was working on, and imported it into Mule Studio through File -> Import -> Existing Maven Projects.
Wingify engineering has written an interesting review of how their architecture has changed and scaled. They've open sourced one of the key technologies they built that allowed them to do it: agentredrabbit a transport agent for taking chunks from Redis lists and bringing them to RabbitMQ.
This article from PyCon was titled "How we use Python at Spotify" but I wanted to focus on the fact that they also use ZeroMQ. It's a little difficult to find a list of the big-name companies that use ZeroMQ, but now you can rest assured that one of the biggest fish in the IT pond use it.
ZeroMQ is a socket abstraction and concurrency framework that's changing the way we think and reason about distributed systems. In this talk we'll discuss the importance of lightweight messaging for applications, composable messaging patterns, swappable transports and more...
In this blogpost I aim to clarify some concepts which will show how to configure an HTTPS client and server in Mule for SSL and two-way SSL (Mutual Authentication).
The Java API for WebSocket (JSR 356) is one of the APIs recently added to Java EE 7. It is a '1.0' release. "Tyrus" serves as the JSR 356 Reference Implementation.
Over 10 years ago, Enteprise Integration Patterns (EIP) became the world wide defacto standard for splitting huge, complex integration scenarios into smaller recurring problems. This session revisits EIPs and gives shows status quo.
A common use case Mule ESB flows is validating if an XML document is valid against a corresponding XSD. It can be quite annoying to find out you have spent a lot of time fixing an issue when it was actually caused by another system that was supplying invalid XML.
One of the primary questions I get asked is - "What is the difference between SAML and OAuth?". I hope I can use this article to provide my thoughts on this important topic. I will also try to point out various use cases where each one is preferred.
There are two philosophical approaches to how this orchestration might take place: through a tightly-integrated system, or through a more loose coupling of heterogeneous components. But how should architects make the choice between these approaches?
When I talk about JAX-RS 2, JSON-P and Java EE 7 a surprising number of people seem to assume that GlassFish and Jersey does not support JSON binding and just supports lower level JSON processing.
I can't help but think how things could have been different with Healthcare.gov if it there had been some sort of external watchdog group tracking on the process from start to finish.
While the awesome Apache Camel team is busy fixing the handling of the multiple parameters in the query, here’s a workaround
API Examples is an application pattern originally devised by Daniel Worthingon-Bodart, in which a new version of a producer application is accompanied by a sibling artifact that solely contains example API requests and example API responses.