Live data from Hacker News

Building Microservices: Free Ebook from O’Reilly and NGINX

nginx.com

31–36 of 36 posts

Re: Building Microservices: Free Ebook from O’Reilly and NGINX

#31

Earlier quoted context omitted.

I suspect that getting our developers to embrace not only this new architecture, but also the new paradigm of functional programming is a bridge too far. Regarding the "full-bore bus" question, I see it being that way for two reasons: 1. Distributed architecture. I think that the way to foster simple deployment of updates services is making them distinct deployable units, and the most obvious way to do that is to put…

What I should do, once I finish up the basic functionality (which could take a month or two working part-time), is copy this over to an empty box(es) and pound the hell out of it; see how much volume it can handle. My gut tells me the Ubuntu O/S can take quite a bruising. It'd be interesting to find out. Also there'd be some good lessons in there :) Remember, the goal of microservices is to completely decouple proces…

A microservices OO construct by definition would have to do a lot of honking around with the CPU before we got to the "work" part.

No doubt. While I'm enamored with OO myself (having begun my professional life in the late 80s when it was the thing), I think that anything OO would be internal to a given service, and the interfaces between services would be much more conventional, most likely a simply REST approach.

Re: Building Microservices: Free Ebook from O’Reilly and NGINX

#34
post #14

One of the main problems with breaking up a system into many independent (micro?)systems is that you can't easily combine two or more systems into a logical transaction. Or, in other words, it becomes increasingly more difficult to do things atomically to the complete system. Is this problem covered?

A concrete example we've faced. A certain operation requires writing data to N flaky services. You successfully write to N-1 of them, but the Nth fails. Now what do you do? If these N things were just database writes to the same DB, transactions would save you, as you could just rollback. Without that, the answer has to be handled in code -- do you reverse the previous changes (if possible) by sending delete events,…

You are basically describing the consensus problem [1] and one of the most popular algorithms used to solve is the paxos algorithm [2]

[1] - http://en.wikipedia.org/wiki/Consensus_%28computer_science%2... [2]- http://en.wikipedia.org/wiki/Paxos_(computer_science)

Re: Building Microservices: Free Ebook from O’Reilly and NGINX

#35

Earlier quoted context omitted.

I'm looking forward to this. We're about to embark on a (probably) .Net-based microservices project, although we'll probably use C# rather than F#. One thing I've found is that infrastructure stuff abounds for Java-based projects, doing much work for the message bus, metrics, and logging. But I find much less available for .Net, particularly for the latter two. Maybe you'll find some stuff that'll help me.

What are your reasons for using C# over F#?

The team has significant experience with C#, but none with F# (or indeed with functional programming at all). It seems like changing the architecture from a well-partitioned yet still monolithic service to a microservice approach is enough of a paradigm shift. Switching also to a functional approach may lead to some exploding heads.

Re: Building Microservices: Free Ebook from O’Reilly and NGINX

#36
post #4
post #2

Direct link http://nginx.com/wp-content/uploads/2015/01/Building_Microse...

I'm pretty sure the idea behind publishing this free book was gathering leads and potential customer-data for future marketing. You know, if it's free, you're the product and all that yadda yadda. By posting the direct DL link here, you are discouraging similar free offers in the future. If I were you and I appreciated free offers, I would consider editing my post.

> I'm pretty sure the idea behind publishing this free book was gathering leads and potential customer-data for future marketing.

This is exactly why the direct link should be shared. I'd bet that most HN users aren't interested in "future marketing."

Post reply on HN