This post is a prerequisite for an upcoming post. Here I’ll be creating a Whatsapp echo bot using Twilio and Nodejs. I’ll be making use of so as to save myself from the burden of going through the environmental setup. Repl.it Now, let’s get started 🏃‍ 🔑 Accounts and Keys First, Sign up for Twilio Once you’re done verifying your phone number, select Products > Programmable SMS and then continue to name your project. Feel free to skip steps for adding teammates — you won’t need that for now. You must now take note of some authentication keys you’ll need for building the WhatsApp bot 👇 The final step — setup your WhatsApp Sandbox — choose any number, and join your sandbox following instructions on the page. 👇 here Aaaaaand you’re done with credential setup! Don’t worry, that was the toughest part of this tutorial 😛 🚀 Getting Started So that we don’t spend too much time on setup, we’ll be using ! you can use within your browser. Head over , and click on new Repl 👇 Repl.it here Select express from the language dropdown and name your Repl appropriately (or not !!). After creating it you’ll be automatically redirected to the console. Replace the code in index.js with the following code 👇 Now start the server. You’ll get an error — Error: Cannot find module ‘twilio’ To resolve this you’ll need to add twilio module in Repl.it from packages menu on the left menu bar. Search for package there and add it. Hit Restart. An interactive browser window will open up and show default route message. Let’s go back to the , and put in a webhook URL for incoming messages. WhatsApp Sandbox We’ll be using route to receive messages sent to the bot, so we will be redirecting them to the above-shown URL (Your’s will be different, obviously !!) /incoming Add to the browser URL and save that into sandbox redirect URL. /incoming After saving the configuration in the Twilio Sandbox, you’ll need to add your phone number to sandbox participants by sending the code to the mentioned number. 👇 After adding participants try sending any message from your number to the Sandbox number and observe the Repl.it consoles log. 👇 🛠️Replying to incoming messages To create an echo bot we’ll need to send back the incoming messages. For that purpose, we’ll need to use twiml. Add the following code in /incoming route handler. const twiml = new MessagingResponse(); twiml.message(req.body.Body); res.writeHead(200, {‘Content-Type’: ‘text/xml’}); res.end(twiml.toString()); Index.js at this point will look like this. 👇 Hit Restart then and send the message again to the sandbox number. Now you’ll be able to receive the same message back from the bot. ⚡ What’s next? There you have your WhatsApp echo bot. In case you get stuck you are free to use my . Just replace Account Sid and Authentication Token with your own. Repl.it Needless to say, it can be modified to create whatever you wish to do. Ranging from notification services to Wikipedia bots. One particular scenario I’ll be sharing in a few days so do stick around.

The Sandbox

Creating a WhatsApp bot Using NodeJs, Repl.it and Twilio API

Something I really like about living in the city is the fact that it is made for the masses. Despite its many defects (the rain being one), Seattle is architected to enable hundreds of thousands of people to go through their busy days. It has a transportation system that interconnects different areas, it mandates different land usage policies for parks, residences, commerces and schools, and it provides restricted parking zones. It is designed for walking (assuming you like hills), it provides easy access to hospitals and it is guarded by police and fire departments. not But Seattle wasn’t initially a big city, its growth is more of a work-in-progress kind of thing. Like many other cities including all-mighty New York, Seattle is constantly under development and re-planning so it can to support even more people. It needs more efficient transportation (think subway), bigger highways, more parking and more recreational areas and residential zones. scale The similarities between city planning and software engineering are fascinating to me, they are well described by Sam Newman in his “Building Microservices” . Just like cities started as small towns, most services started as simple servers sitting under someone’s desk, and processing a few hundred requests per day. Given some time and if the idea is right, a service may become popular —that’s a great thing to happen except that the challenge of increasing demand quickly turns into a problem of dealing with higher customer expectations. This is similar to how we expect better transportation and more efficient police enforcement when a town evolves into a city. book I personally like the story of Twitter’s Fail Whale. As Yao Yue , the whale is a story of . Twitter started with a monolithic service called , represented as a gigantic box of functionality with enormous scope. While this might be the best way of getting  started, soon became too complex to reason about. Availability and slow performance problems surfaced as Twitter’s engineering team grew to a bigger set of people that were constantly adding features. This required more resources and a more principled architecture with better failure handling. Twitter nicely covered up its system errors with the image of a failing whale. mentions growing up Monorail Monorail If any of that sounds familiar, perhaps one should consider following Twitter’s approach of embracing a microservices-based architecture. Evolving a monolithic architecture into a set of microservices is about splitting a big I-can-do-everything box into more manageable boxes that have scoped responsibility. It is also about splitting teams into smaller teams that can focus on a subset of those services ( ). The resulting services are autonomous —like the teams who manage them—, so they can be independently deployed. Conway’s law Getting a microservice architecture right is quite an engineering journey, it requires discipline and patience. The Microservices Maestro (i.e. ) must be able to orchestrate principles of separation of concerns, the system’s overall cohesion, failure degradation, security and privacy. you I found that establishing some initial key architecture principles and ensuring they are attained can help alleviate some of these challenges. From the engineering and operational readiness standpoints: . There are many strategies for testing in production. One of my favorites is canary testing, a common practice in which less-stable code is enabled to only a small percentage of production traffic and “baked” for a predetermined period of time, before its broad roll-out. The ultimate test environment . Ideally, the time it takes from check-in to production is hours, not months. Getting there usually requires building a fully automated deployment pipeline that is able to safely and reliably make progress. Continuous deployment . Any feature that does not include basic monitoring of its performance, its resource utilization or its unexpected failure cases cannot be taken seriously —releasing it is like flying blind, hoping it will just work. In a system that scales to millions of requests per minute, things that are supposed to fail only 0.01% of the time will fail once every minute and will require almost immediate remediation. Hope is not a strategy in software engineering, but monitoring services and learning from their data is. Watch and learn . I usually avoid waiting for the perfect system to be implemented. It is better to release something small and improve it over time. Incremental improvements From the internal architecture standpoint: It may sound non-trivial, but sharing code that is tightly coupled with business logic is an and should be avoided in favor of autonomy and system decentralization. The force of autonomy. antipattern . Expecting that a contract between two services will not change is not realistic. Versioning support, backwards compatibility and upgradeability are essential for the long-term stability of any feature. Embrace contract changes . Services that spend resources waiting for responses can be wasteful. In the world of async, communication abides to event-based models with pub/sub services that don’t wait. There is no free lunch though, the diagnosis of event-based systems has proven to be a challenging area. Go async Stateless services are easy to reason about. In many cases they can be rolled back with minimum risk if their most recent version proves to be unstable. Rolling back stateful services, on the other hand, may cause multiple side effects that are hard to understand and increase the chance of data corruption. Furthermore, persisted data typically requires consistency models, high availability and quick retrieval. Don’t store what can be re-learned. . I really like the idea of Netflix’s Chaos Monkey – a service that is constantly triggering controlled failures in Netflix’s services in order to ensure that all services have sound failure isolation guarantees. Michael Nygard’s book recommends circuit breakers as protection mechanisms against fault propagation that are worth exploring. In short, circuit breakers are about cutting further communication to a service that is unavailable in order to avoid filling up queues of requests. Communication can be restored automatically once the external services are back online. Be resilient Release It! In general, I think scale is hard and often underestimated; it is an area that I expect will have dramatic innovation over the next few years. Did you like this article? Subscribe to get new posts by email. Image credit: Steve Dennis

Netflix

Twitter

Zones

Get a new perspective on tech news at geekonrecord.com

Winner of Noonies 2020 for the award Hacker Noon Contributor of the Year - MICROSERVICES.

2020 - Hacker Noon Contributor of the Year in MICROSERVICES

2022 - HackerNoon Contributor of the Year - Augmented Reality

2022 - HackerNoon Contributor of the Year - Facebook

2022 - HackerNoon Contributor of the Year - Privacy

Nominated for 2022 - HackerNoon Contributor of the Year - Facebook

Nominated for 2022 - HackerNoon Contributor of the Year - Augmented Reality

Nominated for 2022 - HackerNoon Contributor of the Year - Privacy

The Microservices Maestro

It is nearly impossible these days to scroll through your social media news feed without seeing a headline about cryptocurrency. The global phenomenon that is blockchain technology has swept the world in a relatively short time and impacted most global communities. The recent approval by is a clear sign that Bitcoin is here to stay. US regulators to allow Bakkt to launch a Bitcoin backed futures exchange New users that are looking for the best place to purchase Bitcoin for investment purposes or to use as a payment system digital currency are likely to open up Google and just go with the first cryptocurrency exchange that appears in their country. This is a big mistake. Beginners should always conduct their own research and the most popular exchanges are not always the best place for them to buy cryptocurrencies. This article will outline 3 reasons why you should consider using a broker instead of an exchange to buy cryptocurrency. #1 Greater Liquidity Pool For every asset that is bought or sold, whether it is cryptocurrency or forex, needs to have someone to sell to or buy from. The more people buying and selling, the more liquid an exchange is considered. When a new cryptocurrency exchange opens, it must populate all of its trading pairs order books with buyers and sellers to provide a market for its users to trade. This distributes the trading liquidity from existing exchanges that can negatively affect smaller exchanges that you might be currently trading with. Cryptocurrency brokers can avoid this problem by monitoring the market and acting on instruction from the trader to buy or sell based on an estimate or quoted price. By using distributing buys and sells across the highest liquidity exchanges in the world, the broker is able to increase its combined order book liquidity for the particular asset. This means its users are able to trade cryptocurrency assets with maximum available liquidity. #2 Reduced Spread and Slippage Fees A common mistake is selecting a new cryptocurrency exchange based on its low trading only. This might seem like an attractive proposition and logical decision to maximise a fiat deposit in exchange for more cryptocurrency. However, cryptocurrency exchanges with low liquidity in the order book will result in high spread and slippage fees that will eat into your funds. Some brokers can distribute buys and sells across the most liquid cryptocurrency exchanges (such as ) to identify where the highest liquidity is for that particular asset and split the order across those exchanges. Binance Traders using brokers benefit by getting the best market rate, lowest spread and minimal slippage that can increase profitability in the long run. #3 Increased Cryptocurrency Pairs to Trade Being stuck in an altcoin trade and not being able to get a fill can be a common problem on exchanges that offer 100 or 200+ tradable assets. Depending on the daily trade volume, cryptocurrency pairs on exchanges will have their own order book for each asset against fiat (e.g. USD) and also Bitcoin (BTC). This means less and less liquidity is available on the exchange that results in higher spread and slippage charges for the asset traded. Cryptocurrency brokers ability to offer assets without liquidity losses is a major advantage. Not only does this mean lower spread and slippage fees, users are able to use a single cryptocurrency broker trade, manage their crypto portfolio and store assets in the one location without having to register with multiple exchanges to trade. Conclusion If you’re looking to purchase Bitcoin or other cryptocurrencies, we would recommend doing thorough research of the company before hand to check spread and slippage fees associated with low liquidity order books. There is an alternate option to the deception, manipulation, hyper-inflation and high spreads by greedy cryptocurrency exchanges. The solution is to find a that provides better market rates and lower fees that will increase profitability in the long run as Bitcoin continues its rise in global adoption. reputable cryptocurrency broker Author Bio We aim to bring awareness and education to the digital currency space for beginners. For more information, visit us at hedgewithcrypto and leave a comment.

Binance

fees

Google

3 Reasons Why You Should Use a Broker To Buy Cryptocurrency

If Stitch Fix’s product offering is clothing personalization, this should also Show not tell.

One of the benefits of serverless is the pay-per-use pricing model you get from the platform. That is, if your code doesn’t run, you don’t pay for them! Combined with the simplified deployment flow (compared with applications running in containers or VMs) it has enabled many teams to make use of temporary CloudFormation stacks. In this post, let’s talk about two ways you should use temporary CloudFormation stacks, and why. Disclaimer : this shouldn’t be taken as a prescription. It’s a general approach that has pros and cons, which we will discuss along the way. Temporary stacks for feature branches It’s common for teams to have multiple AWS accounts, one for each environment. While there doesn’t seem to be a consensus on how to use these environments, I tend to follow these conventions: is shared by the team, this is where the latest development changes are deployed and tested end-to-end. This environment is unstable by nature, and shouldn’t be used by other teams. dev is where other teams can integrate with your team’s work. This environment should be fairly stable so to not slow down other teams. test should closely resemble production, and would often contain dumps of production data. This is where you can stress test your release candidate in a production-like environment. staging and then there’s production Having one account per environment is considered best practice. Some of my AWS friends would go even further and have one AWS account per developer. Personally, I have never felt the need to have one account per developer. After all, there is some overhead for having an AWS account. Instead, I usually settle for one AWS account per team per environment. However, for a particular project, I would often have a separate deployment CloudFormation stack per developer (but in the same dev account). This is especially useful when I’m working on feature branches. When I start work on a new feature, I’m still feeling my way towards the best solution for the problem. The codebase is still unstable and many bugs haven’t been ironed out yet. Deploying my half-baked changes to the dev environment can be quite disruptive: it risks destabilising the team’s shared environment it’d overwrite other features the team is working on team members would be fighting over (not literally!) who gets to deploy their feature branch to the shared environment Some of these challenges can be mitigated with feature toggles. Different feature branches can be live at the same time and only enabled for the developers working on them. Services like LaunchDarkly is great for this, even if using it with Lambda . requires extra work But what do you do when you need to deploy and test some unfinished changes? That is, the change is not complete and not yet ready to be reviewed and merged back into . Feature toggles won’t help you in this case. master Instead, I can deploy the feature branch to a dedicated environment, e.g. . Using the , that is as easy as running the command . This would deploy all the Lambda functions, API Gateway and any other related resources (DynamoDB, etc.) in its own CloudFormation stack. I would be able to test my work-in-progress feature in a live AWS environment. dev-my-feature Serverless framework sls deploy -s dev-my-feature Having these temporary CloudFormation stacks for each feature branch have negligible cost overhead. There is no traffic in the account since it’s only used by the team. When the developer is done with the feature, the temporary stack can be easily removed by running . dev sls remove -s dev-my-feature However, since these temporary stacks are an extension of your feature branch. They exhibit the same problems when you have long-lived feature branches. Namely, they get out-of-synch with other systems they need to integrate with. Both in terms of the events coming into your function, such as the payloads from SQS/SNS/Kinesis, etc. As well as data your function depends on, such as those that reside in DynamoDB. While it’s not a problem with serverless technologies per se, but I find teams move faster when they use serverless. Which means the problems with long-lived feature branches become more prominent and noticeable as well. Don’t leave feature branches hanging around for more than, say, a week. If the work is large and takes longer to implement, then break it up into smaller features. And when you’re working on a feature branch, integrate from master regularly (no less than once per day). running localstack vs talking to AWS Instead of spending lots of time to get tools such as working, I find it much more productive to deploy a temporary CloudFormation stack in AWS and run against the real thing. localstack The main downsides are: you need an internet connection deploying to AWS is slower than running code locally, which slows down the feedback loop The internet access argument is only relevant for a handful of people who spend most of their time on the road. I travel more than most and do a lot of work while I’m at airports, and internet access is rarely a problem for me. As for the slower feedback loop, it probably feels worse than it actually is. Most of my deployments are less than 30 seconds. But they do feel like an eternity when I’m staring at the screen and waiting for it to be done. To compensate for the loss of feedback loop, I also use tests as well as to run my functions locally while talking to the real AWS services. sls invoke local Temporary stacks for end-to-end tests Speaking of testing, another common use of temporary CloudFormation stacks is for running end-to-end tests. One of the common problems with these tests is that you need to insert test data into a live, shared AWS environment. As a rule of thumb I always: insert the data a test case needs before the test delete the data after the test finishes These help keep my tests robust and self-contained as they don’t implicitly rely on data to exist. They also help reduce the amount of junk that is floating around in the shared environment too. dev However, despite our best intentions, mistakes happen and sometimes we deliberately cut corners to gain agility in the short-term. Over time, these shared environments are filled with test data, which at times interfere with normal operations. As a counter-measure, many teams would employ cron jobs to wipe these environments from time-to-time. An emerging practice to combat these challenges is to create a temporary CloudFormation stack during the CI/CD pipeline instead. The temporary stack is used to execute the end-to-end tests and destroyed afterwards. This way, there is no need to clean up test data, either as part of your test fixture or with cron jobs. The drawbacks are: the CI/CD pipeline takes longer to run you still leave test data in external systems, so it’s not a complete solution You should weigh the benefits of this approach against the delay it adds to your CI/CD pipeline and decide if it’s right for a project. Personally, I think it’s a great approach and I’d encourage more teams to adopt it. However, the more data you have to clean up in external systems (that is, systems that are not provisioned as part of the temporary stack) the less useful it becomes. Summary In summary, here are two ways you can use temporary CloudFormation stacks to improve your development flow for serverless applications: use temporary stacks for feature branches to avoid destabilising shared environments use temporary stacks during CI/CD pipeline to run end-to-end tests to remove the overhead of cleaning up test data These approaches should not be considered as a prescription. You need to consider their pros and cons and see they fit with your constraints and how your teams work. Hi, my name is . I’m an and the author of . I have run production workload at scale in AWS for nearly 10 years and I have been an architect or principal engineer with a variety of industries ranging from banking, e-commerce, sports streaming to mobile gaming. I currently work as an independent consultant focused on AWS and serverless. Yan Cui AWS Serverless Hero Production-Ready Serverless You can contact me via , and . Email Twitter LinkedIn Check out my new course, . Complete Guide to AWS Step Functions In this course, we’ll cover everything you need to know to use AWS Step Functions service effectively. Including basic concepts, HTTP and event triggers, activities, design patterns and best practices. Get your copy . here Come learn about operational for AWS Lambda: CI/CD, testing & debugging functions locally, logging, monitoring, distributed tracing, canary deployments, config management, authentication & authorization, VPC, security, error handling, and more. BEST PRACTICES You can also get off the face price with the code . 40% ytcui Get your copy . here Originally published at https://theburningmonk.com on September 12, 2019.

Flow

Stacks

LaunchDarkly

Ask me for help about serverless

Read My Stories

A Case for Using Temporary Stacks when you do Serverless

"The Valve Index has almost everything we want in a next-generation PC VR headset. It delivers excellent image quality, believable VR presence and it has a revolutionary pair of motion tracking controllers." - Engadget State-of-the-art virtual reality today is described as "excellent," "revolutionary," and "believable," while in 1935 VR was literally a sci-fi idea. The Internet was also in science fiction stories before reaching , with the average person spending per day online. half of Earth's population 7 hours Many of the most popular services we use today like Facebook and Google are entirely "free," but we give up our data to these systems to make improvements. Attention is the time we spend on these platforms, and therefore also the data we give up, the Internet. which has long been described as the currency of As technology improves, attention becomes a more competitive landscape, and the amount of data we give up increases. In short, there's a multi-trillion-dollar fight for our attention, and . These technologies include 5G, which means faster connections, and higher-fidelity consumption of content that's 4K and on bigger, more colorful, more immersive displays. our brains suffer by literally devolving While we're plugged into our laptops and phones more directly, we're also connected in the background with apps constantly pinging data back-and-forth and IoT devices capturing live information. In our search for ever more immersive technology, the drive for virtual reality is obvious. As smartphones get bigger and bigger screens, there's clearly a limit. The newest Samsung Galaxy has a , but it can only get so big before it's uncomfortable. There's a bit of a gap to leap from smart phones to VR, but it will easily be bridged, in the same way as the evolution of phones. 6.7" display No one wants to walk around with a bulging Nokia in their pocket, but once the iPhone was released, smartphones became a cool, normal thing to own. In the same way, current VR is more of a niche, hipster product. Now imagine, a few years down the line, that VR has simply undergone a normal technological evolution and has become a slim, portable, fashionable product. You can't exactly imagine everyone walking around with a box in front of their face, but you can imagine everyone walking around with VR glasses, or even better, a VR implant. When (not if) that happens, advertisers will again compete for our attention - but in a much more immersive playing field.

Engadget

Facebook

Samsung

Let's connect!

The Future of VR: An Arms Race for Attention - on Steroids

BUNCH

Glue

Lumen

Get in Touch!

[A How To Guide] Planning the Technology Stack for an Event Sourcing Project

When was the last time you actually met someone who wasn’t carrying a smart-phone in his/her pocket? Before your mind enunciates the obvious answer, let me just say: Not in recent years, of course. According to the , in 2019, there are 2.71 billion smartphone users in the world today. statistics Now, before this whopping figure surprises you in any way, let this be out in the open. This is just the beginning. The numbers keep on increasing each day. In light of this huge achievement, it is only believable that small businesses, large scale businesses, enterprises are looking to create mobile applications with the definite purpose to magnify their existing business applications. Albeit, there’s a worrying that says that the demand in the market for application development will grow five to six times faster than the capacity of the tech departments to complete it up to 2021. statement from Gartner The most generalized challenges came across a mobile app development company in their efforts of mobile application development encompass the lack of skills, limitations, technical stability, etc. This is why it would be a wise decision to choose the to overcome the following promotional challenges for a new mobile developed mobile application. top mobile app development company Lack of Expertise Image Source There is a distinct shortage of versatile application designers who have a fair measure of involvement in the field. This is demonstrating to be perhaps the greatest test for organizations who are enthused about expanding their application development or make their current applications hearty and increasingly useful. Costly Process Image Source 62% of the organizations have admitted that they wound up spending north of $500,000 so as to manufacture just around 1 to 3 applications! There were 13% however who said they spent about $5 million for the equivalent. Most organizations I know don't have as profound pockets as they might want. Aside from the cash venture, the time speculation adds to the expense too. Time Constraint Image Source The way toward structure an application for business does not occur without any forethought, which implies that organizations need to contribute a mess of time sitting tight for the application to be constructed, tried, and afterward discharged on their preferred application store. This time increments much more when the organizations are building separate applications for isolated platforms. Multi-Platform, Multi-Device Mobile App Development Image Source There are numerous organizations that may need to build up the application for various gadgets, including iPads, iPhones, Android, and Window telephones, tablets, and work areas dependent on Windows, Linux, or Apple, notwithstanding different working frameworks crosswise over various gadgets. In such cases, portable applications that they are creating would need to work in a reliable way over every one of these platforms and gadgets. This is, lamentably as convoluted as it sounds and a significant test in the domain of versatile application improvement. Picking between Native, Web, and Hybrid Mobile Apps Image Source This is a choice that should be made ideal toward the beginning of the procedure. As an entrepreneur, you would need to choose which sort of application would be most appropriate for you – web applications, half breed applications, or undeniable local applications. Every one of these sorts of applications accompanies their own experts and their own arrangements of difficulties during the formative platform and past. Beating the Challenges Image Source Presently, only one out of every odd organization has the assets or the cash to have the option to beat these difficulties when they set out to fabricate their very own applications. It is consequently that many of them are selecting to utilize fast application improvement apparatuses. These apparatuses enable the organizations to create refined and completely practical web applications, crossbreed applications, and even local business applications in a loT shorter time range when contrasted with customary strategies for application improvement. This is significant because of the way that the measure of conventional coding required here is decreased impressively for this situation, and for some applications, it is wiped out altogether. The genuine development some portion of the procedure is bolstered by a curated scope of activities which revive up the pace and make it less complex also. Things to Check Out In An App Development Platform Image Source The platform you pick must be adaptable enough to enable you to assemble applications that can be kept running on different kinds of gadgets and platforms and can coordinate with all SQL and different databases You should pick a platform that is structured thinking about the business standard innovations which would ensure that a wide range of alternatives of development can be cultivated from a no-code/low-code way to including custom code and even outside schedules as indicated by the developing industry and its changing necessities. Henceforth, backing up one of the most important points as to why a business should go with the top mobile app development company. To put it succinctly, choosing the top mobile app development company will allow businesses to future proof their applications and help in overcoming the promotional challenges for mobile applications development so that they can evolve with time.

Apple

Moon Technolabs Pvt Ltd

Overcoming The Promotional Challenges for A New Developed Mobile Application

System Center Orchestrator can automate reoccurring tasks related to support and management of the Exchange organization. In particular, it can be used to create a custom interface where support organization can request precise actions like message tracking logs and mailbox moves. This makes executing basic tasks easy as one does not need Exchange permissions or be forced to use tools like Exchange Management Console or Powershell. Speaking from personal experience, I have found Orchestrator to be extremely powerful when it comes to automation. Integration packs for Exchange, SharePoint and Active Directory make room for easy automation solutions. As someone who has taken a liking to Orchestrator and many functionalities it has to offer, I thought it would apt to give the readers a concise overview of some of its prerequisites. Let’s dive in. What do you need to install Orchestrator? Before configuring Orchestrator on their system, here are a few things that need to be in order. Orchestrator Server • minimum requirement: 2008 R2 SP1. Windows Server Operating System: • minimum requirement: 4.6.1 .NET Framework: • minimum requirement: 4.0 PowerShell: • minimum requirement: 7.5. Note: this is part of the Web Server (IIS) role and is enabled automatically by the provided InstallRolesAndFeatures.ps1 script. IIS: • The PowerShell script, InstallRolesAndFeatures.ps1 provided by UiPath will automatically add features and required roles to the application server (s). Server Roles and Features: • It will enable the website to redirect call to http ( ) instead of http (http: // clothingRIC.com). URL Rewrite: https://clothingRIC.com •	Web-Deploy Extension: minimum requirement version: 3.5, 64bit version. It is required only for installations of PowerShell script such as Azure one. SSL Certificates On all browsers where users access the web application, HTTPS is mandatory for communication between Robots and Orchestrator. Three types of web certificates can be used. •	These web certificates are issued by trusted authorities like GoDaddy, Comodo, and DigiCert. Since there’re plenty of options available, users should read an before making the final decision. You need to import web certificate to Server Certificates in ISS. Remember, it’s imperative to know “issue to” entity as Windows installer will prompt you to provide it. SSL Certificate Guide •	Here, you are a Certification Authority which issues certificates that are trusted in the Windows domain. •	You can also work with self-signed certificates but they’re not recommended for production. Since this certificate is not trusted inside the domain, its public keys need to be exported and then imported to all Robot machines. Redis Redis is an open-source, in-memory data structure used for caching and message broking. It’s shared amongst Orchestrator nodes, making way for instant synchronization. You need Redis in a cluster environment. Otherwise it will not function. When it comes to the Redis database, there are two options available; the open-source Redis Server and Redis Enterprise, which is developed and supported by RedisLabs. Redis Server can be installed on Linux and Windows while Redis Enterprise, built on the Redis platform offers extra features and deployment options. The following information is maintained in Redis: •	Session state •	Robot heartbeat cache •	User session from the browser •	Association between organization units and users •	Association between users and roles •	Settings •	License information Redis also sends commands such as start jobs to all Orchestrator nodes. This command is then sent further to correct robots. Keep all packages (.nupkg files ) synchronized on all nodes if the user sets NuGet.EnableRedisNodeCoordination to true. One can also enable SSL encrypted connections among Redis service and Orchestrator nodes via LoadBalancer.Redis.ConnectionString web.config parameter. SQL Server To run the orchestrator, you need SQL server machine with the minimum requirement of 2008 R2 with SP3, Standard or Enterprise Edition. •	You can install the SQL Server product on the same device as the Application Server (which is not recommended for production environment) or provide it as a separate machine. SQL Server machine does not need to be dedicated to Orchestrator; it can be shared with other applications. •	If you’re planning to connect Orchestrator with the database through SQL Server user, first enable Windows and SQL Server Authentication mode. Otherwise, Windows Authentication mode will go the job. •	Use default collation sequence - Latin1_General_CI_AS. •	It is necessary to have SQL Server Management Studio to configure the domain user’s login that connects to SQL Server. •	Before you proceed to install Orchestrator, you need to configure the SQL instance you intend to use. Network Load Balancer Through a network load balancer, you can distribute the load to multiple nodes, enabling a much higher quality of performance of the Orchestrator instance. Moreover, when one node fails, the rest can carry the load, ensuring zero downtime. Personally, I recommend F5 load balance with a predictive algorithm. With the loads distributed to better performing nodes, the . Orchestrator performs better Elasticsearch Server Elasticsearch is an option and can be used to store messages that have logged by the Robots. These logs can to a local SQL database or ElasticSearch, enabling users to have non-repudiation logs. While using both SQL and ElasticSearch, both will not affect each other if one encounters an issue. Although Elasticsearch is a cross-platform product that runs on Windows, Unix and Linux, it needs Java. Lastly, combining Elasticsearch with Kibana will help you create custom views based on logs sent to Elasticsearch. Conclusion Once you’ve everything in order, Orchestrator should install without any issues. It’s a flexible platform that can perform automation task with great efficiency. Especially when used with SharePoint, it can create custom tools that anyone can use without needing permission in Exchange.

Keep

SSL Certificates and Some Other Prerequisites for Installing Orchestrator

seems to be buzzword of late, and I do like the idea behind it. There is a bit of rebellion there. Cryptocurrency Cryptocurrencies found their when bitcoin officially went live. The concept of bitcoin was introduced by the pseudonymous person or persons . first success in 2009 Satoshi Nakamoto The cryptocurrency also owes part of its success to the state of the world at that time. Many people were leery of banks after the financial crisis in 2008. So for some, the line of thought was, if the current monetary system was in shambles, what’s so bad about creating a new one? Enter cryptocurrencies. Street Fighter and Cryptocurrencies: An Unlikely Match The idea behind cryptocurrencies also reminds me of a video game I used to play with my siblings growing up, The game featured fighters from around the world who would battle each other in the streets of different cities. Each player had a unique way of fighting. Street Fighter II. While the game has nothing to do with cryptocurrencies, per se, here is the subtle parallel of cryptocurrencies to Street Fighter. Both entities — and cryptocurrencies — solve problems in a seemingly unconventional way. One has fighters duking it out on the streets of random international cities. Hadouken! And the other says Sayonara to the traditional currency system to build one of its own. Street Fighter Both and cryptocurrencies rebel against the status quo to solve an issue in a new way. Trouble settling a dispute? Ay, let’s brawl it out in a city of choice. Street Fighter Trouble trusting that your money is in good hands, and always safe? Maybe bitcoin or ethereum is the answer. So personal anecdote aside, here are a few questions in Q&A format with more information about cryptocurrencies, in case you are interested. Cryptocurrencies: The Q&A 1. What is a cryptocurrency? It is a digital currency made secure through cryptography. (Cryptography uses secret code to encrypt and decrypt data). ( ) Source 2. Isn’t bitcoin a cryptocurrency? What exactly is bitcoin? Bitcoin is the first digital currency to succeed at getting rid of the need for a central authority. The users of the blockchain network, where bitcoin transactions take place, are the ‘authorities’ that confirm the validity of a transaction. is a great article in about bitcoin. ( ) Here WIRED Source 3. What are a few other types of cryptocurrencies? Here goes another interesting term — This term refers to a virtual currency that is an alternative to bitcoin. include Litecoin, Ethereum, Dash, Ripple, Monero, to name a few. ( ) altcoin. Altcoins Source The last question I guess I will ask you, the audience. What's your take on cryptocurrencies? Are they something that you think will really change the way we think about and use money?

Litecoin

Monero

Dash

So, what do you know about cryptocurrencies?

Photo by on Carl Raw Unsplash So you decided to create something amazing for someone you love and have zero ideas about what you should do. Well, look no more, since I am about to walk you through making your first quiz game, that amazes everyone. As my first anniversary with my girlfriend was coming up, I had to think of something pretty darn good. I study computer science, so naturally, it made sense to include my skills from everyday educational life. While thinking about it, I knew I wanted to make something related to us as a couple, but also to fun and easy to “play.” And here is what I’ve come up with: Smart phone App. Quiz. Rewards. Seems pretty straightforward, right? It is actually. All your partner has to do is open fields, do a little riddle (that would make sense for your relationship) and you reward them with a gift. We are done talking, let’s begin with the project. Writing down ideas for questions and rewards Take a piece of paper and immediately start writing everything that you can come up with related to you and them. Make funny jokes but also leave some space for mystery and let them guess what could be the reward. This gift can be made of many smaller gifts, such as flowers, a necklace, candy, and so on. App itself I created this app in . It is free to use and pretty easy to install and setup. Android Studio Create a new project Welcome Screen of Android Studio When you open AS, Start a new Android Studio project. It will ask you next, what kind of project you want, and you should begin with an “Empty Activity.” Types of Projects You can name your project, select the location, and also tell AS, which android version you want and it tells you how compatible the devices would be. Project configuration Chart of android devices When you set up everything, click Finish and that is all, a new window will open and get you started. Beginning of the project Once you begin, there are no limits, everything in the Studio is available to you, and your imagination has to be something that widens the horizons of your app and gets that wow effect! Crucial things in Android Studio are Pallete and File Overview. Add elements from the Pallete and view every file (Activity, Layout, String, Image…). As far as my ideas go, I will propose the next things: Welcome screen Make them feel at home and tell them how much you love them with a little message and add a button to enter the game. Also, add a background image and make it warmer. When you go to another screen, you should create a new activity and for the best for it to be empty again. Right-click on layouts to create a new one. Quiz Fields of questions. Create a lot of buttons on the screen and let them open new screens after clicking on those. The same thing with opening new activity as before, just create a new activity and name it well! This is from the app that I created and how it might look for you as well, but feel free to create your own ideas! Amongst the gifts and questions that can hide behind the fields in the quiz, what you can do is put a short message, pouring your heart out if that is something you like! And after the short message and telling them how much you love them, add some favorite couple , which is also pretty easy. pictures as a slide show Last words of motivation If this is your first time programming, it might get frustrating and do not worry since that is what comes with it. Nevertheless, stay determined and do not give up. everything. Google Hope you like the app idea and I hope you have nice time together after making something awesome! If you like this story, check my other ! stories on Medium

Read my stories on medium: https://medium.com/@lazar.gugleta

HackerNoon Tech Stories Archive September 15th, 2019

Creating a WhatsApp bot Using NodeJs, Repl.it and Twilio API

@worm4047
Abhishek Chaudhary

The Microservices Maestro

@geekonrecord
Geek on record

3 Reasons Why You Should Use a Broker To Buy Cryptocurrency

@hedgewithcrypto
hedgewithcrypto

“

@patricia-mou
Patricia Mou

A Case for Using Temporary Stacks when you do Serverless

@theburningmonk
Yan Cui

The Future of VR: An Arms Race for Attention - on Steroids

@FrederikBussler
Frederik Bussler

[A How To Guide] Planning the Technology Stack for an Event Sourcing Project

@keithmifsud
Keith Mifsud

Overcoming The Promotional Challenges for A New Developed Mobile Application

@jayanti-kataria
Jayanti Kataria

SSL Certificates and Some Other Prerequisites for Installing Orchestrator

@EVelyn.J
Evelyn

So, what do you know about cryptocurrencies?

@turnsofphrase_
Obinna

I Made A Game for my Girlfriend as a Gift for Our Anniversary. You Can Do it Too

@lazar.gugleta
Lazar Gugleta

Top 100 Places to Learn to Code for Free Online in 2019.

@oleksiy
Oleksiy

HackerNoon Tech Stories Archive September 15th, 2019

@worm4047Abhishek Chaudhary

@geekonrecordGeek on record

@hedgewithcryptohedgewithcrypto

@patricia-mouPatricia Mou

@theburningmonkYan Cui

@FrederikBusslerFrederik Bussler

@keithmifsudKeith Mifsud

@jayanti-katariaJayanti Kataria

@EVelyn.JEvelyn

@turnsofphrase_Obinna

@lazar.gugletaLazar Gugleta

@oleksiyOleksiy