cbaleanu
Joined 14 years ago
Karma
332
Submissions
117
Member since
Jul 9
Recent submissions
Comment · 2 years ago
And we were all staring at the blinkenlights too.
Comment · 4 years ago
Please mark as [pdf]
Comment · 5 years ago
I have just upvoted this for you as I also loved the article :)
Comment · 5 years ago
I have to use an Oracle product for timesheets and besides the UI which is as you can imagine reading the previous comments, contains javascript code for a 'finite state machine for controlling the notification popup component'...
[edit: typo]
Comment · 6 years ago
And that is why HN is my favorite part of the net for about a decade now :)
Comment · 7 years ago
I get a 403 as well, no point in linking to something unaccessible just because reasons. Gdpr is hard but people in Europe should not be denied access just for the sake of immutable URIs
Comment · 7 years ago
Me and my team are happy users of keycloak[0] running in a docker swarm, pretty nice so far anf very good documentation. Building your own authorization/authentication solution is really nice as you learn a lot, but there is a lot of work involved.
[0] https://github.com/keycloak/keycloak
Comment · 8 years ago
Sorry but your facts are just wrong. Angular2 was announced in late 2014, just about the time when angular 1 was becoming mainstream used by big banks and the like. Look at Microsoft's blog from early 2015 announcing the use of typescript in Angular2. Linking some generic website does not make your comment less toxic and I would strongly suggest you get your facts right before posting stuff like that here.
Comment · 8 years ago
When I first joined my local photographer's club, one of the masters there told me that I need to accept that all the photos I will take will have been probably already shot by someone else.
Obviously not that realistic, but articles like this sure make it sound more plausible.
Comment · 9 years ago
Bad article, the author should have indeed put some more time into understanding what he is writing about.
var firstTeenager = people.find(teenager)
Comment · 9 years ago
Interesting find, by using that link, I gave FB some metrics about me and in return they sponsored my visit to the wsj article.
Comment · 9 years ago
Sure, the case study would be this https://aws.amazon.com/solutions/case-studies/rozetta-techno...
For architecture debates ( yes there were some :) ) the resources used would vary depending on the level of the issue at hand.
For inter-service communication we had a standardized API interface that would need to be exposed and most of the discussions would circle around how does the service solve a problem and what API does it expose to the outside world.
For general system workflow issues we would resort to diagrams or good old fashioned whiteboarding whose artifacts would also get converted into diagrams.
A general rule-of-thumb that I pushed was that every single service would be documented starting with the design process and ending with support info.
Hope that makes any sense :)
Comment · 9 years ago
From my experience, there are several issues that were mostly touched by the other commenters:
* auth / authorization: easy to grasp, tough to implement,
opens a world of architectural wtfs
* service configuration files / variables
* understanding that more microservices can run on
the same host
* system entry point, credential based, jumpbox
Happy to chat more, I am definitely not an expert on the domain but for what is worth I was technical lead (whatever that means to you) on an AWS Case Study project.
puful3tu at yahoo dot com