I would like to implement things for two reasons: one is general good and second for money. The current project is for general good but with attitude to learn things. This time I want to learn several new things: AWS Elastic Beanstalk, Docker, Erlang web and AWS Dynamo for back end. Probably also some AWS Lambda / serverless things. In the end the idea is to build a service model that runs in the cloud without me worrying much of it later.
AWS
SC5, a local company here in Jyväskylä, arranged a hackathon with serverless topic. I joined the session and I understood something cool. I don't need any server instance since there are just cpu units in the cloud. Next thing was to start using those items. AWS Lambda (or serverless) was not usable as it is for web page. Amazon provided this elastic beanstalk instead. So, why not? You could use elastic beanstalk more easily with predefined set of languages but in the end I chosen to run Docker image inside the system.Erlang within Docker
Docker was selected because of it will be used in our company more heavily and I wanted to run and learn Erlang. I don't have currently any comments about Docker. It could be faster but otherwise it is okay. I selected Erlang because it is small and efficient. I run into N2O project some time ago after I was looking for web framework for Erlang. In the front page of N2O it has following image which I like a lot.
I am speed-o-holic regarding to software systems. For me a slow system means pretty much same as non-working system. Currenty I work with rails and that is awfully slow in many ways. Legacy is legacy. To tell more about N2O, I have still worked out without N2O technology. The idea within N2O is to serve (almost) whole web page through websocket. Every action you do on the page inits server requests and the page is changed accordingly the business logics in server side. Interesting technology but currently I am looking something else to learn.
Let's see how this goes.
Ei kommentteja:
Lähetä kommentti