This is the 3rd post I am writing to explain the use of extension points in WSO2 Identity Server. WSO2 Identity Server has so many such extension points which are easily configurable and arm the server with lot of flexibility.
As a developer, I’m enjoying working on new microservice instances which are effectively greenfield projects with well defined constraints on their interface, but with a flexible internal implementation and therefore a flexible set of tools and frameworks with which we can achieve our goal.
I gave a brief introduction about the Overlord project family yesterday. Today it's time to test-drive a bit. The API Management sub-project released a 1.0.0.Alpha1 two days ago and introduces the first set of features according to the 18-Month roadmap.
I have been learning SimpleInjector for few days and it’s just awesome. I have already written two post about it(see below link) and this post will be third post about it. In this post we are going to learn how we can do Dependency Injection with ASP.NET MVC.
Java 8 was – as always – a release of compromises and backwards-compatibility. A release where the JSR-335 expert group might not have agreed upon scope or feasibility of certain features with much of the audience. See some concrete explanations by Brian Goetz about why.
I have just completed a script that can be used to install a service bus host as a windows service. It is nice to use, when delegating the installs to the support team, this is always done via NServiceBus.Host.exe.
Last week I was tasked with developing a quick prototype that used AngularJS for its client and Spring MVC for its server. My colleague mentioned he was going to use RESThub as his starting point, so I figured I'd use JHipster as mine.
To ensure that your API is ready for success, part of your testing practices should ensure that your API will handle this successful load. You should also be fully ready for surprising growth and popularity of your API!
I have been working on integrating with RabbitMQ to implement the messaging architecture.
I’ve been working on migrating some batch jobs for Podcastpedia.org to Spring Batch. Before, these jobs were developed in my own kind of way, and I thought it was high time to use a more “standardized” approach
Building an API for longevity requires careful thought, careful design, and extensive prototyping to get developer feedback. Without a solid foundation your API is doomed to be short lived, becoming nothing more than a costly experiment to justify building a better API.
This post covers some basics of JVM memory structure and quickly peeks into PermGen to find out where it has disappeared since advent of Java SE 8
ServiceStack is a light-weight, complete and independent open source web framework for .NET. I recently started playing with it and I must say that it is an awesome framework. It has several nice features including .NET’s fastest JSON serializer.
As I talk to people about using a microservices architectural style I hear a lot of optimism. Developers enjoy working with smaller units and have expectations of better modularity than with monoliths. But as with any architectural decision there are trade-offs.
This is another blog the ongoing series about the Red Hat xPaaS solutions, where I am trying to demystify the acronyms a bit and give you more information about the projects and products composed around it. After the initial overview this post focuses on the first aspect of the iPaaS solution: JBoss Data Virtualization.
In this part-2 tutorial, we will take a look at what are Angular modules, controllers and services and how to configure and use them. Also we will look into how to use ngRoute to build multi-screen application.
I’m going to show you a neat trick which combines the health indicator endpoint in Spring Boot and the metrics provided by Hystrix.
REST API Security has come a long way from being a case of "Just use SSL"... or has it? On September 18th at 11am US Eastern Time / 4pm UK, we're running a webinar with Gunnar Peterson on the Top 10 Security Issues for REST APIs.
The benefits of applying the principles of SOA when catering to the IT needs of your organization are clear in a business-driven, vendor-neutral architecture. It considers all requirements from the perspective of the business process and delivers implementations in order to automate the same.
Recently, I was working on a project which uses a REST services layer to communicate with the client application (GWT application).
I usually pay a visit to the JetBrains booth and chat with the guys at every concert I go to. So last time I was at Devoxx UK I talked with Hadi Hariri about how to get better application server support within the IDE (let’s say WildFly). He asked me to send him an email… so I wrote this blog.
For any particular GlassFish release, we used to have different distributions. We had an English and a multilingual (ML) version of GlassFish. We had a Zip based distribution. We also had versions with a native installer... on different platforms (Windows and Unix's).
In spite of its title, this blog is not about how to enter a relaxed or restful state, but instead, presents some of the concepts behind REST (REpresentational State Transfer) and links to more information. It will show that simply returning JSON over HTTP is not a REST API.
Creating a method that has many parameters is a major sin. Whenever there is need to create such a method, sniff in the air: it is code smell
There are plans to expand this demo project with various integration scenarios or use cases, but for now we start with just a single story around using a JBoss Fuse camel route to interact with a rules and process project deployed onto JBoss BPM Suite.