Web session clustering provides freedom of load balancing user sessions to any app server without losing intermediate user session data. Why? Because underneath it takes advantage of in-memory distributed caching technology which ensures that user sessions are available in memory regardless of which server is hit.
There's a bunch of people out there that think I don't like docker, they are wrong. I just never understood the hype about it since I didn't see, (and still don't) see it being used at large and people seem to understand that as being against it.
If you haven’t used Vagrant before then hopefully this will not only help you get up and running with Apache Kafka but also get introduced to Vagrant. Vagrant helps to create and configure lightweight, reproducible, and portable development environments.
Since Gnome 3.8 has been out in the portage tree, a lot of problems arise when you try to emerge something. If it was only when you update the system, it would be OK, but this arises every time you try to install something.
I’m personally tired of hearing about how new, growing, successful businesses do things. I felt different about this Spotify presentation even though it fit the mold. Autonomy and collaboration are built into organizational structure.
When you work on very talented teams, you will frequently know the answer to whatever the problem is well before the rest of the organization. When these conversations pop up, you should look a little closer to home. It is possible you have Smartest-person-in-the-room Complex.
AWS customers are saving money mostly because you can rent what you need vs. buy for the peak traffic. They are also gaining not only increased scalability but increased flexibility, reduced response times and reduced development times.
The tech industry needs to be more inclusive of women and people of color. It's about having the largest pool to draw excellence from. Sadly, most of the discussion, even the discussion that is advocating for a more inclusive culture, itself is divisive.
Because we know what it is like to read and debug a 500-line method. And we don’t want to go through it again. Because we’re sure the other guys’ code can use improvement. Even if they thought otherwise.
Amazon Web Services offer various tools for building distributed and scalable workflow applications. One approach for building such an application is to use topics and queues for connecting the distinct steps in the workflow process.
While some providers tout the evils of running agents on your system and can oft be heard shouting, “no agents here!!!”, we prefer to keep an open mind. That being said, like most things in life, agents have their pros and cons.
In an agile team, especially with continuous integration, we don’t notice handoffs. Continuous integration makes handoffs trivial. If we work together to achieve a feature, as in swarming or mob-programming, we don’t even have handoffs.
A few days ago I made the case that the most efficient code review process is one that deals with reviews within minutes of hours of the commit they pertain to. I didn’t dwell so much on the difference between pre-commit reviews (that until they “pass”, the commit can’t go in), and post-commit reviews (which suggest prioritized follow up work in the case of “fail”).
We need to be aware of any peculiarities of the real development process to select a tool that would be capable to replicate it. So, what are the things to note about the process that one would definitely need in the tool?