Apigee Edge Microgateway: 10 Cases When You Should Use It |OPTASY

So you're evaluating and comparing all the available solutions for centralizing and standardizing your APIs. And you can't help wondering: "When is it recommended that I use Apigee Edge Microgateway?"

Why would you use it in the first place, over other platforms for managing internal APIs? Over... the Apigee Edge gateway, for instance?

What "irresistible" capabilities does it provide?

And when precisely should you use it? What are its typical use cases?

Let's get you some answers:

1. What Is Apigee Edge Microgateway? How Does It Work?

If I was to compress its definition in a short line, it would go something like this:

Apigee Edge Microgateway is a hybrid cloud solution for managing your APIs.

Whereas if I was to opt for a detailed one:

It's an HTTP-based message processor for APIs, built on Nodejs, that enables you to centralize and manage all your APIs in a hybrid cloud deployment setup.

From traffic management to enterprise-grade security, to analytics, spike arrest, and quota (and the list goes on), it provides you with most of the standard Apigee Edge capabilities.

Moreover, you get to install it either on the same machine or in the same data center.

Apigee Edge Microgateway: install it on the same machine

Source: docs.apigee.com

"And how exactly does it work?" you'll then ask yourself.

It processes the messages — requests, and responses — going to and from your backend services. Meaning that it'll asynchronously push API execution data to Apigee Edge once consumed by the Edge Analytics.

"What about the Edge Microgateway deployment scenarios? What are my options?"

Well, there are quite a few, since you get to deploy it:

in PaaS platforms (e.g. Cloud Foundry)
Azure App Services
as a service instead of sidecar
integrated with Kubernetes
as a Docker container
in cloud-native PaaS platforms (e.g Google App Engine)
in virtual machines as standalone processes

2. Why Precisely This API Management Solution? 5 Big Benefits

Why would you go with Apigee Edge Microgateway over another setup for centralizing and administering your APIs?

Here are some of the strongest API management capabilities that it provides you with:

enterprise-grade security: it authenticates requests based on an API key or signed access token that each client app gets via Apigee Edge
analytics: it publishes all the data analytics to Apigee Edge so that everyone gets traffic stats in real-time
configuration: no special coding is needed to set up Apigee Edge Microgtateway
rapid deployment: you get to deploy an instance in no time
reduced latency: it collects and sends API data to Apigee Edge asynchronously, therefore with minimal delay

3. When Would You Use It? What Are Its Typical Use Cases?

When is it best to go with a hybrid deployment model for managing your APIs?

Apigee Edge Microgateway: When Should You Use It?

Source: LinkedIn

Here are some of the most common use cases of Apigee Edge Microgateway:

for an application running on a microservices architecture
to keep API traffic within specific limits set for compliance and security reasons
to provide Apigee API management for services running in Kubernetes
for behavioral testing (of the scaling, of the infrastructure...)
for disaster recovery
to speed up API traffic for services running in close proximity
when legal and geographical boundaries are involved; for instance, when some of your global products need to run in regional data centers due to issues regarding personal data
to keep processing messages even when there's no internet connection
for cost management and market segregation

4. And What's the Difference Between Apigee Edge and Microgateway?

Apigee Edge vs Microgateway... why should you consider the later?

How are they different more exactly?

Especially since it gets even more confusing when considering that you even get Apigee Edge Microgateway plugins, which are so similar to Apigee Edge's policies...

What capabilities, that you can benefit from using Apigee Edge, does Microgateway lack, for instance?

Now, in terms of differences, here's a general "rule of thumb":

Apigee Edge Microgateway does not come to replace the Edge gateway.

It has its own specific "lighter" use cases, like various mediations, key verification, quota that you can do with your backend services in close proximity, all while tapping into its robust above-mentioned capabilities.

The END!

Are you using Apigee Edge Microgateway? If so, what's your specific use case?

And why have you decided to go with Microgateway instead of Edge Gateway?

Image by Lynn Neo from Pixabay

We do Web development

Go to our Web development page!

Visit page!

Recommended Stories

Design Drupal 8 Tips

5 Drupal Blog Posts That Have Made It to the Favorites Lists of All the OPTASY Team Members this Month

This month's "surreal" events have shaken the world as we had known it. They have "closed" us safely inside our homes, stopped us from doing many of what we had considered as "ordinary" activities, but it hasn't stopped us from... reading. And Drupal blog posts are always on our reading lists. We've recently compared our lists of favorites, put together OPTASY's monthly selection, which includes those Drupal articles that most of our team members found valuable, and... we're now ready to share it with you. Here they are: OPTASY's top 5 favorite Drupal tutorials, guides and insights in March. 1. Getting Started with the Gutenberg Editor in Drupal We, too, have recently shone some light on the Gutenberg module for Drupal 8, one of the latest layout tools added to Drupal's toolbox. A tool aimed at improving the editing experience in Drupal. While doing our research, we “bumped into” this blog post. And it quickly became one of the team's favorite Drupal blog posts of the month since: it's concise and to the point it's neatly structured it includes all the information that anyone interested in taking this Drupal page builder for a “spin” could possibly need From: installation to configuration to the final step, where you use the Gutenberg Editor to publish content on your Drupal landing page … the blog post takes you through all the steps you need to take to get yourself familiarized with using this site building tool. Source: Opensource.comNote: we loved that the Opensource team insisted on highlighting those Gutenberg features that are specific to the Drupal integration only (you won't find them in the WordPress plugin): granular permission placeholder content the possibility to add Drupal blocks inline 2. Drupal Website Accessibility in Review: Key Features & Useful Modules “How to implement web accessibility?” “How do I make my website WCAG compliant?” Any responsible Drupal website owner asks himself this kind of questions these days. No one wants to risk getting sued for having underestimated the importance of color contrast. Or the importance of displaying web forms that can be easily filled in by all the website visitors. But what if your CMS helped you check off most of the recommendations on the W3C accessibility checklist by... default? This is what Drupal 8 helps you with. And this is what the Wishdesk team's post, one of the best Drupal blog posts in March, is all about. It makes a useful inventory of Drupal's built-in accessibility features and contributed accessibility modules. “What makes Drupal 8 accessible out of the box and easily extendable, helping you reach even the “nice to have” accessibility levels on your website?” The post has all the answers to your question. Source: WishDesk.com It outlines all of Drupal's built-in features for accessibility: the accessible inline form errors the shiny and new Olivero front-end theme the ALT text for images required by default in Drupal 8 ... Then, it covers the key contributed modules that you could enable to further boost your website's level of accessibility: CKEditor Abbreviation, Siteimprove, Automatic Alternative Text, HTML Purifier, etc. A useful checklist to keep at hand whenever we add or improve accessibility on our clients' Drupal websites. 3. Using Drupal in a Pandemic, One of Our Top Favorite Drupal Blog Posts The Lullabot team stroke again. Just that this time it wasn't a valuable Drupal tutorial/technical guide that they put together, but a list of Drupal mindsets that we can all apply in the context of the COVID-19 pandemic. And the similes that they found and pinpointed are just fantastically... appropriate. Here are just some examples: 3.1. As Drupal contributors, we've come to learn that we can also help the community by stepping back and letting other contributors step forward. Likewise, we can still join the fight against COVID-19 by simply... staying home.Source: Lullabot.com 3.2. Over time, we've learned that by “getting off the Drupal island” and partnering with other communities we could help push Drupal forward. Likewise, these days we need to step out off our own circles of needs and put our skills and technical knowledge to work for others in need. Or for those who are directly involved in providing relief. 3.3. “Community” is the best term for defining Drupal. It's a community of contributors working together and not a community of individualistic “rock stars” contributing, each, merely for his/her own fame and gratification. Likewise, there's no way that we can fight this pandemic by being selfish and egocentric. We need to join forces. To join the global community of people who're applying the “social distancing” measures. It's something that we can all do and that we can all benefit from. And these are but some of the Drupal-specific principles that the Lullabot team managed to turn into clear responses to the crisis that we're living. We invite you to discover their other Drupal lessons that you, too, can easily turn healthy mindsets these days. 4. Set Up Product Attributes in Drupal Easily & Boost Online Sales A useful step-by-step tutorial on how to set up product attributes on a Drupal Commerce website. Why has it made it to our list of favorite Drupal blog posts of the month? because it tackles an all too common “To do” on the lists of our Drupal projects: setting up product attributes properly, in a way that's easy to manage by the site admins/editors and easy to scan through and to select from for the end-user because it's clearly written, with lots of helpful print screens and a logic structure In short: it's an honest tutorial, written in a clear and accessible style, that shows you exactly how to set up product attributes in your online Drupal store. From the point where you add a new product attribute, all the way to the final step, where you connect that attribute to the specific product variation type on your e-commerce website. Source: Druedesk.com 5. Concurrent Editing in Drupal 8: Possible or Not? “How do you implement concurrent editing in Drupal? Is there a solution for it already in Drupal core?” This is the question that the QED42 team asked themselves when they faced the challenge of setting up a system where multiple content creators could access and edit, simultaneously, yet independently, layouts and widgets in a Drupal app. Source: QED42.com And it's this problem, that they had to find an answer to while working on their project, that made them share their findings in the form of a useful blog post. A post that brings forward 3 modules that the team evaluated as possible solutions for concurrent editing in Drupal: Paragraph Frontend UI Conflict Content Lock What makes it set itself apart from other Drupal blog posts that we've read in March? it's focused on a real Drupal limitation ... one that many Drupal teams struggle to find an answer to while working on their clients' projects: how to enable distributed editorial teams to edit content simultaneously, with zero conflicts that might arise from their concurrent actions it presents multiple possible Drupal solutions to it, each one with its strengths and weaknesses it shares their own custom solution to this Drupal shortcoming: turning the widget creation into a decoupled, separate node, and referring all those widget nodes into the Layouts Useful, usable, relatable. In short, it's a Drupal blog post valuable enough to add it to our own resources list. The END! Your turn now: How does your own list of March favorites look like? What valuable Drupal guides, tutorials, and insights have you run into this month?Photo by Annie Spratt on Unsplash ... Read more

Adriana Cacoveanu / Mar 31'2020

Tips Web Design

You Have Your List of Web Accessibility Issues: What Do You Fix First? 8 Simple Ways to Prioritize Accessibility Problems

You've run your audit, you've got your list of web accessibility issues: now what? Where do you start? Before you get to the point where you ask yourself “How do I fix web accessibility issues on my site?” you wonder: “Which issue to address first?” How do you prioritize accessibility problems? By noticeability, by severity or by tractability? What criteria do you use? And this is the question that this post will answer to. It's a list of 8 simple ways to prioritize the issues included in your accessibility audit report: If Your Website's Image-Heavy, ALT Text Becomes a Priority If You Host Lots of Videos, Adding Captions Is Critical Let the Data on Your Target Audience Dictate Your Priorities If the Issue Is Repetitive for Screen Readers, Then It's High Priority Put on Your List of Web Accessibility Those that Impact the User Navigation Prioritize the Issues that Prevent Users from Submitting Forms Prioritize The Accessibility Issues Detected on Key Pages of Your Site Prioritize Low Complexity, but High-Value Issues 1. If Your Website's Image-Heavy, ALT Text Becomes a Priority Do you have lots of images on your website? Then adding ALT text is a top priority, by default. 2. If You Host Lots of Videos, Adding Captions Is Critical Do you have lots of video content on your site? Then adding captions should be one of the first tasks to carry out after you've run your web accessibility audit. 3. Let the Data on Your Target Audience Dictate Your Priorities Customer analytics should be the main criteria to use when you put together a list of web accessibility issues. How many people in your customer base use screen magnifiers to zoom in specific sections on your website? Are there users depending on screen readers in order to interact with your website? What does the analytics data tell you? It's those stats that determine how you should prioritize your usability problems. And how you should design your website accessibility plan. Source: Medium.com In this case, categorizing (and therefore prioritizing) web accessibility issues by their WCAG level (A, AA, AAA) is a bit rudimentary. The data that you have on your user target group might reveal to you that complying with certain AA (or “nice to have”) standards is more important for your audience than complying with some A standards... In short: start with those issues that have a direct impact on your specific customer base. 4. If The Issue Is Repetitive for Screen Readers, Then It's High Priority Take an issue listed in the W3C accessibility checklist as common as... link names. It says there that the displayed text should be unique, meaningful and descriptive enough. Has your automated accessibility testing tool identified multiple instances of this issue? Do they seem to be so repetitive that the experience of any website visitor using a screen reader is just... terrible? Then you should address them ASAP. 5. Put on Your List of Web Accessibility Issues Those that Impact the User Navigation You've run your web accessibility audit and now you need to prioritize the issues detected. An effective criterion to use for setting up a hierarchy of “errors” is the impact that those issues have on users' navigation experience. For, if those issues prevent users who depend on assistive technologies from navigating your website, they'll get discouraged/frustrated. And leave your site. For instance, your accessibility audit might detect a problematic heading structure. Which, by the way, falls into the AA category. If that heading structure: skips certain levels or, even worse, there is no heading structure at all or it contains too much irrelevant information … and is the main “culprit” for the poor navigation experience on your website, then you should make it a priority. 6. Prioritize the Issues that Prevent Users from Submitting Forms For there's nothing that says “I don't care about you” like web accessibility issues that stop users from filling in a form on your site. In short, make sure you tackle those first. I'm talking here about usability issues like: unhelpful error text messages like “please enter correct information” unaccessible inline error messages … that make it impossible for these website visitors to submit any form. 7. Prioritize the Web Accessibility Issues Identified on Key Pages Build your web accessibility test plan around the most important pages on your website. Source: support.siteimprove.com For instance, optimizing a page with a Help article isn't a top priority. But optimizing for accessibility your: Product page Login page Checkout page User Registration page Contact Us page Feedback or Survey page … should be listed among your top priorities. Tip: a common web accessibility mistake is to ask people with disabilities to enter information from their paper receipts on the survey page. Make sure this problem is among the first ones that you address. So, before you go ahead and add problems to your top list of web accessibility issues, you might want to ask yourself some key questions: “What's the scope of the page presenting accessibility issues?” “What's the traffic on the page that you're about to optimize?” 8. Prioritize Low Complexity, but High-Value Issues And now you have your answer to the question: “What if I have a high-value issue, but with low complexity like... defining page titles for dynamic pages on my website?” Final Word: Internal Prioritization Is Crucial Putting together a list of web accessibility issues to tackle first depends on your website's: audience content functionality Sticking to an “A level vs AA level” technique for figuring out what problems to fix first is... a bit too simplistic. For even not all A-level accessibility standards are of equal importance and not all AA-level issues are just “nice to haves”: Source: www.w3.org Your turn now: What criteria do you use to prioritize the accesilbity issues that you identify on your website? Are there other prioritization techniques that I should add to this list? Let me know in the comments below.Image by Gerd Altmann from Pixabay ... Read more

Adriana Cacoveanu / Mar 27'2020

Tips Web Design

What Are the 10 Rules of Good UI Design? What Is Good UI/UX Design?

In this post, I'll share with you the top 10 rules of good UI design. You will be learning: What are the essential elements of a good UI design What are the most common UI/UX mistakes that designers make What are the UI best practices in 2020 Lots more UI design tips Now, let's get started. 1. Aim at an Almost Invisible User Interface What is a good UI design? A logical structure & necessary visual elements only. In other words, in order to design an almost invisible user interface you need to: be “merciless” and keep the essential elements only base your UI on a well-thought-out structure use clear language in your text messages and on your labels Source: Medium.com A poorly structured and cluttered UI would only make the user ask questions like: “Where's the main menu?” 2. Keep It Consistent And this is one of those good UI design principles that's overlooked or undermined most often. Consistency should span over the entire ecosystem of elements that make up a UI design: fonts, colors, menus, buttons, icons. Keeping a consistent UI throughout your website translates into creating patterns aimed at enhancing efficiency. At improving the user experience. And here I'm referring to layout, design, language patterns. Once the user gets familiar with a given pattern, it will be easier for him/her to interact with other parts of your website that present the same pattern. 3. Be Purposeful with Page Layout One of the fundamental rules of good UI design is to structure your pages based on importance. In this respect, here are the crucial principles of user interface design to guide your page layout creation: take into account the spacial relationships between various elements on the page place your UI elements strategically: draw users' attention to the most important information on the page and make it easy for them to scan it through keep in mind that “form follows function”: design each item in accordance to its function (no need to reinvent the wheel and to turn the hamburger menu into a... sandwich menu, for instance) stay away from clutter, at all cost: keep the visual elements on the page to a minimum make smart use of headings, group similar elements together, add numbered items, as well, all in the name of readability IMAGE Image by 200 Degrees from Pixabay 4. Use Color and Texture Strategically Make smart use of color, texture, contrast, and light to direct the user's attention to key elements and important information on the screen. 5. Use Familiar UI Elements: One of the Key Rules of Good UI Design One of the UI best practices that's both: the easiest to implement the most underestimated And it all comes down to intuitive design. To sticking to common elements when creating your user interface. Again, the hamburger menu makes the best example: once spotted, the user knows what it is and how to open it. Restrain yourself from showing off your creativity as a web designer. From being "discouragingly" innovative. Form should follow function, remember?Instead of impressing your users, you should help them get things done quickly and easily. That's what delivering a good user experience is all about, after all. 6. Put the User in Control of the UI Instilling a sense of control in the user is one of the most powerful UI design principles. Source: xd.adobe.com In this respect, here are some specific measures that you can implement: 6.1. Provide enough context Ensure that the user knows, at each stage of his journey on your website, where he is, where he's been, and where he could go next. Tip: place visual cues to help the user develop a sense of mastery and control. 6.2. Be transparent about the system status Another one of those golden rules of good UI design: Let the user know, at all times, what's the status of the process that he's initiated. For instance, he/she might have started an action that requires some time for the computer to carry out. In this case, make sure you provide feedback, at regular intervals, about the system status, about what's going on. 6.3. Make actions reversible In other words, allow users to: unselect undo their last actions restart whatever processes that they've engaged in 6.4. Design your UI with all user skill levels in mind And this is one of the most obvious characteristics of a good UI design. It's an easy to use interface for both casual and expert-level users. 6.5. Provide feedback on every user action It's more than a good UI best practice: it's a matter of... good manners to provide at least some sort of feedback at each point of action. Therefore, make sure your system delivers a meaningful reaction each time a user: clicks on a menu hits a button clicks on a text message tab Let the user know, using specific UI elements — animations, progress bars, pop-up windows, color change — whether he's successfully carried out the action or not. 7. Minimize Cognitive Load: Recognition over Recall “Task-relevant information only” should be one of your key rules of good UI design. And sticking to a limited number of elements within the display aligns with the very limits that the human attention, itself, imposes. In this respect, it's human nature that your users prefer to recognize information across a sequence of screens rather than to strive and recall it from their memory. For instance, our cognitive load is always lighter when we're challenged to answer multiple-choice questions compared to having to tackle short answer questions. 8. Stick to One Primary Action per Screen And here, we go back to the “visual declutter” principle again: Make sure that each screen supports just one single main action. Squeezing too much information on the same screen and requesting the user to carry out more than one primary action will just: confuse him/her distract him lead to attention overload 9. Use Typography to Create Visual Hierarchy Most likely one of the easiest to follow rules of good UI design. Strategically use different font sizes and display text to enhance: readability scanability legibility Photo by Alice Donovan Rouse on Unsplash 10. Stick to a Small Number of Gestures Gesturing, swiping, tapping, pressing... no need to “squeeze” all these user actions into your app. Keep them to a minimum. Tip: Facebook and WhatsApp make some good UI design examples; their interfaces require a limited number of user gestures. Pro tip: make sure it's crystal clear to your users what gestures they need to perform in order to carry out certain actions on your interface. Source: Medium.com The END! Now, I'm really curious to hear/read your thoughts: How does your own list of must-follow rules of good UI design look like? Have I overlooked any key best practices? Let me know in the comments below.Image by FiveFlowersForFamilyFirst from Pixabay ... Read more

Silviu Serdaru / Mar 17'2020

Apigee Edge Microgateway: Why Would You Want to Use It and When Should You? 10 Typical Use Cases

1. What Is Apigee Edge Microgateway? How Does It Work?

2. Why Precisely This API Management Solution? 5 Big Benefits

3. When Would You Use It? What Are Its Typical Use Cases?

4. And What's the Difference Between Apigee Edge and Microgateway?

Recommended Stories

5 Drupal Blog Posts That Have Made It to the Favorites Lists of All the OPTASY Team Members this Month

You Have Your List of Web Accessibility Issues: What Do You Fix First? 8 Simple Ways to Prioritize Accessibility Problems

What Are the 10 Rules of Good UI Design? What Is Good UI/UX Design?

Browse cities

Toronto

Montreal

Vancouver

New York

Partners

Apigee Edge Microgateway: Why Would You Want to Use It and When Should You? 10 Typical Use Cases

1. What Is Apigee Edge Microgateway? How Does It Work?

2. Why Precisely This API Management Solution? 5 Big Benefits

3. When Would You Use It? What Are Its Typical Use Cases?

4. And What's the Difference Between Apigee Edge and Microgateway?

Recommended Stories

5 Drupal Blog Posts That Have Made It to the Favorites Lists of All the OPTASY Team Members this Month

You Have Your List of Web Accessibility Issues: What Do You Fix First? 8 Simple Ways to Prioritize Accessibility Problems

What Are the 10 Rules of Good UI Design? What Is Good UI/UX Design?

Browse cities

Toronto

Montreal

Vancouver

New York

Newsletter

Partners