I am a fullstack developer focused on creating Webapps and Websites built with React/Redux and PHP Backend. In love with APIs and always available to test new tech..;)
Nothing here yet.
No blogs yet.
Next.js is too opinionated for me... My problem currently is, that once i compile on the server, the server throws an error because he can't parse class names. (Syntax Error). I guess it's because of the style-loader fallback of Extract-Text... Thanks for the tipps, gonna check it out. If you have some code to show, i am happy af ;)
What you are referring to is the schema.org structure of Hashnodes Source Code. https://searchenginewatch.com/2016/07/19/the-complete-beginners-guide-to-schema-org-markup-2/ That has nothing to do with the editor (besides the sign that their code is clean and they use all ressources;) The Editor is written in Draft.js (react) https://draftjs.org/
Depends on your usecase. As far as i know, the best solution is to make an entry layer for your request, which authorizes and authenticates the request. After that barrier i'd completely discard an authentication, if you need information between the services you can use headers, payloads or basically anything. The only real requirement is that the services are not accessible without going through the Auth Layer. The most microservice setups i have seen work that way. If the User doesn't call a service directly, why authenticate? Just throw everything in a closed network and let the auth layer decide who can enter and who can not. If you need to do it any other way, i'd also suggest JWTs like Arpit Mohan did. They are safe, can store information and do everything you need. I'd still just use one call (service) to generate the tokens, all other services just request the token.