In my previous post NGrams and Edge NGrams – computational complexity, I explored the runtime implications of working both with NGrams and Edge NGrams. This is a follow-up post that will build on the previous one so if you are not familiar with these terms, I would suggest checking it first. In this post, I would like to take a look at the space requirements of NGrams and Edge NGrams and how to estimate the size required to store the data intended for your indices.Continue reading “NGrams and Edge NGrams – space complexity”
In my current project, we do a bunch of work revolving around Elasticsearch and enabling our customers to quickly access the relevant portions of our large data set. A couple of weeks ago I was asked to come up with a method to compare the costs of working with NGrams and Edge NGrams. I tried to make my life easier and look around the Internet for somebody else’s breakdown but I didn’t find anything I would like. So I decided to bite the bullet and do the work myself. In this post and the follow up one, I would like to present my way of reasoning about NGrams and Edge NGrams.
In my previous article, Spring and Amazon Web Services, I provided a brief introduction to Spring Cloud AWS module and what you as a developer can expect from it at this point in time. One thing that is not obvious from the official documentation is how to use this module when your Internet connection is restricted by a proxy server. In this post I will outline how to approach passing of proxy configuration for both Java-based and XML-based configuration. This aspect of configuration will probably be addressed in the future releases however it might help you now in case you work with this module and need your application to work with a company proxy.
Continue reading “Spring Cloud AWS with proxy settings”
Amazon Web Services (or AWS) is nowadays one of the most common choices of the infrastructure and hardware providers to use and deploy to. Many Spring applications have tackled challenges of integrating the application infrastructure and the underlying layer. These in-house solutions differ in complexity and the degree of sophistication when it comes to the design and the actual functionality. One of the key attributes of success of such a solution besides the proficiency of the team is the overall knowledge and experience with AWS Java SDK. Based on the way Spring Framework has been designed and maintained, it was only a matter of time before Spring introduced a module dedicated to bridging the gap between AWS and the way we configure our Spring applications. I want to discuss some aspects of adoption of this relatively new module in this post and also point out what to look forward to and what to watch out for.