In 2016 pretty much every commercial software system built with modern tech is a distributed system. Yes, we all build distributed systems these days. Obviously, the term "distributed" is very spacious - I'm not saying we're all creating stuff like eventually consisted, sharded data stores (should be left to specialists who excel in these), but having 2+ layers of independently scaled, communicating processes in production is today's bread'n'butter. I'll save you all the standard talk about usual implications like: increased complexity, need for being asynchronous & message-driven, etc. - if you follow my blog posts at least once…
All posts in reactive programming
February is over, so it was a high time to open the conference season in 2015 already ;P Due to practical reasons I carefully track such events that happen in Poland (not much to be tracked, but the number is increasing from year to year) - that's how I found myself in Cracow on 26th of February, the 1st day of Lambda Days, relatively less known conference dedicated to functional programming. You can find all the details about the idea of this conference on its website, but there's one thing worth mentioning -> during the second day of Lambda…
I've spend yesterday's early evening on presenting about Reactive Extensions (Rx) for professional local .NET enthusiast User Group in Warsaw - WG.NET. To be honest I didn't expect many people to come: it's still August & many people are on vacation the library (Rx) is not that new & I can't really call it a hyped solution for these days :) I don't find myself a renown speaker, audience would fill the room for there were no swags / contests / lotteries, just the talk we've announce the talk just a week in advance & it was not on a usual day…
Private advertisement mode ON In about 1-1.5 week time I'll be presenting about Reactive Programming in .NET at WG.NET. The final date is not confirmed yet (it should be very soon & I'll update this post for sure), but it should be around 21st of August (the updated info will be present at the bottom of this post). Here's a ... Trailer: In the era of cloud, distributed computing doesn't seem to be a big deal anymore - wherever you go, you'll run up into distributed app sooner or later. Unfortunately, their commonness doesn't mean that suddenly they've got…
Majority of my co-workers and acquaintances associate me (and my professional work) with the .NET stack. This association is so strong that when I tell them about my recent works with Scala/Akka, they think I'm nuts (or close to): What's the point of learning another stack if you've committed so much time and effort to master the previous one? Don't worry - I'm not going through the whole learning thing again in this post - this time I'd like to focus on something I hear pretty frequently from the fellow codecrafters: Yes, this Akka thingie looks decent and Scala…
Reactive applications. Scalable & responsive. Resilient & fault-tolerant. Event-driven & asynchronuous. The benefits of RAs are well and commonly known (if you're not up-to-date, make sure you get yourself familiar with Reactive Manifesto: start with the following link), but it's not the benefits I'd like to write about specifically today: What about the real cost? What about the effort? In a typical scenario, when a company needs an enterprise-ready solution to fullfill its functional needs - does it make sense to go for a reactive application? Not now, not here Obviously, there are some circumstances when going reactive doesn't make…