98% Off: Get the Complete Amazon FBA A-Z Bundle for Only $29

The world of retail is dominated by Amazon. The ecommerce giant has been the go-to platform for individuals and businesses who want to sell their products. By selling on Amazon, you can reach a far larger customer base found on any of the other e-commerce platforms. Amazon’s FBA services makes it incredibly easy to sell […]

The post 98% Off: Get the Complete Amazon FBA A-Z Bundle for Only $29 appeared first on designrfix.com.

WordCamp US 2019 to Offer Free On-Site Childcare

child coloring
photo credit: Aaron Burden

WordCamp US announced today that the event will be offering free on-site childcare for children aged 6 weeks to 12 years old. Organizers have contracted A Helping Hand, a licensed conference childcare service company based in Virginia Beach, VA, to provide childcare for all three days, with flexible drop off and pick up throughout the day as necessary.

When WCUS tickets went on sale in May, parents who registered had the option to indicate whether they would be interested in on-site childcare during the conference, as organizers considered different childcare options. This is the first time WordCamp US has offered it as part of the event. WordCamp Europe has included childcare for years and a handful of other camps have also had it available in a varying capacities, including WordCamp Nordic, WordCamp Pittsburgh, and WordCamp Vienna.

Parents interested in using this service at WordCamp US will need to pre-register by selecting a “Parent with Kids ticket.” Registrants will receive an email with a pre-registration link to complete the signup process on the childcare provider’s website. Both lunch and snacks will be provided, so parents will not be required to pick their kids up for lunch.

The availability of childcare makes it possible for single parents to attend and speak at events. It can also be helpful for parents with small children who are unable to be separated from their caregivers for long periods of time. With WordCamp US opting to provide childcare at this year’s event, it’s clear that this is a growing trend to help promote diversity at WordPress conferences.

Baron Launches Weather API for Public Safety

Baron, a weather intelligence company, has announced the Baron Weather API for Public Safety. Through the API, developers can integrate quality-controlled weather data into devices and services of many kinds. From websites and apps to desktops and smartphones, the integration capability of weather data is vast and the Baron API is ready to serve.

Sound Off! How Has ManagedWP Weathered the Acquisition?

Back in September of 2016, GoDaddy acquired ManageWP. What was odd about the acquisition was the amount of backlash that was generated by ManageWP customers.

While most were happy for Vladimir Prelovac, founder of ManageWP, many customers worried about GoDaddy’s reputation, unsatisfactory service, and how such a great service would fit into GoDaddy without changing much in the process.

Nearly three years later, Prelovac is no longer with the company as he quietly left soon after the acquisition. I reached out on Twitter to ManageWP customers who stayed with the service through the transition and asked if they’re pleased with their service and if it has improved. Here are a few of the responses I received.

If you use ManageWP and have been a customer since the acquisition, let us know in the comments about how the service has evolved. Have you noticed any significant changes?

Everything You Need to Know About Java Certification

Thinking of beginning your career in programming? Not a bad idea, as there’s a high demand for programmers today. Also, being certified in a technology or programming language can considerably increase the chances of employment and improve your skills. One of the most widely used programming languages is Java, and thus, Java programmers are in high demand all around the world. If you are looking to get a Java certification, you can get it from Oracle.

Getting this certification is not that difficult or expensive. Once you’re certified, you can make your own applications, games, etc. You can use coupons from GoDaddy to host your Java app; these coupons can help you save a decent amount of money when launching your app. You can also use coupons to purchase the test preparation material, or when booking the test, you can save a decent amount of money on the test.

Git Branching: Don’t (Always) Follow the Best Practices

A debatable headline, I agree, but I will explain what it means and I hope that by the end of this short article, you will be equipped with enough parameters to chose your branching and versioning strategy and not make your decisions based purely on best practices.

Gitflow has become the de facto branching strategy for most, if not all, modern companies, and there is not a shred of doubt that it works wonders if properly adhered to. Gitflow is an exhaustive model that encompasses the branching needs of products following varied software development lifecycles, be it a bi-weekly release cycle or a half-yearly release cycle, and that is where my concern lies — it covers everything, and in my opinion, this 'one size fits all' branching model does not work in every situation. It can create process barriers and actually slow down the team.

The Future of API Management

To gather insights on the current and future state of API management, we asked IT professionals from 18 companies to share their thoughts. We asked them, "What’s the future for API management?" Here's what they told us:

Lifecycle Management

  • Deeper integration of all of the tools across the entire API lifecycle will further improve the speed of the lifecycle and more importantly the delivery of APIs that meet the consumer’s needs. This goes hand-in-hand with process improvements in the lifecycle of APIs. We see this starting to happen as organizations start treating APIs as products with product managers guiding the lifecycle.
  • I see more growth around monetization. All these API gateways are focused on the infrastructure side. As someone who publishes APIs to customers, I’d like to have analytics go one step further to monetize APIs as well. Some are more expensive others are less expensive. Be able to do manage monetization without building custom systems would be a nice thing to do.

Microservices

  • A number of big shifts are taking place at the moment. API lifecycle — everyone talks about it, but a lot of the time do you have tools for each phase versus providing an integrated approach to make it easier for the developer to design, implement, deploy, and have it managed in an automated way. I don’t want to have to do a design document and wait months to see if the API meets the design. Developers want to be more iterative and support an agile development process. We’ll ultimately automate the DevOps of APIs, but we’re not there yet.
    There will be a continued emphasis on the developer and recognizing the developer is king and making the job easier for them. We understood this for the public, but we still need to improve internally. In the form of a service catalog for internal developers to make it easier for them to ramp up and get benefits of existing APIs. New architecture — Everything is driven by containers, container platforms, and K8s is leading to microservices architecture with new approaches to control traffic with sidecar approaches to manage traffic like Envoy and Istio to provide service mesh to manage applications within the container cluster.
    As these things come up, there will be a proliferation of types of control points with multiple form factors.  We embrace Envoy as the new gateway. Right now we live in a mixed world and it’s important to consider how service mesh and API management will overlap. API management is about the relationship of providing a service and multiple consumers of that service. The more scale, the more important the formal API management platform.
    If controlling API access for a single user or developer team using an API rather than a shared library, a service mesh is fine a way to secure communications between two endpoints. A service mesh provides an intelligent network to help developers connect with other services within the mesh. Developers are at ground level in learning how to create distributed applications that work on a container, microservice environment, and service mesh will help developers with this. 
  • Modernizing applications based on microservices-based architectures is central to digital transformation initiatives. The greatest opportunity lies in the API management of microservices. Solutions with a small footprint that is flexible, portable and can operate on any infrastructure (bare metal, VMs, and containers, public cloud, and private cloud) are needed for managing APIs that are used by microservices.  
  • Now in the last year or two, there is a huge trend toward service mesh. Take API management and bring to every microservice. Ensure the ability to applications and microservices to talk to each other. Instead of API gateway also put proxy at the edge to trick microservices to only talk to the proxy. 
  • I think the market’s ready for SaaS solutions to provide authorization and API delivery options for customers who want to bring microservices APIs directly to their customers.  We aren’t the only business facing these challenges, and it’s a shame that my team has to spend so much time building proprietary solutions to what feels like commodity problems.
    It’s no surprise that Amazon, who builds each component of AWS as a microservice directly addressable by customers, is the closest I’ve found.  You can write custom authorizers that take in OAuth bearer tokens and convert these into access decisions based on IAM policies. 
    This is really slick stuff, but it does require a lot of configuration and customization on the part of the AWS customer.  I think the market need is great enough that someday we’ll see a standards-based, resource-aware API authentication and authorization product from Amazon delivered as a first-class, named product, not an orchestration tucked away in a tutorial.

Other

  • More about the discovery of the APIs out there and simplifying communication with them if I’m a consumer, knowing it’s out there and getting up, running and communicating as fast as possible. We're starting to see this with open-API specification. 
  • The tools are getting there. It's more about the industry maturing, getting there, ready to support APIs. Making tools easier and more accessible. Tools become more integrated.
  • Having a fleet of various APIs doing a specific job and doing it well is aligned with the Unix philosophy. This will give room for developers to focus solely on their core project and delegate redundant work to an already well-working service that will ensure quality and efficiency. The drawback is that often, these APIs won't be free and adding many of them might increase the monthly bills significantly.
  • Smaller, more efficient, have to be multi-language, there are opportunities for using some styles internally versus externally. GRPC a binary format developed by Google is a much more efficient way to communicate internally. Externally you still need something like REST that’s more agnostic and user-friendly. More adoption of GRPC and APIs internally. We'll see APIs presented in multiple formats – one in internal and one in external formats. 
  • In the short-term, HTTP/2 will quite probably have a broader impact than it currently has, on the very form of APIs. Use cases that were unachievable — communication patterns that were clumsy to realize are now possible. This power is not leveraged just yet.
    In the long-term, true data (and possibly compute) decentralization could seriously change the game. The tools to realize this concept are still in their infancy, though. The most advanced enabler today being the blockchain paradigm. It is awesome to see so many companies exploring how blockchain could solve better-solved problems, tackle unsolved problems — it will be full of learning. 
  • While OpenAPI Specification (OAS 3.0) adoption is still very high compared to RESTful APIs, some companies and technologies are moving beyond SOAP/XML and WSDL/WADL-based APIs. New advances in technologies like HTTP/JSON-based RESTful APIs are being adopted and serving industries very well. 
    Additionally, non-HTTP-based APIs are also on the rise making gRPC, asynchronous APIs (messaging, streaming, publish and subscribe) the focus for some companies. For example, AsyncAPI specification was built to address non-HTTP-based asynchronous APIs such as MQTT, Kafka, WebSockets, AMQP and STOMP protocols. This is where the opportunity lies for API management vendors and the rise of transformers — a tool to transform API specifications from one format to another. 
    Another opportunity for API management vendors includes expanding offerings in API Operations (APIOps). APIOps will be applied to API in a similar way that DevOps is applied to the development lifecycle of software. For example, GitLab offers the complete DevOps tools for the API lifecycle starting from project planning, source code repository to CI/CD for monitoring, security, issue tracking features all in one place for enterprises. All of the above can be hidden behind the API management platform. 
  • Considering the costs, or security issues that get created when the costs are not spent to properly maintain APIs, we need a better way. GraphQL, SPARQL, and data security co-resident with data offer an attractive future. It simplifies, offers additional utility, and puts data security where it needs to be in our multi-consumer world. Blockchain can be used to secure data integrity, allowing consumers to prove the origins of information. We sign the apps we download now to ensure they haven’t been tampered with, we think equally if not more critically is our data we are transmitting needs similar integrity to prove its origins and that it hasn’t been tampered with.
  • In the future, most of the data would’ve to be generated, sent and received in real-time. Given that data volumes generated every day are growing at an extremely high pace, developers will soon need more cloud-native and scalable solutions for managing APIs. Legacy API management solutions are already too slow and aren’t always able to scale horizontally.

Here's who shared their insights:

Messaging APIs of RingCentral

RingCentral deals with different kinds of APIs that offer reliable VoIP calling, web meetings, fax, and more features over cloud communication with reliability, security, and quality.

In this article, we will discuss the different APIs related to SMS and messaging and it’s various status.

Using AI to Augment Customer Service Agents

There is seldom a sector or field that is not undergoing some form of transformation at the moment, many at the behest of a tidal wave of digital technologies that are upending the traditional way of doing things. While many of these claims suffer from frothy over-hype, the way companies engage with customers is one domain in which the claims are justified.

A recent report from Deloitte highlighted how customer service has transitioned from the cost center of old, and the most sophisticated companies now aim to create experiences that delight customers and turn them into loyal devotees of the brand.

WordCamp Central America Organizers Prepare Proposal for 2020 Event in Managua, Nicaragua

Managua, Nicaragua
Managua, Nicaragua – image credit: CostaRica.org

WordCamp Europe’s continuing success has inspired other parts of the WordPress world to work towards getting their own regional camps off the ground. With a little help from WCEU mentors and inspiration from WordCamp Nordic’s proposal, WordCamp Asia is now officially on the schedule for February 21-23, 2020, in Bangkok, Thailand. WordCamp Central America is on deck to be the next new regional WordCamp with a proposal targeting 2020 for an inaugural event in Managua, Nicaragua.

Members of the Central American community began discussing the possibility of a larger event at the most recent WordCamp Managua 2019. For the past five years, Central America has been home to a growing number of local WordPress communities, with 12 meetups across five countries and a total of more than 4,000 participants as of July 2019. Meetup organizers have hosted more than 230 events since 2014, averaging four events per month.

In the working proposal, a document that was forked from the Nordic and Asian WordCamp proposals, organizers outlined why the timing is right for a regional camp in Central America:

The local WordPress communities have also experienced an exponential growth. In the last five years the local WordPress Meetup groups have increased fivefold. Moreover, the collaboration between the Central American communities is more active than ever; sharing experiences and resources, members attending events in neighboring countries, giving talks and volunteering in WordCamps.

This can be explained not only by the relative closeness of our countries, but also by the shared culture, values and identity of the Central American people.

We believe that hosting a Central American WordCamp will further strengthen the bonds between the local communities and give birth to new initiatives and collaborations between the local WordPress Meetup groups.

San José, Costa Rica, has the largest local WordPress community with more than 2,000 meetup members and 750 attendees at recent WordCamps. Managua, Nicaragua, the second largest community, was selected as the first host city due to its central location, direct flights from all major cities in the region, and wide availability of bus services. It is also one of the most affordable capital cities in the region and does not require visas for citizens of other Central American countries.

Organizers are planning a three-day event, beginning with Contributor Day, with four tracks during the main conference days. They are eyeing early October 2020 to avoid conflicts with other WordCamps that are frequently attended by the local community.

WordCamp Central America’s proposal has not yet been officially submitted but if it is approved, the event would be a strong addition to the region’s growing technology sector. It also has the potential to expand and amalgamate the local communities through shared knowledge and experience.

If you want to get involved, check out the proposal in progress and join the dedicated Slack workspace to participate in discussions.

Introducing Scala Cypher DSL

Working with Neo4J and Scala at ThoughtWorks, I had a major qualm regarding the way we were interacting with the graph database using Cypher. Cypher is a declarative language, hence it is tricky to compose it programmatically. This is the reason why most of the ORMs (or micro-ORMs) for Neo4J are effective only for simple use cases. We observed that as the scale and complexity of our business logic started to increase, our code fragmented into two distinct flavors. There were Scala models and business implementations. And then there were string generation and manipulation methods to generate Cypher queries.

String-based queries have inherent issues like no type safety, minimal syntax checking, difficulty in composing directly proportional to complexity, etc.

RedisAI: First Steps

At RedisConf 2019, Redis Labs introduced a new module called RedisAI. The idea is to bring together machine learning (ML) and deep learning (DL) and execute artificial intelligence (AI) models as close as possible to where your data currently lives.

This sounds amazing, but what if you’re brand new to all of this? What if you’re interested in machine learning, but you’re not quite sure what the heck it all means? How do you make sense of it all? Your boss’ boss is saying, “We need to integrate machine learning,” and last week you thought that meant he wanted you to run an extra compile step or something. Now you’re sitting here trying to understand a lot of new terms and how you can bring this into your organization.

Solving the Pains of Polyglot Persistence With Distributed SQL

Today’s microservices rely on data with different models and read/write access patterns. Polyglot persistence, first introduced in 2008, states that each such data model should be powered by an independent database that is purpose-built for that model. This post highlights the loss of agility that microservices development and operations suffer when adopting polyglot persistence. We review how distributed SQL serves as an alternative approach that doesn’t compromise this agility.

E-Commerce Example

Polyglot Persistence in Action at an E-Commerce App (Source: Martin Fowler)

Retrieving Emails and Attachments From Emails in Mule 4

Step 1

Create a new Mule project and name it samplemaildemo (You can choose any name).

Step 2

Drag and drop an HTTP listener component to get the request for your service. Specify the host and port and provide a URI path. Make sure to test it, as the port is not being used by any of your other services.

UC Browser – The Extensive Review of Chinese Browser

UC Browser is an application that attracts many users around the globe. Some users even think to switch to this browser and forget about good-old Chrome, Firefox, or Opera. The browser made by Chinese developers already had a few versions. Initially, it was distinguished by a more convenient interface, its loader, and data compression to [...]

The post UC Browser – The Extensive Review of Chinese Browser appeared first on WPArena.

How Devs Can Improve Security (Part One)

To understand the current and future state of the cybersecurity landscape, we spoke to and received written responses from 50 security professionals. We asked them, "What suggestions do you have for developers to improve the security of their applications and data?"

This is the first in a series of three articles.