Architecture Pitfalls: Don’t use your ORM entities for everything — embrace the SQL!
When designing an application with JPA/Hibernate, I’ve encountered a common pattern that suggests developers should channel as many of their interactions as possible with their database via their persistence entities and ORM, avoiding writing SQL at all costs.
In this post, I explain that affording yourself a bit more latitude to use other tools and techniques tends to pay off quite significantly.
Architecture Pitfalls: Don't let your persistence layer bleed into your presentation layer
It's common for developers to return their JPA persistence entities to the presentation layer as a way to get started quickly and minimise boilerplate.
This post explores why this practise is a bad idea and provides some alternatives to push you in the right direction.
Sponsored Apiman contributions for vendors
If you are a vendor that wants to create a top-notch Apiman integration with your platform or product, we can help.
We've successfully delivered a wide array of integrations for Apiman already, from datastores and metrics, to security and API catalogues.
Why we develop commercial relationships with Apiman users
Commercial relationships are key to the sustainability of Apiman.
We provide significant value over and above the open source community.
We explore just a few examples of our successful projects with clients.
The mystery of the evil line endings
Black Parrot Labs were drafted in to investigate why a client's backend services were intermittently experiencing strange, corrupted HTTP headers in production.
We outline this interesting case from initial investigation to resolution.