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]
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
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
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.
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.
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.
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
And the most important issue I keep seeing across the systems I work with is documentation and speed of onboarding new staff.
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.
Same story here, but I have been living in Eastern Europe and then Australia and then back for a few years now, paying for unblock-us and Netflix US which I signed up for while in the US.
Ever since my first experience with Netflix powered by a Roku I have been praising how awesome it is, trying to get my friends to sign up for the service.
And then the geofencing crap happened but the service was suddenly available in our country, but with minus 90 percent of the content - a lot of my friends signed up and then cancelled their subscription.
I for one am seriously thinking about canceling both unblock-us and Netflix as I suddenly feel a 'localized' citizen with no way to legally we global anymore and it sucks.
sshfs or winSCP on windows are great, beats text mode for me especially when editing files on stable known hosts.
I wouldn't bother using either for ephemeral instances though.