ค้นหาจากครู ภาษาอังกฤษ หลากหลายคน...
Brazil flagEvandro Pires
Function as a Service and Java. Is that a good idea? In the last IT event that I went, I saw many talks about Function as a Service (it's also known as Serverless). That's a new kind of architecture and, different as the name can suggest, you'll need servers, but you don't need concern about that. During my article I'll use the acronym FaaS for Function as a Service. In terms of concept and architecture I've liked so much of FaaS. That architecture forces you build codes very cohesive and, because of that, you can reuse the function easily for another functions. The main principle of FaaS is that you don't need concern about servers. The vendors offers to you solutions while you just need to configure the scale, the level of availability and some others high level configurations. The common vendors for that kind of architecture are: AmazonWS Lambda, Azure Functions, Google Cloud Functions and IBM Cloud Functions. Talking about my PoCs, I built two proof of concepts: the first one are two functions where one of that add a product and the other get the product. For that PoC I used Java 8, IBM Cloud Functions and Cloudant NoSQL Database. My second proof of concept is a function that returns a number in words with Java and Python. The idea was benchmarking both functions to know what the best language to make my functions. To test my functions I built a JMeter test that add an product and get the same product. I ran with 8 threads (limited of my free tier on IBM Cloud) and 100 iterations. The test ran in 2 minutes with a throughput of 6 reqs per second. The first sample ran in 1 minute and 17 seconds. It was 8 threads and 100 iterations. The result was 10,4 reqs per second. The second sample ran exactly equal. The first sample ran in 1 minute and 15 seconds, while the second sample ran in 1 minute and 3 seconds. Both executions was with 8 threads and 100 iterations. In the second sample with Python the performance was almost 20% better than the first sample. When I started those tests, honestly, I was expecting a biggest difference between a load test with Java and Python. My intuition said me Java would be slower than Python, and isn't true. Python performs better in the second sample when the function are started, but not too much. With these results my conclusion is whatever your programming language. It's more about how you can build your code more cohesive and shorter. In Java your package must be thin. But don't forget the pros and cons of FaaS, that's will guide you if you'll really need to use FaaS.

การแก้ไข · 3

0
Paddington, italki has a hidden limit to the size of finished edited text and it can be very frustrating for us editors. In reality, every time you use a highlight (different text style, marking, or color) it actually adds the equivalent of forty or so characters to the size of the text without telling you or showing this in the "remaining count". Then when you try to save it, it either ignores your save or gives you an error because the final text is too large. The way around this is to recognize when the original text might be too large to edit successfully, such as the article here you responded to. Instead of correcting you need to ask the poster to divide their article into two parts and repost. This way, each part will be small enough that your edits will take. I hope this helps.
0
Hi Paddington! Thank you so much. After your review I read my entry again and the errors were clear to me. :)
0
I tried to correct your journal entry twice, but both times I added in all of my corrections and color-coded them, and then italki won't let me post the corrected entry for some reason! So, I corrected a bunch of smaller errors, but two things stuck out to me: pay attention to your conjugations for the third person singular of verbs (he/she/it offers, they offer), and make sure you have number agreement with your verbs (he/she/it was, they were). Most of the errors I spotted boil down to one of those two things. One other thing to note: you want to use the verb "to worry about" and not "concern". You're probably thinking of the reflexive verb "to concern oneself with smth", but that doesn't go with the preposition "about". So, you'll have to choose one or the other. "To worry about" is more common and more colloquial than "to concern oneself with smth", so I would choose the former. There are a few other issues with phrasing, places where I just rewrote part of the sentence, but other than that...it's a good journal entry. =)

ต้องการความก้าวหน้าที่เร็วขึ้นหรือไม่

เข้าร่วมชุมชนแห่งการเรียนรู้และทดลองใช้แบบฝึกหัดฟรี!

Don’t miss out on the opportunity to learn a language from the comfort of your own home. Browse our selection of experienced language tutors and enroll in your first lesson now!

Start Learning Today