Partner – DBSchema – NPI EA – (tag = SQL)
DbSchema is a super-flexible database designer, which can take you from designing the DB with your team all the way to safely deploying the schema.
The way it does all of that is by using a design model, a database-independent image of the schema, which can be shared in a team using GIT and compared or deployed on to any database.
And, of course, it can be heavily visual, allowing you to interact with the database using diagrams, visually compose queries, explore the data, generate random data, import data or build HTML5 database reports.
>> Take a look at DBSchema
Partner – CAST AI – NPI EA (tag = kubernetes)
The Kubernetes ecosystem is huge and quite complex, so it’s easy to forget about costs when trying out all of the exciting tools.
To avoid overspending on your Kubernetes cluster, definitely have a look at the free K8s cost monitoring tool from the automation platform CAST AI. You can view your costs in real time, allocate them, calculate burn rates for projects, spot anomalies or spikes, and get insightful reports you can share with your team.
Connect your cluster and start monitoring your K8s costs right away:
>> FREE Kubernetes cost monitoring
Partner – MongoDB – NPI EA (tag = MongoDB) Partner – Thundra – NPI EA (tag = Jenkins)
You can get some real insight into your CI pipelines, and into your tests by using Foresight.
This includes not just the basics but some actual, actionable data like Change Impact Analysis, where we can see the changes in a PR and correlate them to test runs and test coverage to show how they affect our builds:
>> Try out Foresight in a project
1. Spring and Java
A peek under-the-hood at coroutines – a feature not natively supported by the JVM – and how they work in Kotlin.
A great overview of this IETF standard for communicating problems and errors to API clients.
An excellent primer for newbies, and a nice review for the more experienced JPA connoisseur.
Also worth reading:
Webinars and presentations:
Time to upgrade:
2. Technical
A guide to the headers and HTTP status codes to use in this scenario.
A case study of a failed microservices architecture — and why a monolith was ultimately the better solution.
Also worth reading:
3. Musings
An interesting look at the market forces that preclude rewrites of poorly-designed systems.
Also worth reading:
4. Comics
And my favorite Dilberts of the week:
5. Pick of the Week
res – REST with Spring (eBook) (everywhere)