shrimpi
Re:What to call an API Gateway combined with a sidecar?
on Tuesday February 25, 2020 @08:21PM (#22419419)
Found the paper https://www.usenix.org/system/files/conference/hotcloud16/ho.... Puts forward a very nice overview of distributed container patterns. But maybe in articles that Google Scholar says cite this one, a name has already been found for this specific combo. Thx for the lead.
What to call an API Gateway combined with a sidecar?
I'm writing an article that discusses the advantages of using the API Gateway pattern combined with a sidecar within the same microservices environment. These two patterns are often thought of as an either/or decision because they overlap. In the article I propose using both in some situations. What is a good descriptive term for such an architecture? One option is to call it "hybrid...
Re:When AWS, Azure, or GCP Becomes the Competition
on Monday October 28, 2019 @07:48PM (#21383010)
This one is easy: patents
Re:Ask HN: Anyone try a 2-way coding interview?
on Monday September 09, 2019 @09:29PM (#20924330)
This is so great.
Re:Ask HN: Anyone try a 2-way coding interview?
on Saturday August 31, 2019 @02:11PM (#20847889)
Yes, this is clearly a tradeoff in the approach in that 2-way interviews have the potential to be extended, could even take twice as long. Working on a question/problem together is a great way to establish a working relationship from the start. If it goes really well, we'll always remember it. You gain insights into my thinking process, and I hear yours. This, as opposed to me just asking you questions one-way. For this to work though, maybe a short initial meeting to get to know each other on some basic level and to set the stage for the exercise would be a great way to start.
Ever had the opportunity to try this approach in some way? If so, how did things go?
Re:Ask HN: Anyone try a 2-way coding interview?
on Saturday August 31, 2019 @01:54PM (#20847764)
Great anecdote. I would expect the approach to level-set the relationship from the start. And, in a way, when both sides of the decision to hire take turns asking questions, the participants will find themselves in a better state by cooperating while they may find themselves in a worse state if they do not, which provides prisoner's dilemma outcomes. For example, in a coding interview, I'll go easy on you because I know you'll go easy on me.
And so how did things go from there?
Ask HN: Anyone try a 2-way coding interview?
Would it be fair in a coding interview for the interviewer to be asked by the interviewee to solve similar problems? Such that the interview process is 2-way: if you ask me to solve a problem, then I get to ask you to do the same. So we both come prepared to a coding interview as both interviewee and interviewer. If we're going to work together, I'm just as interested in your abilities as you...