This means the entire system requires less cross-technology knowledge or specialized skills to build and maintain it. I didn't need other external systems like Amazon SQS, Kafka, or even just Redis to pass state between servers. Typically that would be REST or GraphQL with a JSON structure for transferring data to and from the front-end. Building a JS front-end means I need JS components, a front-end router, a way to model the state in the browser, a way to transfer player actions to the server and a way to receive state updates from the server. I didn't build a Javascript front end using something like React.js or Vue.js. What I find remarkable is what I didn't need to build. So I set out to see if I could create a fully distributed, clustered, privately networked, global game server system. What's more, I wanted to have fun doing it. I wanted to go further and create a fully clustered, globally distributed, privately networked, secure application. They often show the ease and power of LiveView but stop at multiple browsers talking to a single web server. Many great Phoenix LiveView examples exist. One of the best things about building web applications in Elixir is LiveView, the Phoenix Framework feature that makes it easy to create live and responsive web pages without all the layers people normally build. This, it turns out, makes us one of the easiest places in the world to run clustered and distributed Elixir apps, and if you’re into Elixir, you should give us a try it’ll take just a couple minutes to get started. We’re Fly.io, and we run full-stack apps on our hardware around the world.
0 kommentar(er)
