How to Log a Log: Application Logging Best Practices

The importance of implementing logging in our application architecture cannot be overstated. If — and this is a big “if’ — structured correctly, logs can contain a wealth of information about a specific event. Logs can tell us not only when the event took place but also provide us with details as to the root cause.

But to ensure our application logs are indeed useful, there are some basic requirements. First and foremost, they need to be digestible. Meaning, they need to be structured in a way that both humans and machines can read. Complying with this requirement requires careful planning and strategizing but also ensures that searching and analyzing the logs will be easier.

Easier said than done, right?

Below is a list of some tips and best practices we advise our users to adhere to when setting up logging for their applications.

https://logz.io/blog/logging-best-practices/

The Expert (Short Comedy Sketch)

10 Tips for failing badly at Microservices by David Schmitz

Microservices are just a bunch hip new framework plus some AngularJS frontend or React, right?
So, if you want to make sure that you absolutely and definitely fail at your Microservice project, then watch this talk and learn how.

Using real world experience from multiple green field and brown field projects, I can show you: – how to ignore the mandatory organizational impact
– how to focus on the code only without any regard towards ops and testing
– continuous deployment is for losers. Real projects use their meat cloud for delivery – jumping onto every new and untested framework is a must
– EventSourcing and CQRS are both free lunches. So, you can add complexity without any real need
– …and more

If you mind my tips, then surely you will fail at Microservices and your boss will never again try to move away from your beloved vintage monolith.

David Schmitz
Pricinpal architect at Senacor Technologies with a history of + 13 years of working in various projects using a bunch of different stacks and environments.

Current focus is on migrating architectures and organizations, such that our customers can cope with the challenges of the digital age.

Mock Responses in Postman

Postman recently introduced mock servers allowing developers to simulate an endpoint without spinning up a back-end server. Today, Postman is announcing Examples to take it one step further, or to be precise, one step earlier in the API development lifecycle.

Developers can mock a request and response in Postman before sending the actual request or setting up a single endpoint to return the response. Establishing an Example during the earliest phase of API development requires clear communication between team members, aligns their expectations, and means developers and testers can get started more quickly.

http://blog.getpostman.com/2017/05/17/mock-responses-in-postman-by-using-examples/