Let’s look at a Couchbase N1QL query.

A data construct that often appears in business applications is the hierarchical data structure. Hierarchy captures the parent-child relationship often between the same object. For instance, a company structure captures the reporting line between employees. A business organization captures the relationship between parent companies and subsidiaries. Territory hierarchies in Sales. Book of accounts in financial applications.

Due to the self-referencing nature of hierarchy, querying the structure efficiently along with its associated data can be a challenge for RDBMSs, particularly from a performance perspective. In this article, I will discuss how a traditional RDBMS handles hierarchical queries, the challenges that it has to deal with, and how this issue can be similarly addressed with Couchbase N1QL and Couchbase GSI.

Source de l’article sur DZONE

Through Spring Aware interfaces, you can access Spring bean lifecycle events.

Spring Aware interfaces allow you to look into the inner workings of the Spring Framework. Through Spring Aware interfaces, you can access the Spring context, or Spring bean lifecycle events.

Your Spring beans might require access to framework objects, such as ApplicationContext, BeanFactory, and ResourceLoader. To gain access, a bean can implement one of the many Aware interfaces of the Spring Framework.

Source de l’article sur DZONE

Do all programmers after 40 feel like this? #gettintoooldforthisstuff

Note the qualifier, after 40. There is no doubt that it is a great field for anyone younger, but is it all sunshine and roses for people older than that?

I am not yet 35, but will be there in a couple of years.

Source de l’article sur DZONE

We have received an awful lot of requests about extreme programming in waterfall — and that how one could benefit from it as a project manager. Just in case you didn’t know what extreme programming is, it is a form of agile framework where PMs get the best out of available resources in a software development environment.

Extreme Programming (XP) In Agile SDLC Environment

Source de l’article sur DZONE


“A good review from the critics is just another stay of execution” — Dustin Hoffman

I’ve always been intrigued by the different ways in which Scrum Teams go about their Sprint Reviews. It isn’t as though I coach a range of techniques, and suggest that teams just pick whatever format they like. My usual coaching battle is normalizing the practice of having a Sprint Review at all.

Source de l’article sur DZONE



The term API Platform has been used synonymously by some vendors with API Management, Full Lifecycle API Management, and even the term API Gateway. Everyone loves to spice up a subject with the word platform but being loose with the term is cutting the subject short. What is an API Platform? An API Platform is all these things and more.

An API Platform’s purpose is to serve net new application development — building new capabilities, new experiences, nurturing ecosystems, and more. API Management, Full Lifecycle API Management, and API Gateways are tables stakes here of course. These bring life to API design and development, to lifecycle management, to policy and security enforcement, to analytics and to nurturing development communities as consumers of these APIs. All critical.

Source de l’article sur DZONE

I see a lot of happy path bias when it comes to the development of APIs, but specifically when it comes to crafting testing to ensure APIs are delivering as expected. Happy path is a term used in testing to describe the desired outputs a developer and product owner are looking for. Making the not-so-happy path being about testing for outcomes that a developer and product owner are not wanting to occur. When it comes to API development, most developers and product owners are only interested in the happy path and will almost always cut corners, minimize the investment in, or completely lack imagination when it comes to less-than-happy path API testing.

There are many reasons why someone will have a bias towards the happy path when developing an API. Every API provider is invested in achieving the happy path for delivering, providing, and consuming an API. This is what generates revenue. However, in this quest for revenue, we often become our own worst enemy. Shining a spotlight on the happy path, while being completely oblivious to what the not-so-happy paths will look like for end users. Why do we do this?

Source de l’article sur DZONE

The deployment of Mule applications can be managed using Maven. The Mule Maven plugin allows integrating the packaging, testing, and deployment of Mule applications with the Maven lifecycle.

It helps in automating the application deployment.

Source de l’article sur DZONE