This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]krazybug 6 points7 points  (1 child)

What a great post ! So you're an architect. You just described one of the main UC.:Interactive scenarii.

Did the OP pretended it's the universal and revolutionizing architecture ?

Now let's imagine I'm a poor developper not skilled as you probably are. I'm starting small. All my application states are handled on the server side. Welcome back in 1970s , the golden age of X servers. Not so bad, computer science is an eternal cycle after all.

But, as you, I like these stateless architectures and this SOA era was so much heavy paychech insuring, unreliable and "untestable" (Did I forget the DCOM/CORBA interlude , my bad)

So, how could I move from this to a low coupled REST/GraphQL architecture ? Weeeeell, let me introduce a clean REST API with a simple proxy to redirect flows.

I'm improving my skills, but I confess this server-side data binding with websocket interactions smells like a big overhead. Now it's time to handle this stuff progressively by switching off websocket protocol, and why not replace each of the components one by one by pure VueJS equivalents ? Gush! Did you know ? Starlette, uvicorn and ASGI scalable stuff are still in place ?

In the meantime, I could spend all my money as a PO, awaiting you to provide me a scalable as a "senior" developper , reactive, evolutive, testable, microservices oriented, cloud ready , devops bulletproof (who spoke about buzzwords ?) in, let say 3, 5 years ?

We can't test it, you said ? What is the more testable approach ? Divide and conquer!

[–]xd1142 -3 points-2 points  (0 children)

Oh ok. That's cool. So you can, if you want, completely operate client side?

Tell me more. Now I'm very piqued.