As the number of our new (and old) customers grows, it becomes crucial to use IaC and enjoy all of its benefits like mitigation of human errors, infrastructure (self-)documentation etc. (more…)
Try to Google a bit and find some blog posts about adoption of microservices, Docker, Kubernetes and other “new” stuff in the traditional environments. Almost every post is like “yeah, microservices are kinda cool, but monitoring and overall observability is very challenging.”
Well, that’s not true anymore. And today I’m gonna show you one important pillar of this shift from “challenging” to “absolutely possible.” Please make some noise for the technology which can’t be missing in your microservice stack – distributed tracing.
As we’ve shared in our previous DevOps posts, we mainly use Jenkins for our common CI and CD tasks. Nowadays, Jenkins is still industry standard, there are heaps of resources tutorials and Stackoverflow threads about (almost) every conceivable issue. I’ve written “almost” back there, I know. Well, sometimes you have to dive in to Java code and figure out what the hell that XYZ plugin actually does. And things can get messy. But enough of complaints.
The data dependencies management is an important topic for me. Over the years, while working with React, Redux and other libraries from this ecosystem, we developed a few solutions for this problem. Here is our story.
Redesigns launch countless waves of hate. That’s an axiom. Every logo change of any more or less known company is welcomed by tons of bitter posts and comments on every social network of the world. Insults on designers, supposedly “witty” memes, attempts to improve the design, listings of human organs that can be seen in new graphics, discoveries of old-time logos from which the new one was obviously copied – just classic. The quality of the redesign doesn’t matter. Twitter will explode even when Spotify changes the shade of green.
Interacting with the Tezos blockchain on an iOS device should be an easy task. With TezosSwift, we at Ackee are working to accomplish that goal. TezosSwift has been built with type-safety in mind and implements most of what you could possibly need for Tezos development on iOS. Parts of this tutorial are also applicable to Keefer Taylor’s TezosKit, a library that TezosSwift is based on.